Hi Alexey, Yes, you are right. The session should be kept with G711a unless there is a bug in your system.
Best regards, Xin On Fri, 9 Feb 2018 at 11:19, Alexey <ale...@12connect.nl> wrote: > Good morning. > I have an issue for following call flow : > MGC 8 -> pjsip > > INVITE > .... > < OK > >ACK > ...established rtp g711a... > < re-INVITE T.38 attempt to switch to t.38 > > 100 > >488 Not acceptable here > <ACK > After this ACK my provider required me send re-invite with G711a but in > my opinion session which use g.711a already exist and attempt to change > it failed so session have to continue with with previous negotiated codec. > Beside this in accordance with RFC 3261 : > "If the other party does not accept the change, he sends an error > response such as 488 (Not Acceptable Here), which also receives an ACK. > However, the failure of the re-INVITE does not cause the existing call > to fail - the session continues using the previously negotiated > characteristics." > > Do i am right that re-invite in NOT mandatory by standard to continue > call with previous established RTP session ? > > > > > > > > > > > > > _______________________________________________ > Sip-implementors mailing list > Sipemail@example.com > https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors > _______________________________________________ Sip-implementors mailing list Sipfirstname.lastname@example.org https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors