Re: [Sip] Different SDP Session Version in 183 & 200 OK

Hey Guys,

             Please tell me , how can i relieve from this site. All your
mails are delivers into my mail id to........ Please suggest the idea.

With regards,

Ji

On Wed, Mar 9, 2011 at 1042 PM, Vijay Tiwari <vijay11tiwari@gmail.com>wrote:

> Hello Nitin
>
> Hope you are doing good, sorry i was able to respond that time. i saw are
> mail and according to my understanding this value can be change if
>
> "<sess-version> is  increased when a modification is made to the session
> data."
>
>
> it means that if any session data change between 183 and 200 ok message
> then it is standard behavior
>
>
> Thanks
> Vijay
>
>   On Wed, Mar 9, 2011 at 12:54 PM, Nitin Kapoor <nitinkapoorr@gmail.com>wrote:
>
>>  Hello All,
>>
>> Could any one please help me out on requested query as below.
>>
>> Thanks,
>> Nitin
>>
>> On Tue, Mar 8, 2011 at 4:48 PM, Nitin Kapoor <nitinkapoorr@gmail.com>wrote:
>>
>>> Dear All,
>>>
>>> I have one call scenario where my termination is sending the SDP in 183
>>> as well as in 200 OK also. As far as i know if we are getting SDP in 183
>>> session progress then my UAC can ignore the SDP in 200 OK. Also most of the
>>> time SDP is same.
>>>
>>> But here i noticed the slight difference of "Session Version". Here when
>>> my termination is sending 188 Session Progress with SDP is sending the SDP
>>> as below.
>>>
>>> I can see that  my Termination is incrementing  "*Session Version*" for
>>> SDP in 183 & 200 OK in same dialog..
>>>
>>> *183 with SDP*
>>>
>>> S_OWNER : o=TLPMSXP2 22660 *22660* IN IP4 69.90.230.210
>>> S_NAME : s=sip call
>>> S_CONNECT : c=IN IP4 69.90.230.217
>>> TIME : t=0 0
>>> M_NAME : m=audio 59072 RTP/AVP 18 4 8 98
>>>
>>> 200 OK with SDP:
>>>
>>> S_OWNER : o=TLPMSXP2 22660 *22661* IN IP4 69.90.230.210
>>> S_NAME : s=sip call
>>> S_CONNECT : c=IN IP4 69.90.230.217
>>> TIME : t=0 0
>>>
>>> Could anyone please let me know if that is okay to increment the session
>>> version and if any supported document is there?
>>>
>>> Thanks,
>>> Nitin
>>>
>>
>>
>> _______________________________________________
>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>> This list is essentially closed and only used for finishing old business.
>> Use sip-implementors@cs.columbia.edu for questions on how to develop a
>> SIP implementation.
>> Use dispatch@ietf.org for new developments on the application of sip.
>> Use sipcore@ietf.org for issues related to maintenance of the core SIP
>> specifications.
>>
>
>
>
> --
> They can because they think they can.
>
>
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is essentially closed and only used for finishing old business.
> Use sip-implementors@cs.columbia.edu for questions on how to develop a SIP
> implementation.
> Use dispatch@ietf.org for new developments on the application of sip.
> Use sipcore@ietf.org for issues related to maintenance of the core SIP
> specifications.
>