On 25 aug 2010, at 18.37, Staffan Kerker wrote: > The Request-URI in the ACK returned from sipxregistry is still the long > name-addr and not a URI.
However, I've noted that the ACK is different now from the previous trace. Please see tracefile below (adding to tracker as well) http://www.kerker.se/files/tandberg-polycom-ack-misrouted-sipxregistry-4.3.0-019022.xml Frame 50-54 show the ACK. The outgoing ACK in frame 53 has a Request-URI addressing the NATed address with a Route header pointing towards the SipXproxy itself. In the next frame, the ACK frame 54, this Route header is removed and the only routing information left is the Request URI with the RFC 1918 address (sipX-privcontact). This address is not routable from the SipXproxy. If I put my Tandberg terminal on a public IP address and remove the NAT complexity, the call is completed correctly and the ACK is routed correctly. /Staffan -- Staffan Kerker mail/sip/xmpp: [email protected] "There is absolutely no money above the 5th fret..." /Donald "Duck" Dunn
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
