Hello,

I dont think rtpengine_manage() does automatically rtpengine on 4xx.

You have to explicitly do it. Bécasse rtpengine Can not decide if 4xx is for initial invite or reinvite failure.


My advise use rtpengine_offer and rtpengine_answer and rtpengine_delete instead of rtpengine_manage.

Le 21 avr. 2023 08:53, Benoît Panizzon <benoit.panizzon@imp.ch> a écrit :

Hi all

I wonder, if there is a documentation on what action is performed by
rtpengine_manage() on which kind reply.

Am I right, that rtpengine_manage(), on any 4XX reply causes a delete?

So if there is a re-invite (for example to switch to T.38) and the
other party replies with 488 which in turn is passed through
rtpengine_manage() the existing RTP stream is deleted from rtpengine
instead of being left running with the previously agreed codec?

Has anyone already figured out a list of what reply codes should be
exempt from calling rtpengine_manage()?

--
Mit freundlichen Grüssen

-Benoît Panizzon- @ HomeOffice und normal erreichbar
--
I m p r o W a r e   A G    -    Leiter Commerce Kunden
______________________________________________________

Zurlindenstrasse 29             Tel  +41 61 826 93 00
CH-4133 Pratteln                Fax  +41 61 826 93 01
Schweiz                         Web  http://www.imp.ch
______________________________________________________
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-leave@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe: