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?
It's a touchy question, because the theoretical answer may be different from the practical one. Within the RFC 3263 process for translating the host-port parts of SIP URIs into the actual transport destinations, the presence of a port makes a huge difference. If I see "domain.com", then I look for NAPTR records, then SRV records, then A and CNAME records. If I see "domain.com:5060", I skip the first two steps, and only look for A and CNAME records. That is, if a port is present, the host part *must* be a host name. So in principle, "domain.com:5060" isn't a valid alias for your SIP domain, or for your proxy, and probably doesn't designate any SIP destination at all. To get to the bottom of this, it would help to know where "domain.com:5060" came from. We really should be using "domain.com", if what we mean is "route through some proxy for domain.com". 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
