Re: [Sip-implementors] Codec Negotiation issue

Rakesh writes: > SECOND CASE: > * User B put in Hold User A > * User B sends REINVITE with sendonly containing only EVS, > * REINVITE arrives to User A with sendonly and it contains all the VoLTE > codecsin the following order: AMR WB, EVS, AMR NB. > * User A answer with 200 OK

Re: [Sip-implementors] Codec Negotiation issue

On 2/22/18 3:34 AM, Rakesh wrote: Hi Expert, I have a scenario here can anyone help me to undrstand is the behaviour is correct on both cases? FIRST CASE: • User A calls User B • Negoziation for EVS codec • User A put in hold User B • REINVITE from User A, contains sendonly, with only EVS

Re: [Sip-implementors] Codec Negotiation issue

Hi Asim, It is not answer to my question since the section that you refer is not answering my above question. I am aware of this already. Thanks. I need to know any specific order or priority to handle the coded and why not all codec listed is not send back in answer as both A and B support all

Re: [Sip-implementors] Codec Negotiation issue

Please have a look to RFC 4317 and Section 2 Regards, Asim Sulaiman From: sip-implementors-boun...@lists.cs.columbia.edu [sip-implementors-boun...@lists.cs.columbia.edu] on behalf of Rakesh [rak...@gmail.com] Sent: Thursday, February 22, 2018 12:34 PM

[Sip-implementors] Codec Negotiation issue

Hi Expert, I have a scenario here can anyone help me to undrstand is the behaviour is correct on both cases? FIRST CASE: • User A calls User B • Negoziation for EVS codec • User A put in hold User B • REINVITE from User A, contains sendonly, with only EVS (codec negotiated and used). • REINVITE