Hello,

the details about source address as well as local socket are inside the field:

struct receive_info rcv;

from sip_msg_t structure. This is cloned in hard copy inside tm structure.

Are you looking for something else? Or, on the other hand, maybe you can detail more about the issue you are having/trying to solve.

Cheers,
Daniel

On 31/10/14 13:23, Alekzander Spiridonov wrote:

Re-sending, since it's looks like to be lost.

Just note: looks like the best fix is to copy message socket to force_socket struct inside transaction.

2014-10-21 13:33 GMT+04:00 Alekzander Spiridonov <alekz@li.ru>:

Hi list,

While going through an issue with multiple listen ip's I've found that while cloning the message tm doesn't save any info about the socket it was received on.

The question is: was it done on purpose or it's a bug? (e.g. for retransmitions timer prrocess is able to pick any(?) socket for sending message)/

--

Best regards,
Alekzander Spiridonov

--

Best regards,
Alekzander Spiridonov
_______________________________________________
sr-dev mailing list
sr-dev@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev

-- 
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda