Hi, Vinayak!
OpenSIPS does not do transcoding, RTPEngine does it, OpenSIPS simply
passes in SDP whatever RTPengine was instructed to do.
If I understand your question, you want want to keep the two DTMF codecs
on the offering side, but offer a new one (101) on the other side. I've
never done this, but what I would try is to first mask the offered
codecs, and transcode the one I want. This would result in the following
parameters:
rtpengine_offer("codec-mask-telephone-event/8000
codec-mask-telephone-event/16000 transcode-telephone-event/8000");
Posting the inbound and outbound SDPs might be helpful in case this does
not work. But again, I am no expert in trans-coding and/or RTPengine,
this is just what I would try myself.
Best regards,
Răzvan
On 9/24/24 9:00 AM, Bogdan-Andrei Iancu wrote:
Hi, This sounds more like an rtpengine question, rather than an opensips
one :(. Hopefully someone here will be able to assist, you never know :)
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
https://www.opensips-solutions.com
https://www.siphub.com
On 07.09.2024 09:46, Vinayak Makwana via Users wrote:
Hi all,
I am trying to transcoding for a specific
DTMF telephone-event from opensips +rtpengine. I am using opensips
3.2.12.
Here's Call scenario :
Initial INVITE SDP ---> OpenSIPS
* a=rtpmap:105 telephone-event/16000
a=rtpmap:100 telephone-event/8000*
From opensips i want to add below DTMF payload 101 because B party is
accepting this DTMF payload type.
*a=rtpmap:101 telephone-event/8000 *i am using below code.
* rtpengine_offer("transcode-telephone-event/8000");*
By using this function opensips does not transcode specific DTMF
payload 101.
Is there any way to achieve this transcoding ?
Please let me know.
Regards,
Vinayak Makwana
*https://www.ecosmob.com/ucx-expo/ <https://www.ecosmob.com/ucx-expo/>
*
*Disclaimer*
In addition to generic Disclaimer which you have agreed on our
website, any views or opinions presented in this email are solely
those of the originator and do not necessarily represent those of the
Company or its sister concerns. Any liability (in negligence, contract
or otherwise) arising from any third party taking any action, or
refraining from taking any action on the basis of any of the
information contained in this email is hereby excluded.
*Confidentiality*
This communication (including any attachment/s) is intended only for
the use of the addressee(s) and contains information that is
PRIVILEGED AND CONFIDENTIAL. Unauthorized reading, dissemination,
distribution, or copying of this communication is prohibited. Please
inform originator if you have received it in error.
*Caution for viruses, malware etc.*
This communication, including any attachments, may not be free of
viruses, trojans, similar or new contaminants/malware, interceptions
or interference, and may not be compatible with your systems. You
shall carry out virus/malware scanning on your own before opening any
attachment to this e-mail. The sender of this e-mail and Company
including its sister concerns shall not be liable for any damage that
may incur to you as a result of viruses, incompleteness of this
message, a delay in receipt of this message or any other computer
problems.
_______________________________________________
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
--
Răzvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
