Hello, If you want to test protocol switching, try the Mercuro IMS Client (http://www.mercuro.net/). It supports the ability to switch from UDP to TCP when the packet size exceed ~1300 bytes.
Regards, Laurent Etiemble. Need an IMS Client ? Try out Mercuro IMS Client. http://www.mercuro.net/ 2009/9/28 Zhaoning Jiang <jiangzhaon...@gmail.com>: > It's a pity that many SIP device vendors do not fully support UDP auto > switch to TCP when the packets size if big according to RFC 3261 > recommandations. > > 2009/9/28 <sip-implementors-requ...@lists.cs.columbia.edu>: >> Send Sip-implementors mailing list submissions to >> sip-implementors@lists.cs.columbia.edu >> >> To subscribe or unsubscribe via the World Wide Web, visit >> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors >> or, via email, send a message with subject or body 'help' to >> sip-implementors-requ...@lists.cs.columbia.edu >> >> You can reach the person managing the list at >> sip-implementors-ow...@lists.cs.columbia.edu >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of Sip-implementors digest..." >> >> >> Today's Topics: >> >> 1. Re: When to use TCP and UDP for sip request (Schwarz Albrecht) >> 2. Re: When to use TCP and UDP for sip request (Kanta C) >> 3. Re: When to use TCP and UDP for sip request (I?aki Baz Castillo) >> 4. Re: When to use TCP and UDP for sip request (Pranab Bohra) >> 5. Re: When to use TCP and UDP for sip request (I?aki Baz Castillo) >> 6. Re: When to use TCP and UDP for sip request (Pranab Bohra) >> 7. Re: When to use TCP and UDP for sip request (David Benoit) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Thu, 24 Sep 2009 12:29:36 +0200 >> From: "Schwarz Albrecht" <albrecht.schw...@alcatel-lucent.de> >> Subject: Re: [Sip-implementors] When to use TCP and UDP for sip >> request >> To: "Abhishek Dhammawat" <abhishek.dhamma...@aricent.com>, "Sip >> Server" <sip-implementors@lists.cs.columbia.edu> >> Message-ID: >> >> <f4562d4585113d42ac08dc47fdec49b002407...@frvelsmbs23.ad2.ad.alcatel.com> >> >> Content-Type: text/plain; charset="us-ascii" >> >> you missed the SCTP option as alternative to TCP >> >> >>> -----Original Message----- >>> From: sip-implementors-boun...@lists.cs.columbia.edu >>> [mailto:sip-implementors-boun...@lists.cs.columbia.edu] On >>> Behalf Of Abhishek Dhammawat >>> Sent: Donnerstag, 24. September 2009 12:26 >>> To: Kanta C; Sip Server >>> Subject: Re: [Sip-implementors] When to use TCP and UDP for >>> sip request >>> >>> Hi >>> >>> TCP should be use when reliability is required. >>> Also when dealing with large messages TCP should be used to >>> avoid fragmentation of the messages over UDP. >>> >>> For details please refer RFC 3261 section 18.1.1. >>> " If a request is within 200 bytes of the path MTU, or if it >>> is larger than 1300 bytes and the path MTU is unknown, the >>> request MUST be sent using an RFC 2914 [36] congestion >>> controlled transport protocol, such as TCP." >>> regards >>> Abhishek Dhammawat >>> Aricent >>> >>> >>> -----Original Message----- >>> From: sip-implementors-boun...@lists.cs.columbia.edu >>> [mailto:sip-implementors-boun...@lists.cs.columbia.edu] On >>> Behalf Of Kanta C >>> Sent: Thursday, September 24, 2009 3:41 PM >>> To: Sip Server >>> Subject: [Sip-implementors] When to use TCP and UDP for sip request >>> >>> Hi All, >>> >>> Is there a rule for selecting the the transport layer >>> protocol like when to use TCP or when to use UDP.... >>> Regards, >>> Kinnu >>> >>> __________________________________________________ >>> Do You Yahoo!? >>> Tired of spam? Yahoo! Mail has the best spam protection >>> around http://mail.yahoo.com >>> _______________________________________________ >>> Sip-implementors mailing list >>> Sip-implementors@lists.cs.columbia.edu >>> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors >>> >>> "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 >>> Sip-implementors@lists.cs.columbia.edu >>> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors >>> >> >> >> >> ------------------------------ >> >> Message: 2 >> Date: Thu, 24 Sep 2009 03:32:38 -0700 (PDT) >> From: Kanta C <sip_on_...@yahoo.com> >> Subject: Re: [Sip-implementors] When to use TCP and UDP for sip >> request >> To: Schwarz Albrecht <albrecht.schw...@alcatel-lucent.de>, Abhishek >> Dhammawat <abhishek.dhamma...@aricent.com>, Sip Server >> <sip-implementors@lists.cs.columbia.edu> >> Message-ID: <659622.88344...@web111604.mail.gq1.yahoo.com> >> Content-Type: text/plain; charset=iso-8859-1 >> >> Thanks?everyone.... >> ?Regards, >> Kinnu >> >> >> >> >> ________________________________ >> From: Schwarz Albrecht <albrecht.schw...@alcatel-lucent.de> >> To: Abhishek Dhammawat <abhishek.dhamma...@aricent.com>; Sip Server >> <sip-implementors@lists.cs.columbia.edu> >> Sent: Thursday, September 24, 2009 3:59:36 PM >> Subject: Re: [Sip-implementors] When to use TCP and UDP for sip request >> >> you missed the SCTP option as alternative to TCP >> >> >>> -----Original Message----- >>> From: sip-implementors-boun...@lists.cs.columbia.edu >>> [mailto:sip-implementors-boun...@lists.cs.columbia.edu] On >>> Behalf Of Abhishek Dhammawat >>> Sent: Donnerstag, 24. September 2009 12:26 >>> To: Kanta C; Sip Server >>> Subject: Re: [Sip-implementors] When to use TCP and UDP for >>> sip request >>> >>> Hi >>> >>> TCP should be use when reliability is required. >>> Also when dealing with large messages TCP should be used to >>> avoid fragmentation of the messages over UDP. >>> >>> For details please refer RFC 3261 section 18.1.1. >>> " If a request is within 200 bytes of the path MTU, or if it >>> is larger than 1300 bytes and the path MTU is unknown, the >>> request MUST be sent using an RFC 2914 [36] congestion >>> controlled transport protocol, such as TCP." >>> regards >>> Abhishek Dhammawat >>> Aricent >>> >>> >>> -----Original Message----- >>> From: sip-implementors-boun...@lists.cs.columbia.edu >>> [mailto:sip-implementors-boun...@lists.cs.columbia.edu] On >>> Behalf Of Kanta C >>> Sent: Thursday, September 24, 2009 3:41 PM >>> To: Sip Server >>> Subject: [Sip-implementors] When to use TCP and UDP for sip request >>> >>> Hi All, >>> >>> Is there a rule for selecting the the transport layer >>> protocol like when to use TCP or when to use UDP.... >>>? Regards, >>> Kinnu >>> >>> __________________________________________________ >>> Do You Yahoo!? >>> Tired of spam?? Yahoo! Mail has the best spam protection >>> around http://mail.yahoo.com >>> _______________________________________________ >>> Sip-implementors mailing list >>> Sip-implementors@lists.cs.columbia.edu >>> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors >>> >>> "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 >>> 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 >> >> >> >> >> >> ------------------------------ >> >> Message: 3 >> Date: Fri, 25 Sep 2009 20:15:45 +0200 >> From: I?aki Baz Castillo <i...@aliax.net> >> Subject: Re: [Sip-implementors] When to use TCP and UDP for sip >> request >> To: sip-implementors@lists.cs.columbia.edu >> Message-ID: <200909252015.45353....@aliax.net> >> Content-Type: Text/Plain; charset="utf-8" >> >> El Jueves, 24 de Septiembre de 2009, Schwarz Albrecht escribi?: >>> you missed the SCTP option as alternative to TCP >> >> Yes, but also note that SCTP doesn't exist in the real IP world yet... >> >> PS: Operators network (SMS = 0.25? in 2009 year) is not what I mean "IP >> world". >> >> >> -- >> I?aki Baz Castillo <i...@aliax.net> >> >> >> >> ------------------------------ >> >> Message: 4 >> Date: Sat, 26 Sep 2009 09:05:23 +0530 >> From: Pranab Bohra <pranab.bo...@gmail.com> >> Subject: Re: [Sip-implementors] When to use TCP and UDP for sip >> request >> To: Abhishek Dhammawat <abhishek.dhamma...@aricent.com> >> Cc: Sip Server <sip-implementors@lists.cs.columbia.edu> >> Message-ID: >> <4a0886bd0909252035x666ceea9i49b8d4e2f0f2d...@mail.gmail.com> >> Content-Type: text/plain; charset=ISO-8859-1 >> >> Hi, >> >> SIP over UDP would be generally used within private or trusted >> networks where one need not worry much about reliability, bandwidth >> etc. For example, your company's network. >> TCP would be used when the messages go out into the public network. As >> Abhishek mentioned, reliability is the concern here. >> >> Thanks, >> Pranab >> >> On Thu, Sep 24, 2009 at 3:56 PM, Abhishek Dhammawat >> <abhishek.dhamma...@aricent.com> wrote: >>> Hi >>> >>> TCP should be use when reliability is required. >>> Also when dealing with large messages TCP should be used to avoid >>> fragmentation of the messages over UDP. >>> >>> For details please refer RFC 3261 section 18.1.1. >>> " If a request is within 200 bytes of the path MTU, or if it is larger than >>> 1300 bytes and the path MTU is unknown, the request MUST be sent using an >>> RFC 2914 [36] congestion controlled transport protocol, such as TCP." >>> regards >>> Abhishek Dhammawat >>> Aricent >>> >>> >>> -----Original Message----- >>> From: sip-implementors-boun...@lists.cs.columbia.edu >>> [mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of Kanta C >>> Sent: Thursday, September 24, 2009 3:41 PM >>> To: Sip Server >>> Subject: [Sip-implementors] When to use TCP and UDP for sip request >>> >>> Hi All, >>> >>> Is there a rule for selecting the the transport layer protocol like when to >>> use TCP or when to use UDP.... >>> ?Regards, >>> Kinnu >>> >>> __________________________________________________ >>> Do You Yahoo!? >>> Tired of spam? ?Yahoo! Mail has the best spam protection around >>> http://mail.yahoo.com >>> _______________________________________________ >>> Sip-implementors mailing list >>> Sip-implementors@lists.cs.columbia.edu >>> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors >>> >>> "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 >>> Sip-implementors@lists.cs.columbia.edu >>> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors >>> >> >> >> >> ------------------------------ >> >> Message: 5 >> Date: Sat, 26 Sep 2009 12:53:49 +0200 >> From: I?aki Baz Castillo <i...@aliax.net> >> Subject: Re: [Sip-implementors] When to use TCP and UDP for sip >> request >> To: sip-implementors@lists.cs.columbia.edu >> Message-ID: <200909261253.49575....@aliax.net> >> Content-Type: Text/Plain; charset="iso-8859-1" >> >> El S?bado, 26 de Septiembre de 2009, Pranab Bohra escribi?: >>> As >>> Abhishek mentioned, reliability is the concern here. >> >> I don't understand it. You are speaking about *network* level reliability >> (level 4) but since we are talking about SIP what we need is *application* >> level reliability (level 5). And the fact is that SIP implements by itself >> reliability in the protocol (ACK, CSeq, retransmissions...). >> >> Of course that SIP over TCP simplifies the reliability mechanism (basically >> some transaction timers used in SIP UDP dissapear for SIP TCP) but from the >> point of view of the application protocol (SIP) reliability exist for both >> transport layers (reliable: TCP, and non reliable: UDP). >> >> Regards. >> >> -- >> I?aki Baz Castillo <i...@aliax.net> >> >> >> >> ------------------------------ >> >> Message: 6 >> Date: Sun, 27 Sep 2009 23:35:44 +0530 >> From: Pranab Bohra <pranab.bo...@gmail.com> >> Subject: Re: [Sip-implementors] When to use TCP and UDP for sip >> request >> To: I?aki Baz Castillo <i...@aliax.net> >> Cc: sip-implementors@lists.cs.columbia.edu >> Message-ID: >> <4a0886bd0909271105v3ee6a37crb5551333780fc...@mail.gmail.com> >> Content-Type: text/plain; charset=ISO-8859-1 >> >> An example - An UAS will respond with 500 response when it receives >> out of order requests. >> This might result in session tear down. >> TCP handles OOO packets in a better way and won't let such situation occur. >> I think one would use TCP (i.e reliable L4 ) when SIP reliabilility >> alone is not enough. >> >> Thanks, >> Pranab >> >> >> On Sat, Sep 26, 2009 at 4:23 PM, I?aki Baz Castillo <i...@aliax.net> wrote: >>> El S?bado, 26 de Septiembre de 2009, Pranab Bohra escribi?: >>>> As >>>> Abhishek mentioned, reliability is the concern here. >>> >>> I don't understand it. You are speaking about *network* level reliability >>> (level 4) but since we are talking about SIP what we need is *application* >>> level reliability (level 5). And the fact is that SIP implements by itself >>> reliability in the protocol (ACK, CSeq, retransmissions...). >>> >>> Of course that SIP over TCP simplifies the reliability mechanism (basically >>> some transaction timers used in SIP UDP dissapear for SIP TCP) but from the >>> point of view of the application protocol (SIP) reliability exist for both >>> transport layers (reliable: TCP, and non reliable: UDP). >>> >>> Regards. >>> >>> -- >>> I?aki Baz Castillo <i...@aliax.net> >>> >>> _______________________________________________ >>> Sip-implementors mailing list >>> Sip-implementors@lists.cs.columbia.edu >>> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors >>> >> >> >> >> ------------------------------ >> >> Message: 7 >> Date: Sun, 27 Sep 2009 15:19:37 -0300 >> From: David Benoit <ben...@starscale.com> >> Subject: Re: [Sip-implementors] When to use TCP and UDP for sip >> request >> To: Pranab Bohra <pranab.bo...@gmail.com> >> Cc: sip-implementors@lists.cs.columbia.edu >> Message-ID: <20090927181937.gb22...@starscale.com> >> Content-Type: text/plain; charset=us-ascii >> >> RFC 3261 clearly states that a failure of a transaction within a dialogue >> does >> not necessitate tear-down of the session. For example, if a re-INVITE fails, >> the session continues with the previously negotiated information. Only in >> the >> case of a 481 or a 408 should the dialogue be torn down. >> >> Out of order requests (aside from not having a distinct error code for that) >> is a simple case to deal with. >> >> The _only_ reason I ever switch to TCP is if the patch between endpoints >> involves something that will fragment a large UDP packet and not re-assemble >> it. There are too many headaches with the TCP usage in SIP to use it for >> anything else. >> >> David >> >> On Sun, Sep 27, 2009 at 11:35:44PM +0530, Pranab Bohra wrote: >>> An example - An UAS will respond with 500 response when it receives >>> out of order requests. >>> This might result in session tear down. >>> TCP handles OOO packets in a better way and won't let such situation occur. >>> I think one would use TCP (i.e reliable L4 ) when SIP reliabilility >>> alone is not enough. >>> >>> Thanks, >>> Pranab >>> >>> >>> On Sat, Sep 26, 2009 at 4:23 PM, I?aki Baz Castillo <i...@aliax.net> wrote: >>> > El S?bado, 26 de Septiembre de 2009, Pranab Bohra escribi?: >>> >> As >>> >> Abhishek mentioned, reliability is the concern here. >>> > >>> > I don't understand it. You are speaking about *network* level reliability >>> > (level 4) but since we are talking about SIP what we need is *application* >>> > level reliability (level 5). And the fact is that SIP implements by itself >>> > reliability in the protocol (ACK, CSeq, retransmissions...). >>> > >>> > Of course that SIP over TCP simplifies the reliability mechanism >>> > (basically >>> > some transaction timers used in SIP UDP dissapear for SIP TCP) but from >>> > the >>> > point of view of the application protocol (SIP) reliability exist for both >>> > transport layers (reliable: TCP, and non reliable: UDP). >>> > >>> > Regards. >>> > >>> > -- >>> > I?aki Baz Castillo <i...@aliax.net> >>> > >>> > _______________________________________________ >>> > 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 >>> >>> !DSPAM:4abfa992127521958711902! >>> >> >> >> ------------------------------ >> >> _______________________________________________ >> Sip-implementors mailing list >> Sip-implementors@lists.cs.columbia.edu >> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors >> >> End of Sip-implementors Digest, Vol 78, Issue 13 >> ************************************************ >> > > > > -- > 此致 > 敬！ > > 姜兆宁 > > _______________________________________________ > 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
