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?
Thanks, -- Alex Balashov - Principal Evariste Systems LLC Tel: +1-678-954-0670 Web: http://www.evaristesys.com/, http://www.alexbalashov.com/ Please be kind to the English language: http://www.entrepreneur.com/article/232906 _______________________________________________ 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
