The literal contact header (after subst_hf mangling) became Contact: <sip:[email protected] <sip:[email protected]>> sip:[email protected]:5090;transport=udp <sip:[email protected]:5090;transport=udp>
Which is completely bogus. I was trying (as a temporary hack) to mangle this to become Contact: <sip:[email protected] <sip:[email protected]>> Which would have matched the contact header from the INVITE and then I would have seen whether this affects the subsequent ACK for the 200 OK. But my usage of subst_hf() turned this (syntactically correct yet uninterpretable) header Contact: <sip:[email protected]:5090;transport=udp> into Contact: <sip:[email protected] <sip:[email protected]>> sip:[email protected]:5090;transport=udp <sip:[email protected]:5090;transport=udp> The code for the mangling is this: $var(ctct) = "<sip:[email protected] <sip:[email protected]>>"; subst_hf("Contact", “/\<.+\>/$var(ctct)\r\n/", "a”); Which is why I originally asked about how to use subst_hf just to debug the missing ACK. > On 24 Sep 2018, at 19:25, Alex Balashov <[email protected]> wrote: > > On Mon, Sep 24, 2018 at 06:27:51PM +0100, Ben Hood wrote: > >> Contact: <sip:[email protected] <sip:[email protected]>.x> > > Is this literally your Contact header? If so, it is definitely not > grammatically valid, and you are entirely right to assume that the > end-to-end ACK, along with any other in-dialog messages, will not be > routed from the caller correctly. > > -- > Alex Balashov | Principal | Evariste Systems LLC > > Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) > Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ > > _______________________________________________ > Kamailio (SER) - Users Mailing List > [email protected] > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
_______________________________________________ Kamailio (SER) - Users Mailing List [email protected] https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
