Sent from my Android phone using TouchDown (www.nitrodesk.com)
-----Original Message----- From: [email protected] [[email protected]] Received: Monday, 15 Apr 2013, 1:34 To: [email protected] [[email protected]] Subject: Sip-implementors Digest, Vol 121, Issue 5 Send Sip-implementors mailing list submissions to [email protected] 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 [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of Sip-implementors digest..." Today's Topics: 1. Forming of MESSAGE-INTEGRITY header for STUN Bind request and Response (Sachin Rastogi) 2. SIP 200 OK (onewhoknows) 3. Contact Header!! (Kumar, Puneet (Puneet)) 4. Re: Contact Header!! (Dmitry Akindinov) 5. Re: Contact Header!! (Kumar, Puneet (Puneet)) 6. IN SDP Session version value received negative ([email protected]) 7. Re: IN SDP Session version value received negative (Brett Tate) 8. Re: Contact Header!! (Brett Tate) 9. Query regarding ABNF syntax for SIP message headers (Sumant Gupta) ---------------------------------------------------------------------- Message: 1 Date: Thu, 11 Apr 2013 21:52:40 +0530 From: Sachin Rastogi <[email protected]> Subject: [Sip-implementors] Forming of MESSAGE-INTEGRITY header for STUN Bind request and Response To: [email protected] Message-ID: <CAEP1s-MR1sf56nQyqShfE=d+ou9lj12oh+hswa5rwnzbnhy...@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Dear All, I have a question on forming of MESSAGE-INTEGRITY header for STUN Bind request and STUN Bind Response. ICE username and password are exchanged using SIP offer/answer model. Offer from ICE Full Client (say Client IFC) ============================================= v=0 o=UE1 970829 970829 IN IP4 10.199.103.2 s=- c=IN IP4 10.199.103.2 b=AS:80 b=TIAS:64000 t=0 0 m=audio 27000 RTP/AVP 0 b=RS:0 b=RR:0 a=rtpmap:0 PCMU/8000 a=ptime:20 a=sendrecv a=ice-pwd:asdfghjklpoiuytrewqasd a=ice-ufrag:8hhy a=candidate:1 1 UDP 2130706431 10.199.103.2 3478 typ host a=candidate:2 1 UDP 1694498815 10.199.103.2 3479 typ srflx raddr 10.199.103.2 rport 3479 a=candidate:3 1 UDP 16777215 10.199.103.2 27000 typ relay raddr 10.199.103.2 rport 27000 Answer from ICE Lite Client (say ILC) ============================ v=0 o=sip 186828262 109337344 IN IP4 10.199.74.52 s=- i=Audio/Fax Session c=IN IP4 10.199.74.52 b=AS:80 b=TIAS:64000 t=0 0 a=ice-lite a=maxprate:50.0 m=audio 22036 RTP/AVP 0 b=AS:80 b=TIAS:64000 a=rtpmap:0 PCMU/8000 a=maxprate:50.0 a=ptime:20 a=sendrecv a=ice-ufrag:/iUD a=ice-pwd:bHsngceY6C9735cwqC6PTe a=candidate:1 1 UDP 2130706431 10.199.74.52 22036 typ host a=candidate:1 2 UDP 2130706430 10.199.74.52 22037 typ host I want to know which password (as we have two password one from client IFC and other from client ILC) will be used for forming of MESSAGE-INTEGRITY header of STUN Bind request and response. Client IFC will be sending STUN bind request and client ILC will be replying with STUN bind response. STUN Bind/Request is as follows =============================== Sent from IP|Port=10.199.103.2|27000 To IP|Port=/10.199.74.52:22036 Sequencer=19 Transport=UDP [STUN BindingRequest messageType[0x00 0x01 ] length=[116] transactionID=[0x21 0x12 0xa4 0x42 0x0d 0x54 0xa9 0x78 0x68 0xd7 0x57 0x9a 0x00 0x00 0x00 0x00 ] and 6 attributes. USERNAME=[0x00 0x06 ] valueLen=[9] value=[/iUD:8hhy] padding=[3] ICE-CONTROLLING=[0x80 0x2a ] valueLen=[8] value=[-119239875] padding=[0] PRIORITY=[0x00 0x24 ] valueLen=[4] value=[2130706431] padding=[0] PASSWORD=[0x00 0x07 ] valueLen=[22] value=[bHsngceY6C9735cwqC6PTe] padding=[2] MESSAGE-INTEGRITY=[0x00 0x08 ] valueLen=[20] value=[0xe0 0xe0 0x54 0x88 0xf4 0x99 0xc8 0xfa 0xef 0x55 0xae 0x92 0xcb 0x49 0xa9 0x63 0xbf 0xde 0xf8 0x20 ] padding=[0] FINGERPRINT=[0x80 0x28 ] valueLen=[4] value=[0x78 0x1e 0x02 0x91 ] padding=[0] ] INFO FSM (STUN1) - State (HostCandidate) sent event (BindingRequest) sequencer=19. INFO >>>>> RX: Length = 64 Received on IP|Port=10.199.103.2|27000 >From IP|Port=10.199.74.52|22036 Sequencer=20 Transport=UDP [STUN BindingResponse messageType[0x01 0x01 ] length=[64] transactionID=[0x21 0x12 0xa4 0x42 0x0d 0x54 0xa9 0x78 0x68 0xd7 0x57 0x9a 0x00 0x00 0x00 0x00 ] and 3 attributes. XOR-MAPPED-ADDRESS=[0x00 0x20 ] valueLen=[8] IPv4 Address [1] address=[/10.199.103.2] port=[27000] value=[0x00 0x01 0x48 0x6a 0x2b 0xd5 0xc3 0x40 ] MESSAGE-INTEGRITY=[0x00 0x08 ] valueLen=[20] value=[0x5b 0x29 0xe9 0x54 0x76 0x04 0x7d 0x56 0x9d 0xb2 0x31 0x95 0x97 0x1e 0xe0 0x3d 0x90 0x48 0x17 0x52 ] padding=[0] FINGERPRINT=[0x80 0x28 ] valueLen=[4] value=[0x58 0x47 0xcf 0xd8 ] padding=[0] ] Thanks & Regards Sachin Rastogi ------------------------------ Message: 2 Date: Thu, 11 Apr 2013 10:01:31 -0700 From: onewhoknows <[email protected]> Subject: [Sip-implementors] SIP 200 OK To: [email protected] Message-ID: <CAND-Es4yWbckD3dZcZ5Ur7m6wMxChAfEXo=4webumed+xm4...@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Well, it's short for "onewhoknows nothing" ;) Turns out that the contact header issue was a red herring. However, they are balking at the "a=fmtp 100 (null)" problem. ------------------------------ Message: 3 Date: Fri, 12 Apr 2013 07:06:19 +0000 From: "Kumar, Puneet (Puneet)" <[email protected]> Subject: [Sip-implementors] Contact Header!! To: "[email protected]" <[email protected]> Message-ID: <db7756d97fa5f04bb007ee2e91c436ff077...@az-ffexmb04.global.avaya.com> Content-Type: text/plain; charset="us-ascii" Hi All, As per the RFC, grammar for Contact header is: Contact = ("Contact" / "m" ) HCOLON ( STAR / (contact-param *(COMMA contact-param))) What is the utility of this "STAR" ? Can you provide an example Contact header which shows this "STAR" ? Thanks, Puneet ------------------------------ Message: 4 Date: Fri, 12 Apr 2013 11:27:46 +0400 From: Dmitry Akindinov <[email protected]> Subject: Re: [Sip-implementors] Contact Header!! To: "[email protected]" <[email protected]> Message-ID: <[email protected]> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Hello, On 2013-04-12 11:06, Kumar, Puneet (Puneet) wrote: > Hi All, > > As per the RFC, grammar for Contact header is: > > Contact = ("Contact" / "m" ) HCOLON > ( STAR / (contact-param *(COMMA contact-param))) > > What is the utility of this "STAR" ? > > Can you provide an example Contact header which shows this "STAR" ? rfc3261, 10.2.2 Removing Bindings -- Best regards, Dmitry Akindinov ------------------------------ Message: 5 Date: Fri, 12 Apr 2013 09:16:19 +0000 From: "Kumar, Puneet (Puneet)" <[email protected]> Subject: Re: [Sip-implementors] Contact Header!! To: Dmitry Akindinov <[email protected]>, "[email protected]" <[email protected]> Message-ID: <db7756d97fa5f04bb007ee2e91c436ff077...@az-ffexmb04.global.avaya.com> Content-Type: text/plain; charset="us-ascii" Thanks Dmitry. Can we have something like below ? Contact: *;q=0.2 Thanks, Puneet -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Dmitry Akindinov Sent: Friday, April 12, 2013 12:58 PM To: [email protected] Subject: Re: [Sip-implementors] Contact Header!! Hello, On 2013-04-12 11:06, Kumar, Puneet (Puneet) wrote: > Hi All, > > As per the RFC, grammar for Contact header is: > > Contact = ("Contact" / "m" ) HCOLON > ( STAR / (contact-param *(COMMA contact-param))) > > What is the utility of this "STAR" ? > > Can you provide an example Contact header which shows this "STAR" ? rfc3261, 10.2.2 Removing Bindings -- Best regards, Dmitry Akindinov _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors ------------------------------ Message: 6 Date: Fri, 12 Apr 2013 16:08:57 +0530 From: [email protected] Subject: [Sip-implementors] IN SDP Session version value received negative To: [email protected] Message-ID: <[email protected]> Content-Type: text/plain; charset=; DelSp="Yes"; format="flowed" Hello All, What is the rang of origin Session ID and Session version in SDP message ? Owner/Creator, Session Id (o): - 112 -123 IN IP4 192.168.1.32 The Problem is that some UAS Send the first INVITE with negative ("-123") session version value, so what to do in this case received the INVITE or reject the INVITE. Regards, Tejas Patel ------------------------------ Message: 7 Date: Fri, 12 Apr 2013 11:09:11 +0000 From: Brett Tate <[email protected]> Subject: Re: [Sip-implementors] IN SDP Session version value received negative To: "[email protected]" <[email protected]>, "[email protected]" <[email protected]> Message-ID: <[email protected]> Content-Type: text/plain; charset="us-ascii" The SDP is invalid per RFC 4566. You can either allow it (for interoperability reasons since mostly irrelevant) or reject it. If you reject it, you can send a 488 response with Warning header code 399 or send a 400 response. The 400 tends to get more attention; however some prefer not to send it when the body is malformed. <sess-version> is a version number for this session description. Its usage is up to the creating tool, so long as <sess-version> is increased when a modification is made to the session data. Again, it is RECOMMENDED that an NTP format timestamp is used. sess-version = 1*DIGIT > -----Original Message----- > From: [email protected] [mailto:sip- > [email protected]] On Behalf Of > [email protected] > Sent: Friday, April 12, 2013 6:39 AM > To: [email protected] > Subject: [Sip-implementors] IN SDP Session version value received > negative > > Hello All, > > What is the rang of origin Session ID and Session version in SDP > message ? > > Owner/Creator, Session Id (o): - 112 -123 IN IP4 192.168.1.32 > > The Problem is that some UAS Send the first INVITE with negative ("- > 123") > session version value, so what to do in this case received the INVITE > or reject the INVITE. ------------------------------ Message: 8 Date: Fri, 12 Apr 2013 11:15:16 +0000 From: Brett Tate <[email protected]> Subject: Re: [Sip-implementors] Contact Header!! To: "Kumar, Puneet (Puneet)" <[email protected]>, "[email protected]" <[email protected]> Message-ID: <[email protected]> Content-Type: text/plain; charset="us-ascii" > Can we have something like below ? > > Contact: *;q=0.2 No; as indicated within RFC 3261's Contact ABNF, parameters are not allowed when STAR is used. Contact = ("Contact" / "m" ) HCOLON ( STAR / (contact-param *(COMMA contact-param))) ------------------------------ Message: 9 Date: Mon, 15 Apr 2013 11:04:03 +0530 From: Sumant Gupta <[email protected]> Subject: [Sip-implementors] Query regarding ABNF syntax for SIP message headers To: [email protected] Message-ID: <cafty30xjgqnmm-8kk_es1m+ge9ndnfd_0htxs4ojzq0yh4r...@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Hi All, I have a query regarding the parsing of sip message headers.I am taking the example of via header. Is the below message correct or not? Via: \r\n SIP/2.0 \r\n /[transport] [local_ip]:[local_port];branch=[branch]\r\n As per grammer and my understanding: Via = ( "Via" / "v" ) HCOLON via-parm *(COMMA via-parm) via-parm = sent-protocol LWS sent-by *( SEMI via-params ) sent-protocol = protocol-name SLASH protocol-versionSLASH transport Now the via-parm expands to following value after populating the value of "sent-protocol" via-parm = protocol-name SLASH protocol-version SLASH transport LWS sent-by *( SEMI via-params ) Now the HCOLON refers to: HCOLON = *( SP / HTAB ) ":" SWS SWS refers to following value: SWS = [LWS] ; sep whitespace LWS refers to: LWS = [*WSP CRLF] 1*WSP ; linear whitespace >From the above syntax it seems that CRLF is possible in the above syntax of Via message header after the ":". Is my understanding correct or is there some error in understanding the ABNF grammer ? Looking forward for response. Regards Sumant ------------------------------ _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors End of Sip-implementors Digest, Vol 121, Issue 5 ************************************************ _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
