________________________________________ From: Staffan Kerker [[email protected]]
> 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 ________________________________________ OK, good -- the ACK's request-URI is not a name-addr, it's a URI, albeit a very long one. So we've fixed that problem. But you have *another* problem, which seems to be a deficiency in the "NAT compensation" system in the proxy. I'm going to need to look at how the proxy processes that ACK. Can you set the proxy and registrar to log at DEBUG level, execute one of these calls, and then obtain a snapshot (that includes the logs for the call)? Dale _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
