Kapil Nayar wrote:
> Hi Paul
> 
> Glad you corrected me!
> I was specific (not generic) about Call Hold since
> some SIP experts in my neighbourhood were of a view
> that many service providers donot support changing
> codecs when putting a call ON/ OFF Hold in the same
> Re-Invite.
> Although, this is acceptable as per the standards,
> Service Provider support would be crutial for the
> implementors. 

YMMV. If you think you will encounter implementations with a restriction 
like this, then you may want to ensure you never request such a 
concurrent change, while still being prepared to deal with one offered 
to you.

        Paul

> But, from your statement it seems it is likely to be
> supported.
> 
> thanks,
> -kapil  
> 
> --- Paul Kyzivat <[EMAIL PROTECTED]> wrote:
> 
>>
>> Kapil Nayar wrote:
>>> Hi
>>>
>>> The SDP/ SIP standards donot restrict the Call
>> Hold
>>> ON/ OFF (ReInvite with mode sendonly) and Codec
>>> renegotiation (ReInvite with a different codec
>> list)
>>> to be combined in the same transaction (ReInvite
>> with
>>> mode sendonly and different codec list).
>>> Are there any restrictions/ limitations in doing
>> this?
>>> Do most implementations accept/ initiate this
>>> behavior?
>> You are asking if it is permissible to change the
>> directionality 
>> (sendonly, sendrecv, readonly, inactive) of a media
>> stream and the 
>> codecs in a single offer/answer?
>>
>> Yes - its fine to do that.
>>
>> The way you phrase the question suggests you
>> consider the directionality 
>> attributes to simply be a way of communicating the
>> Call Hold feature. 
>> While the directionality attributes can be used to
>> indicate a desired 
>> state due to placing the call on hold, they can also
>> be used for other 
>> purposes.
>>
>>      Paul
>>
> 
> 
> 
>               
> ___________________________________________________________ 
> Inbox full of spam? Get leading spam protection and 1GB storage with All New 
> Yahoo! Mail. http://uk.docs.yahoo.com/nowyoucan.html
> 
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

Reply via email to