In any incoming message, the proxy checks for an removes the initial Route header value if that value specifies "itself". It performs this recursively to avoid extra forwarding of the message. However, the proxy does not recognize its SIP domain (per se) as "self" when performing SipMessage::normalizeProxyRoutes. This is because the test for "self" is done using the isMyHostAlias method of the SipUserAgent, and in an HA system, the SIP domain is not (in fact) an alias for the host. This is currently causing problems with ISN and ENUM resolution (XECS-2390), but can be expected to cause problems any time a Route header appears containing the SIP domain and the SIP domain is not the name of the host.
So it seems to me that we need to update the definition of normalizeProxyRoutes. But there may be complications that I am not seeing. Dale _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
