Hi Wadii,
I haven;t checked the implementation, but the rtpproxy_engage should
take care of the 183 with SDP. Have you tested it?
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
https://www.opensips-solutions.com
OpenSIPS Bootcamp 5-16 Dec 2022, online
https://www.opensips.org/training/OpenSIPS_eBootcamp_2022/
On 12/23/22 9:42 PM, Wadii ELMAJDI | Evenmedia wrote:
hello , i do have a question related to rtpproxy module documentation.
The doc describes that rewriting sdp body should happen during either
INVITE , 200 OK or ACK.
In the case of SDP presence on invite <=> 200 , one should
rtpproxy_offer during the invite and rtpproxy_answer during the 200 OK.
"Documentation : RewritesSDPbody to ensure that media is passed
through anRTPproxy. To be invoked on INVITE for the cases the SDPs are
in INVITE and 200 OK and on 200 OK when SDPs are in 200 OK and ACK."
But sometimes opensips receives a 183 Session Progress containing SDP
before the 200 which i think is related to earlymedia .
I think those sdp packets should also be rewritten with the right rtp
proxy ip/port. In which case the doc should mention "SDPs are in
INVITE and 200 OK /183 Session Progress".
My second question : since we can handle most cases with
rtpproxy_offer/answer methods, what is the purpose of rtpproxy_engage
? is it to ease the management i described above ?
Thank you
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
