So this would seem to imply that the presence of outbound in the support header indicates that a flow should be established and the Edge Proxy record route with a flow token in order for the resulting NOTIFY to be delivered in the absence of the UA having registered?
-----Original Message----- From: Francois Audet [mailto:[EMAIL PROTECTED] Sent: Thursday, March 20, 2008 3:27 PM To: Sumanth Channabasappa; Kevin Johns; [email protected] Cc: Cullen Jennings; Rohan Mahy Subject: RE: [Sip] Outbound-12 comments Like the SUBSCRIBE in the example call flow section (the first one). > -----Original Message----- > From: Sumanth Channabasappa [mailto:[EMAIL PROTECTED] > Sent: Thursday, March 20, 2008 14:25 > To: Kevin Johns; Audet, Francois (SC100:3055); [email protected] > Cc: Cullen Jennings; Rohan Mahy > Subject: RE: [Sip] Outbound-12 comments > > > Section 4.3, Sending Non-REGISTER Requests, 1st paragraph - > "UAs that > > support this specification SHOULD include the outbound > option tag in a > > > Supported header field in a non-Register REGISTER request." > What is a > > non-Register REGISTER request? > > >>I think this is a typo: it should say "non-Register request.". > > > Further why is this recommended? I did not see this > information being > > used by the edge proxy elsewhere in the document? > > >>That is a good question. Rohan? Cullen? > > [S] An example of a non-REGISTER request is a SIP SUBSCRIBE message. I > am guessing this requirement refers to the use of outbound in such > cases. (We use the 'ob' parameter within the SIP Configuration > Framework.) > > > - S > _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [EMAIL PROTECTED] for questions on current sip Use [EMAIL PROTECTED] for new developments on the application of sip
