(I jumped the gun on this one with XX-5918.) I'm seeing in various logs that we are not succeeding to get all the traffic between the proxy and registrar to use TCP. Out-of-dialog requests are routed from the proxy to the registrar by forwardingrules.xml, which always specifies TCP for contacting the registrar. But in-dialog requests (which are always for 'reg' subscriptions) generally go by UDP. In the proxy-to-registrar direction, the reason for that is that the registrar provides for itself a Contact that has no transport specification, so the proxy is free to use whatever transport it chooses, and often the messages are short enough that it chooses UDP. In the registrar-to-proxy direction, the proxy record-routes itself, but the RR does not include a transport specification, so the registrar is free use whatever transport it chooses...
At least in the proxy-to-registrar direction, this could be fixed by having the registrar 'reg' event server use a contact address that specifies "transport=tcp". Dale _______________________________________________ sipx-dev mailing list sipx-dev@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
