Hello,
On 13/08/14 16:28, Alex Balashov wrote:
Hi,
My proxy is bound to a.b.c.d:5060 and secondarily to e.f.g.h:5060.
Most traffic comes into a.b.c.d:5060 and is relayed out that
interface. Some initial INVITEs are routed out of e.f.g.h:5060, forced
via $fs. The problem is that the Record-Route header still reflects
a.b.c.d:5060 and that sequential messages from both ends end up
entering and exiting a.b.c.d:5060. Many endpoints don't like that; for
instance, e2e ACKs from the caller that come from a.b.c.d:5060 while
the initial INVITE came from e.f.g.h:5060 can be a problem in that
they are not matched by some UASs.
What is the best way to approach this? Is this something covered by
Kamailio's 'mhomed' core param?
if you force a different outbound socket than inbound, then the
record_route() should add two headers -- doesn't happen like that? If
yes, can you provide a trace?
Btw, is any of these sockets bound to a virtual network interface?
Cheers,
Daniel
--
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
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
