On 7/24/06, Kai Vehmanen <[EMAIL PROTECTED]> wrote: > But if the Asterisk is in the same network addressing domain, then this > could be a bug (we shouldn't put the invalid-contact to the headers if > there is no NAT between us and a registar). And based on the log, this > would seem to be the case (192.168.0.85 is Asterisk's IP, and .90 is the > client IP)...?
I'm afraid something inserted by Asterisk to the Via headers triggers this bug in Sofia SIP. I'd be very interested to see the SIP messages between Sofia SIP and Asterisk, could you set environment variable TPORT_LOG and send the logs generated when you try to register? Alternatively, ethereal capture would be nice... -- Pekka.Pessi mail at nokia.com ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Sofia-sip-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
