[OpenSIPS-Users] telephone-event rtpmap value

[solarmon]

Hi,

Yes, the client is broken. It advertises RFC2833 in the SDP but does not
send and RTP Events for the DTMF tones and just sends it inband, and the
other end does not like it (it doesn't for some reason fall back to inband
DTMF).

The workaround I have used is to remove the RFC2833 bits in the SDP packet
by using the replace_body() function.

Thank you.

On Tue, 31 Mar 2020 at 13:23, Răzvan Crainea <razvan at opensips.org> wrote:

> This sounds a bit broken: if the client advertises the payload type of
> 96, thats what it will have in the generated RTP packets, so I don't
> really see a valid reason for doing that. Unless the client is really
> broken and advertises a ptype of 96, but sends the packets using 101.
>
> Anyhow, in order to do that, you can use the subst_body() function in
> the textops module:
> https://opensips.org/docs/modules/2.4.x/textops.html#func_subst_body
>
> Best regards,
>
> Răzvan Crainea
> OpenSIPS Core Developer
> http://www.opensips-solutions.com
>
> On 3/27/20 4:43 PM, solarmon wrote:
> > Hi,
> >
> > I have an opensips 2.4 cluster using rtpproxy nodes.
> >
> > I'm troubleshooting some DTMF issue and have a requirement to change the
> > inbound INVITE SDP payload from:
> >
> > a=rtpmap:96 telephone-event/8000
> >
> > to
> >
> > a=rtpmap:101 telephone-event/8000
> >
> > in the outbound INVITE SDP.
> >
> > How could this mapping/conversion be achieved with my opensips/rtpproxy
> > setup?
> >
> > Thank you!
> >
> > _______________________________________________
> > Users mailing list
> > Users at lists.opensips.org
> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20200331/3f094da1/attachment.html>