Hmmm, indeed, passing SDP as variable to rtpengine is possible only with
3.0 , my bad....too many versions.
This is the commit you are looking for:
https://github.com/OpenSIPS/opensips/commit/a27797d04ba418eb3ac4c2d6dadd0cdf7f3c17b6#diff-069ca6b59f3521936eca7bf3684ae63d
maybe you can grab the module from 3.0 right after that commit and copy
it in 2.4 tree - it may compile.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
https://www.opensips-solutions.com
OpenSIPS Summit 2019
https://www.opensips.org/events/Summit-2019Amsterdam/
On 03/06/2019 10:47 PM, Pat Burke wrote:
Thanks Bogdan,
I see that it is part of 3.0, but not a part of 2.4. Is this a module
we can pull back to 2.4?
Regards,
*Pat Burke*
Voxtelesys | solutions to grow your business
______________________________________________________________________________________
Direct: (402) 403-5121 | Cell: (402) 443-8929 | Email:
[email protected] <mailto:[email protected]>
1801 23rd Avenue North | Suite 217 | Fargo, North Dakota 58102
------------------------------------------------------------------------
-----Original Message-----
From: "Bogdan-Andrei Iancu" <[email protected]
<mailto:[email protected]>>
To: "OpenSIPS users mailling list" <[email protected]
<mailto:[email protected]>>, "Pat Burke"
<[email protected] <mailto:[email protected]>>
Date: 03/05/19 09:45
Subject: Re: [OpenSIPS-Users] SDP manipulation & rtpengine
Hi Pat,
What you can do is to grab the SDP from the msg into a variable,
to do whatever fixes/change you have to directly in the variable
and push the body via variable to rtpengine.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
https://www.opensips-solutions.comOpenSIPS Summit 2019
https://www.opensips.org/events/Summit-2019Amsterdam/
On 02/27/2019 11:30 PM, Pat Burke wrote:
Hello:
I am using trying to manipulate parts of the SDP body before
calling rtpengine_offer / rtpengine_answer. However, any changes
made via textops functions such as subst_body, replace_body,
replace_body_all, etc. do not seem to impact the SDP that is sent
to rtpengine.
In my particular case, rtpengine fails to parse the SDP because
of an extra carriage return line feed sent in the SDP. Is there a
way to send rtpengine manipulated SDP, rather than just the SDP
sent in the request?
*_Use case:_*
if (subst_body("/(^a=.*\r\n)\r\n/\1/g")) {
xlog("L_INFO", "bad SDP --- duplicate CRLF");
}
rtpengine_offer(" ... options ... ");
Regards,
*Pat Burke*
Voxtelesys | solutions to grow your business
______________________________________________________________________________________
Direct: (402) 403-5121 | Cell: (402) 443-8929 | Email:
[email protected] <mailto:[email protected]>
1801 23rd Avenue North | Suite 217 | Fargo, North Dakota 58102
_______________________________________________
Users mailing
[email protected]http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
