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. Regards, Jeroen ----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[email protected]> Sent: Wednesday, October 04, 2006 12:01 AM Subject: Re: [Sip-implementors] REGISTERing on behalf of someone >> From: Jeroen Van Bemmel <[EMAIL PROTECTED]> >> Perhaps it isn't ignoring the ports in From/To as it should. Try >> removing those >> I think you've identified the problem -- the "To" header is supposed >> to be the AOR you are registering, but your To header is >> <sip:[EMAIL PROTECTED]:5060>, not >> <sip:[EMAIL PROTECTED]>, and the URI with port 5060 is >> *not* equivalent to the one with 5060. > > I tried changing those values to not include the 5060, but INVITEs still > get sent to my server, not to the contact. > > -- > Craig > > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
