Re: [Sip-implementors] Need Urgent Help for Codec issue

2015-04-22 Thread NK
Dear All, Thank you very much for your help its clear my doubt and problem is fixed. On Tue, Apr 21, 2015 at 1:37 AM, ashish rawat wrote: > Hi Nitin, > > Yes that is correct! ( Based on the media > direction.send-recv,recvonly,sendonly) > > I once again pasting the same RFC, I think this has

Re: [Sip-implementors] Need Urgent Help for Codec issue

2015-04-21 Thread Paul Kyzivat
On 4/21/15 4:37 AM, ashish rawat wrote: Hi Nitin, Yes that is correct! ( Based on the media direction.send-recv,recvonly,sendonly) I once again pasting the same RFC, I think this has the answer to your question. https://www.ietf.org/rfc/rfc3264.txt Offerer Processing of the Answer When t

Re: [Sip-implementors] Need Urgent Help for Codec issue

2015-04-21 Thread ashish rawat
Hi Nitin, Yes that is correct! ( Based on the media direction.send-recv,recvonly,sendonly) I once again pasting the same RFC, I think this has the answer to your question. https://www.ietf.org/rfc/rfc3264.txt Offerer Processing of the Answer    When the offerer receives the answer, it MAY send med

Re: [Sip-implementors] Need Urgent Help for Codec issue

2015-04-20 Thread NK
Hi Paul, Your explanation making sense to me. As you said. - If X offers two codecs, and Y answers with both of those, then there is no choice of codec. Either side can send either codec at any time. # Is that mean, if "Y" replied with 2 codec and so any codec can be use by X (it will not accep

Re: [Sip-implementors] Need Urgent Help for Codec issue

2015-04-20 Thread Paul Kyzivat
Anish, It is a little hard to follow you, but I think you still aren't "getting" how it works. - If X offers two codecs, and Y answers with both of those, then there is no choice of codec. Either side can send either codec at any time. - If X offers two codecs and Y answers with one of th

Re: [Sip-implementors] Need Urgent Help for Codec issue

2015-04-20 Thread NK
Hi Ashish, Thanks for the information. But Michael replied it is clear to me now, but its created 1 confusion as below. Can anyone please help me to get the answer on this. Ideally when we have multiple codec from UAS in 183 or 180 so ideally UAC accept the first codec whatever is there in "m" li

Re: [Sip-implementors] Need Urgent Help for Codec issue

2015-04-18 Thread ashish rawat
Hi Nitin, I think it is valid to change the codec on fly. We often see it during DTMF RFC2833.here isn't any change in existing offer. It's using one of listed codes in the offer/answer ealier. https://www.ietf.org/rfc/rfc3264.txt  The reason this is a SHOULD, and not a MUST (its also a SHOUL

Re: [Sip-implementors] Need Urgent Help for Codec issue

2015-04-17 Thread Dale R. Worley
NK writes: > I assume that when we have multiple codec in Answer then UAC select First > In First out method(i mean it will select the first codec) Your mistake is to talk about "selecting" a codec. If the SDP has listed more than one codec, a UA may use any of the listed codecs *at any time*.

Re: [Sip-implementors] Need Urgent Help for Codec issue

2015-04-17 Thread NK
Hi Michael, Thanks for a lot for you reply. Its making sense to me, however its created 1 confusion to me. As you can ideally when we have multiple codec from UAS in 183 or 180 so ideally UAC accept the first codec whatever is there in "m" line and as far as i know if we have change any codec bef

Re: [Sip-implementors] Need Urgent Help for Codec issue

2015-04-17 Thread Michael Bain
Yes this is valid. When you make an SDP offer, you are saying you are willing to receive any of those codecs at anytime during the session. See the third paragraph of this section: http://tools.ietf.org/html/rfc3264#section-5.1 "If multiple formats are listed, it means that the offerer is capable

[Sip-implementors] Need Urgent Help for Codec issue

2015-04-17 Thread NK
Dear All, I am facing the problem where my vendor changed the codec in RTP packet only. Below is the explanation to this issue. 1) We sent the Invite to vendor and Vendor replied 183 w/SDP along with below m line. Also since its early media RTP started and agreed to use G729 Codec as below and UA