[OpenSIPS-Users] RFC2833 to INFO

[Mark Farmer]

Hi Alain

Yes. Sounds like you have experience?

Mark



On Mon, 18 Mar 2019 at 17:37, Alain Bieuzent <alain.bieuzent at free.fr> wrote:

> I mark,
>
>
>
> Do you made test with PCIPAL ?
>
>
>
> Regards
>
>
>
> *De : *Users <users-bounces at lists.opensips.org> au nom de Mark Farmer <
> farmorg at gmail.com>
> *Répondre à : *OpenSIPS users mailling list <users at lists.opensips.org>
> *Date : *lundi 18 mars 2019 à 17:19
> *À : *Bogdan-Andrei Iancu <bogdan at opensips.org>
> *Cc : *OpenSIPS users mailling list <users at lists.opensips.org>
> *Objet : *Re: [OpenSIPS-Users] RFC2833 to INFO
>
>
>
> Thanks Bogdan. I was beginning to fear as much but I do need a solution
> for this. I will try to explain the problem in more detail.
>
>
>
> Our 3rd party is a secure payment gateway and only receives audio
> following a SIP RE-INVITE. This is to re-route the audio so that DTMF tones
> can be removed. At this point the DTMF is required to be transmitted to the
> 3rd party as SIP INFO messages. Once the payment process is complete, there
> is another SIP RE-INVITE to switch the audio back to it's original path.
>
>
>
> What I have is OpenSIPS & RTPProxy combination but this is a PoC platform
> so I can change things. Is there a method to have an RTP proxy instruct
> OpenSIPS to generate SIP INFO messages and send them to the 3rd party? It
> doesn't matter if we end up with both RFC2833 and SIP INFO - the 3rd party
> will just act on the INFO messages.
>
>
>
> TIA
>
> Mark.
>
>
>
>
>
> On Mon, 18 Mar 2019 at 15:37, Bogdan-Andrei Iancu <bogdan at opensips.org>
> wrote:
>
> Hi Mark,
>
> You cannot do this with OpenSIPS, mainly as OpenSIPS has no access to RTP
> in order to "see" the RFC2833 DTMFs.
>
> 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/18/2019 04:24 PM, Mark Farmer wrote:
>
> Hi everyone
>
>
>
> I have an OpenSIPS server with trunks to a provider and to a 3rd party and
> routing calls between the two. The provider sends DTMF as RFC2833 but the
> 3rd party requires SIP INFO. Somehow I need to translate from RFC2833 to
> SIP INFO - is this possible?
>
>
>
> Many thanks
>
> Mark.
>
>
>
> --
>
> Mark Farmer
> farmorg at gmail.com
>
>
>
> _______________________________________________
>
> Users mailing list
>
> Users at lists.opensips.org
>
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
>
>
>
> --
>
> Mark Farmer
> farmorg at gmail.com
>
> _______________________________________________ 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
>
-- 
Mark Farmer
farmorg at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20190318/055815cf/attachment.html>