Hi, It's implicit. A proxy is expected to consult a location service, and rewrite the request URI with the result. That result should normally match a Contact URI which the UAS used in a REGISTER. See section 16.6 point 2.
The description of supporting "broken proxies" is not very helpful. They should have called it "strict request URI matching" or something like that. There are situations in which the request URI won't exactly match. You don't loose much when disabling this check Regards, Jeroen Stephan Steiner wrote: > Hi > > I recently got a new phone that wouldn't accept any calls on my PBX, > until a found an option to support "broken proxies". According to the > manufacturer, this option removes the request URI check, so that the > Contact Field in the REGISTER request won't have to match the Request > URI in an incoming INVITE. > > I spent the last half hour trying to find that requirement in the > 3261, but I've been unable to. The closest I've come is 8.1.1.1 but I > don't think it's that (especially since when I went ahead and > compared outgoing REGISTER and incoming INVITE messages, the To field > contains the public IP in both outgoing REGISTER and incoming INVITE > and the Contact contains my private IP. > > So I'm wondering if anybody could point me to the right section in > the RFC where it states that the request URI of an incoming INVITE > should match the Contact field used when the UAC registered with the > proxy. > > Regards > Stephan > > _______________________________________________ > Sip-implementors mailing list > Sip-implementors@lists.cs.columbia.edu > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
