> It appears that the (proprietary) implementation of NAT traversal in your > registrar conflicts with third party registrations (in other words: it > does not support 3rd party registrations). It should work with standards > compliant registrars > > Perhaps there exists an additional proprietary mechanism (eg some kind of > flag in the Contact) to tell it not to perform the NAT hack.
Yes, indeed... that is the conclusion I have come to. According to the User Agent of the proxy I am registering against, it is an Asterisk instance. In addition, testing against my own installation of OpenSER gives the same behaviour (and looking at the source code, I can see no way that it could possibly support third-party registrations). Bummer... it is a bit of a pity that two of the most popular proxies don't support third-party registrations properly. I am chasing up on their respective newsgroups to see if there is a flag I can set to workaround it (doesn't look like it so far). Anyway, thanks to all for their patience and assistance. Cheers, Craig _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
