________________________________________ From: [email protected] [[email protected]] On Behalf Of Staffan Kerker [[email protected]]
See the Sipviewer trace: http://www.kerker.se/files/tandberg-polycom-ack-misrouted.xml The sipXproxy.log gives error messages regarding "Invalid addr-spec found", see the logfile below: http://www.kerker.se/files/tandberg-polycom-ack-misrouted.rtf _______________________________________________ It would have helped if you had gotten a proper snapshot. I'm also puzzled why you would turn the log into an RTF file. But the source of the ACK routing problem is pretty clear: In frame 45 of the siptrace, the request-URI is <sip:[email protected]:43272;transport=tcp;x-sipX-privcontact=192.168.0.116%3A5060%3Btransport%3Dtcp;sipXecs-CallDest=INT?ROUTE=%3Csip%3A85.24.162.125%3A5060%3BsipX-sig%3De473b334bdfbd3e1e8f27d18776e50cd%3E> which isn't a URI at all, it's a name-addr. That is clearly a bug in sipXregistrar, which generates it. Dale _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
