Hi, From RFC 5626 - Section 4.2.1. Initial Registrations: ---------- Note: The UAC can situationally decide whether to request outbound behavior by including or omitting the "reg-id" Contact header field parameter. For example, imagine the outbound-proxy-set contains two proxies in different domains, EP1 and EP2. If an outbound-style registration succeeded for a flow through EP1, the UA might decide to include 'outbound' in its Require header field when registering with EP2, in order to ensure consistency. Similarly, if the registration through EP1 did not support outbound, the UA might not register with EP2 at all. ------------
Can UA include the 'outbound' tag in its Require header field when registering with EP1? Regards, Prashanth M E prashanth.me wrote: > Satya, > Thanks, > > Assume that the UA detects itself behind the NAT, if UA decides that no > use to register an un-routable contact > without outbound registration, it has to De-register after finding > **NO** outbound tag in Require header of 200 OK. > > Instead the UE shall add the "outbound" in Require header of REGISTER. > If the Registrar does not support "outbound", it shall simply reject > with "420 Bad Extension" error resp. > So that the registration and again de-registration overhead shall be > avoided. > > Regards, > Prashanth M E > > Satya Kumar wrote: > >> Hi, >> Since the Require header (in 2xx response) with "outbound" >> is sent by Registrar, indicating it's support for it >> It might not be needed from UA side, to mention it as mandatory >> through Require, Since it is a server dependant service. >> >> Regards, >> Satyakumar >> >> ----- Original Message ----- From: "prashanth.me" >> <[email protected]> >> To: <[email protected]> >> Sent: Thursday, November 19, 2009 3:26 PM >> Subject: [Sip-implementors] [outbound] Require: outbound in the >> initialREGISTER request ? >> >> >> >>> Hi, >>> >>> Suppose UA is behind NAT. At registration time, can UA add the >>> Option tag "outbound" in the >>> Require header of REGISTER request, since it does not want to continue >>> otherwise? >>> Similarly, shall it add the option tag "path" in Proxy-Require of the >>> REGISTER? >>> >>> As per RFC3261, if the UA requires the support of any option tag >>> compulsorily, then it adds >>> those tags in Require/Proxy-Require header. >>> But, this behavior is not mentioned explicitly, in RFC5626. >>> >>> Please clarify. >>> >>> Thanks in adv. >>> >>> Regards, >>> Prashanth. M E >>> >>> _______________________________________________ >>> Sip-implementors mailing list >>> [email protected] >>> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors >>> >> The information contained in this e-mail message and/or attachments to it >> may >> contain confidential or privileged information. If you are not the >> intended >> recipient, any dissemination, use, review, distribution, printing or >> copying of the information contained in this e-mail message and/or >> attachments to it are strictly prohibited. If you have received this >> communication in error, please notify us by reply e-mail immediately and >> permanently delete the message and any attachments. >> >> > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
