Can you tell which RFC required this king of behaviour???

I can't find any use for this kind of duplication..

Regards,

Vineet Menon




On 6 December 2011 16:12, Brez Borland <[email protected]> wrote:

> interesting, anybody to comment on this?
>
> On Wed, Nov 30, 2011 at 1:46 PM, Keerthi Srinivasan <
> [email protected]> wrote:
>
> > Hi All,
> >
> > If the SIP stack receives the duplication Mandatory SIP Header then the
> SIP
> > will send failure response or successful response.
> >
> > Ex:
> > Scenario 1:
> >
> > Registrar receives the REGISTER request with *duplication of multiple
> From
> > Header like*
> >       REGISTER sip:registrar.biloxi.com SIP/2.0
> >       Via: SIP/2.0/UDP bobspc.biloxi.com:5060;branch=z9hG4bKnashds7
> >       Max-Forwards: 70
> >       To: Bob <sip:[email protected]>
> >       From: Bob <sip:[email protected]>;tag=456248
> >       From: Bob <sip:[email protected]>;tag=456248
> >       From: Bob <sip:[email protected]>;tag=456248
> >       From: Bob <sip:[email protected]>;tag=456248
> >       From: Bob <sip:[email protected]>;tag=456248
> >       Call-ID: 843817637684230@998sdasdh09
> >       CSeq: 1826 REGISTER
> >       Contact: <sip:[email protected]>
> >       Expires: 7200
> >       Content-Length: 0
> >
> > Scenario 2:
> >
> > Registrar receives the REGISTER request with *duplication of multiple To
> > Header *
> >
> >       REGISTER sip:registrar.biloxi.com SIP/2.0
> >       Via: SIP/2.0/UDP bobspc.biloxi.com:5060;branch=z9hG4bKnashds7
> >       Max-Forwards: 70
> >       To: Bob <sip:[email protected]>
> >       To: Bob <sip:[email protected]>
> >       To: Bob <sip:[email protected]>
> >       To: Bob <sip:[email protected]>
> >       To: Bob <sip:[email protected]>
> >       To: Bob <sip:[email protected]>
> >       From: Bob <sip:[email protected]>;tag=456248
> >       Call-ID: 843817637684230@998sdasdh09
> >       CSeq: 1826 REGISTER
> >       Contact: <sip:[email protected]>
> >       Expires: 7200
> >       Content-Length: 0
> >
> > Scenario 3:
> >
> > Registrar receives the REGISTER request with *duplication of multiple Via
> > Header *
> >
> >       REGISTER sip:registrar.biloxi.com SIP/2.0
> >       Via: SIP/2.0/UDP bobspc.biloxi.com:5060;branch=z9hG4bKnashds7
> >       Via: SIP/2.0/UDP bobspc.biloxi.com:5060;branch=z9hG4bKnashds7
> >       Via: SIP/2.0/UDP bobspc.biloxi.com:5060;branch=z9hG4bKnashds7
> >       Via: SIP/2.0/UDP bobspc.biloxi.com:5060;branch=z9hG4bKnashds7
> >       Via: SIP/2.0/UDP bobspc.biloxi.com:5060;branch=z9hG4bKnashds7
> >       Via: SIP/2.0/UDP bobspc.biloxi.com:5060;branch=z9hG4bKnashds7
> >       Max-Forwards: 70
> >       To: Bob <sip:[email protected]>
> >       From: Bob <sip:[email protected]>;tag=456248
> >       Call-ID: 843817637684230@998sdasdh09
> >       CSeq: 1826 REGISTER
> >       Contact: <sip:[email protected]>
> >       Expires: 7200
> >       Content-Length: 0
> >
> > Scenario 4:
> >
> > Registrar receives the REGISTER request with* duplication of multiple
> > Call-ID Header *
> >
> >       REGISTER sip:registrar.biloxi.com SIP/2.0
> >       Via: SIP/2.0/UDP bobspc.biloxi.com:5060;branch=z9hG4bKnashds7
> >       Max-Forwards: 70
> >       To: Bob <sip:[email protected]>
> >       From: Bob <sip:[email protected]>;tag=456248
> >       Call-ID: 843817637684230@998sdasdh09
> >       Call-ID: 843817637684230@998sdasdh09
> >       Call-ID: 843817637684230@998sdasdh09
> >       Call-ID: 843817637684230@998sdasdh09
> >       Call-ID: 843817637684230@998sdasdh09
> >       CSeq: 1826 REGISTER
> >       Contact: <sip:[email protected]>
> >       Expires: 7200
> >       Content-Length: 0
> >
> > Scenario 5:
> >
> > Registrar receives the REGISTER request with *duplication of multiple
> Cseq
> > Header *
> >
> >       REGISTER sip:registrar.biloxi.com SIP/2.0
> >       Via: SIP/2.0/UDP bobspc.biloxi.com:5060;branch=z9hG4bKnashds7
> >       Max-Forwards: 70
> >       To: Bob <sip:[email protected]>
> >       From: Bob <sip:[email protected]>;tag=456248
> >       Call-ID: 843817637684230@998sdasdh09
> >       CSeq: 1826 REGISTER
> >       CSeq: 1826 REGISTER
> >       CSeq: 1826 REGISTER
> >       CSeq: 1826 REGISTER
> >       CSeq: 1826 REGISTER
> >       Contact: <sip:[email protected]>
> >       Expires: 7200
> >       Content-Length: 0
> >
> > Scenario 6:
> >
> > Registrar receives the REGISTER request with *duplication of multiple
> > Max-Forwards Header *
> >
> >       REGISTER sip:registrar.biloxi.com SIP/2.0
> >       Via: SIP/2.0/UDP bobspc.biloxi.com:5060;branch=z9hG4bKnashds7
> >       Max-Forwards: 70
> >       Max-Forwards: 70
> >       Max-Forwards: 70
> >       Max-Forwards: 70
> >       Max-Forwards: 70
> >       To: Bob <sip:[email protected]>
> >       From: Bob <sip:[email protected]>;tag=456248
> >       Call-ID: 843817637684230@998sdasdh09
> >       CSeq: 1826 REGISTER
> >       Contact: <sip:[email protected]>
> >       Expires: 7200
> >       Content-Length: 0
> >
> >
> > Scenario 6:
> >
> > Registrar receives the REGISTER request with *duplication of multiple
> > Expires: Header *
> >
> >       REGISTER sip:registrar.biloxi.com SIP/2.0
> >       Via: SIP/2.0/UDP bobspc.biloxi.com:5060;branch=z9hG4bKnashds7
> >       Max-Forwards: 70
> >       To: Bob <sip:[email protected]>
> >       From: Bob <sip:[email protected]>;tag=456248
> >       Call-ID: 843817637684230@998sdasdh09
> >       CSeq: 1826 REGISTER
> >       Contact: <sip:[email protected]>
> >       Expires: 7200
> >       Expires: 7200
> >       Expires: 7200
> >       Expires: 7200
> >       Expires: 7200
> >       Content-Length: 0
> >
> >
> > Scenario 7:
> >
> > Registrar receives the REGISTER request with *duplication of multiple
> > Content-Length Header *
> >
> >       REGISTER sip:registrar.biloxi.com SIP/2.0
> >       Via: SIP/2.0/UDP bobspc.biloxi.com:5060;branch=z9hG4bKnashds7
> >       Max-Forwards: 70
> >       To: Bob <sip:[email protected]>
> >       From: Bob <sip:[email protected]>;tag=456248
> >       Call-ID: 843817637684230@998sdasdh09
> >       CSeq: 1826 REGISTER
> >       Contact: <sip:[email protected]>
> >       Expires: 7200
> >       Content-Length: 0
> >       Content-Length: 0
> >       Content-Length: 0
> >       Content-Length: 0
> >       Content-Length: 0
> >       Content-Length: 0
> >
> >
> > Scenario 8:
> >
> > Registrar receives the REGISTER request with *duplication of multiple
> > request-line Header *
> >
> >       REGISTER sip:registrar.biloxi.com SIP/2.0
> >       REGISTER sip:registrar.biloxi.com SIP/2.0
> >       REGISTER sip:registrar.biloxi.com SIP/2.0
> >       REGISTER sip:registrar.biloxi.com SIP/2.0
> >       REGISTER sip:registrar.biloxi.com SIP/2.0
> >       REGISTER sip:registrar.biloxi.com SIP/2.0
> >       Via: SIP/2.0/UDP bobspc.biloxi.com:5060;branch=z9hG4bKnashds7
> >       Max-Forwards: 70
> >       To: Bob <sip:[email protected]>
> >       From: Bob <sip:[email protected]>;tag=456248
> >       Call-ID: 843817637684230@998sdasdh09
> >       CSeq: 1826 REGISTER
> >       Contact: <sip:[email protected]>
> >       Expires: 7200
> >       Content-Length: 0
> >
> > Please anyone can say, how registrar will respond for the above message.
> >
> > Thanks in advance.
> >
> >
> > --
> > Regards,
> > Keerthi
> > _______________________________________________
> > 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

Reply via email to