On Sat, 2009-05-30 at 00:54 -0400, Mark Gertsvolf wrote: > I am investigating a case, where an INVITE reaching sipXproxy with a > R-URI equal to the proxy's SIP domain and a route header containing > proxy's SIP domain gets dropped on the floor with no response. > > R-URI: INVITE sip:domain.com > Route: <sip:domain.com:5060;transport=udp;lr> > > My sipX host is host.domain.com and my SIP domain is: domain.com. > > Looking at the logs I am finding that proxy does not pop the route to > self. The reason seems to be with the fact that proxy's host aliases > list does not contain the "domain.com:5060" string. > > My sipXproxy-config contains: > > SIPX_PROXY_HOST_ALIASES : 192.168.3.2:5060 host.domain.com:5060 > > While I would expect: > > SIPX_PROXY_HOST_ALIASES : 192.168.3.2:5060 host.domain.ca:5060 > domain.com:5060 > > Is that normal?
Yes... as Robert said, the real domain comes from another file. The presence or absence of the port number should not be a problem (the comparison function adjusts for that). More detail on the request and what happens to it might help... _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
