[Spce-user] T.38 to G.711a transcoding for peerings and vice versa

Daniel Grotti dgrotti at sipwise.com
Thu Nov 15 06:00:27 EST 2018


Hi,
frankly I don't see the problem.
I would just enable t.38 anyway, in case the t38 re-negotiation fails 
(e.g with your peering server) the fax should go in G711, as falback.



-- 
Daniel Grotti
Head of Customer Support
Sipwise GmbH, Campus 21/Europaring F15
AT-2345 Brunn am Gebirge

Office: +43(0)130120332
Email: dgrotti at sipwise.com
Website: https://www.sipwise.com

On 11/15/18 11:45 AM, Hohl Matthias wrote:
>
> Hello,
>
> Today I got the information that A1 Telekom is not supporting T.38 in 
> there IC network.
>
> Only if the traffic is a Transit Call, T.38 will be supported as 
> “Pass-Through”.
>
> All other Fax Calls with a Reinvite to T.38 will be “not acceptable here”.
>
> For better fax stability I want to allow T.38 for my subscribers.
>
> Therefore I want to allow T.38 just on subscriber side. On peering 
> side, T.38 has to be transcoded to G.711a, if the destination network 
> is A1 Telekom. Also if a FAX comes from A1 with G.711a it should be 
> transcoded to T.38 for our subscribers, of the subscriber support T.38.
>
> IS it possible to implement this transcoding option in any way on the 
> SPCE mr6.5.1? Maybe with a SEMS patch?
>
> Would be nice if someone has an idea to solve this 😊
>
> Mit freundlichen Grüßen,
>
> Matthias Hohl
>
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20181115/e97a15c3/attachment-0001.html>


More information about the Spce-user mailing list