Hi , When a proxy receive a Invite request with MF value as 1 ,then the condition specified on the RFC 3261 section 16.3 bullet 3 is satisfied. (it is not Zero and it is not Option) .
Then as per the section 16.6 bullet 3 the proxy should decrement the MF's value by 1. Now the value is zero. And proxy forwards the request to UA B. If the Invite belongs to the UA B then it will not give any Error response,instead of giving the error response it have to process that Invite Request and give the 100 Trying or some appropriate responses. Because the Section 16.3 bullet 3 says the following " If the request contains a Max-Forwards header field with a field value of zero (0), the element MUST NOT forward the request ". Also this is Proxy server's behavior but here the final destination is UA B. So , It have to behave as User Agent. so If an UA receives a Request with MF value zero,and at the same time if the request 's final destination is that UA then it have to process the request and give the appropriate response (not 483 ), But if the UA is going to act as Proxy (i.e if it decides to forward that request ) then it have to give 483. Thanks Balaji Murlitharan.C "Bin Chen" <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 11/14/2006 06:01 AM To "'Bogdan Pintea'" <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]> cc [email protected], [EMAIL PROTECTED] Subject Re: [Sip-implementors] Sip-implementors] Queryon max-forwards counts Hi， Sorry, from the RFC3261 I can find any clue that the INVITE should be forwarded when mf = 0 on Proxy-B: If the request contains a Max-Forwards header field with a field value of zero (0), the element MUST NOT forward the request. If the request was for OPTIONS, the element MAY act as the final recipient and respond per Section 11. Otherwise, the element MUST return a 483 (Too many hops) response. Could you explain this? ABAI -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bogdan Pintea Sent: Tuesday, November 14, 2006 12:06 AM To: [EMAIL PROTECTED] Cc: [email protected]; [EMAIL PROTECTED] Subject: Re: [Sip-implementors] Sip-implementors] Queryon max-forwards counts Correct! Only if - incoming request has mf=0 and - request should be proxied further must the Proxy-B generate the 483. [EMAIL PROTECTED] wrote: > Hello, > > This is not correct. As per RFC3261 chapter 16.3 bullet 3 and chapter > 16.6 bullet 3 > Proxy-B will forward the INVITE with Max-Forwards on zero to UA-B. > > Best regards, > > Ben. > > [EMAIL PROTECTED] wrote: > > >> As per 3261: it should reject the request with 483. >> >> HTH, >> Sreeram. >> >> -----Original Message----- >> From: [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED] On Behalf Of >> [EMAIL PROTECTED] >> Sent: Monday, November 13, 2006 5:57 PM >> To: [email protected] >> Subject: [Sip-implementors] Sip-implementors] Query on max-forwards >> counts >> >> >> >> >>> Consider the following flow: (mf=max-forwards) >>> >>> >>> UA-A --- INVITE (mf=2) ---> Proxy-A ---- INVITE (mf=1) ---> >>> Proxy-B ---- INVITE (mf=0) ---> UA-B >>> >>> >>> In the flow above, should Proxy-B forward the INVITE with >>> max-forwards=0 to UA-B or should it reject the request with 483? >>> >>> >>> >> _______________________________________________ >> Sip-implementors mailing list >> [email protected] >> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors >> >> >> The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. >> >> WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. >> >> www.wipro.com >> >> _______________________________________________ >> 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 > > _______________________________________________ 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 *********************** Aricent-Private *********************** "DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus." _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
