[SR-Users] Routing for case of client's changing networks

[Daniel-Constantin Mierla]

The SIP reply is routed based on the address in the VIA header. The 
address in VIA is set by each node sending a request, if between the 
request and the response the sender is no longer available at the 
address it added as VIA, then it is little one can do for that.

You can try not sending the 100 trying, so the sender does 
retransmissions. Also, maybe the sender should send a new re-invite as 
it changes to a new network again.

Cheers,
Daniel

On 11/08/14 13:10, Dmytro Bogovych wrote:
> Greetings all.
> I have following use case:
>
> 0) Peer A and B registers on kamailio via TLS.
> 1) Peer A establishes call to peer B.
> 2) Peer A changes network and call has to be refreshed. Peer A 
> reregisters, gathers ICE candidates, builds reINVITE and sends it to 
> B. After peer A changes network again, reregisters and waits for 
> answer from old reINVITE.
> 3) Peer B receives reINVITE and sends answer.
>
> The problem is this answer never gets to peer B.  Kamailio cannot 
> route answer as old TLS connection is closed and new one did not 
> established before reregistering.
>
> Is there way to solve or avoid this situation?
>
> Thank you :)
>
>
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Next Kamailio Advanced Trainings 2014 - http://www.asipto.com
Sep 22-25, Berlin, Germany ::: Oct 15-17, San Francisco, USA

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20140811/e58e4615/attachment.html>