Benoit,

I think the most comprehensive answer for how rtpengine_manage is working is actually looking at the code, it's quite easy to read

https://github.com/kamailio/kamailio/blob/b65c19fa29976b59403433ed8a5de4b7eef41afc/src/modules/rtpengine/rtpengine.c#L3866

In your case (failed reINVITE), I'd preform a test, cause rtoengine_delete() is called in this case according to a source code. And than it's really rtpengine itself will decide what to do with the stream, fallback or delete.

Le ven. 21 avr. 2023 à 11:34, 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: