[Spce-user] T.38 <-> G.711 Transcoding

[Gabriel Kuri]

Hi Raul,

I suppose I misunderstood the transcoding capability in rtpengine, I
thought it handled T.38 to G.711 transcoding in recent versions.

Any recommendations on a full T38 gateway that handles full T.38 <--> G.711
transcoding?

Thanks ...

On Mon, Aug 31, 2020 at 10:37 PM Raúl Alexis Betancor Santana <
rabs at dimension-virtual.com> wrote:

> No, rtpengine lacks that transcoding capabilitie, for that you need a full
> T38 Gateway
>
> ------------------------------
> *From: *"Gabriel Kuri" <gkuri at ieee.org>
> *To: *"spce-user" <spce-user at lists.sipwise.com>
> *Sent: *Monday, August 31, 2020 5:56:05 PM
> *Subject: *[Spce-user] T.38 <-> G.711 Transcoding
>
> Is it possible for C5 CE (using rtpengine) to transcode between T.38
> (a-leg) and G.711 (b-leg) ?
>
> I've tried setting it up, but I can't figure out how to set the media
> settings facing each leg (t38_force, t38_decode. etc.).
>
> Here's the scenario ...
>
> A-leg (T.38): Analog Telephone Adapter
> B-leg (G.711): Carrier SIP Trunk
>
> On the A-leg, it would be good if we could force C5 CE to Re-INVITE T.38
> to the ATA immediately at the start of the call. But not sure if C5 CE can
> do the Re-INVITE or if it must come from the ATA?
>
> On the B-leg, it would be good if we could stay on G.711 and refuse any
> T.38 Re-INVITES that may come in from the carrier?
>
> Thanks!
>
> --
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20200831/254c604d/attachment-0002.html>