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

Thu Aug 8 12:56:41 EDT 2019

Hello,

do you have any update for me on this topic?

Von: Spce-user <spce-user-bounces at lists.sipwise.com> Im Auftrag von Hohl Matthias
Gesendet: Donnerstag, 15. November 2018 13:26
An: 'Daniel Grotti' <dgrotti at sipwise.com>; spce-user at lists.sipwise.com
Betreff: Re: [Spce-user] T.38 to G.711a transcoding for peerings and vice versa

Hello Daniel,

I believe it would be a problem on subscriber side:

>From SPCE to Peering Server with G.711a for faxing would be less problem because the transport will be with Sync-Ethernet and with direct peering connection.

But between subscriber PBX and SPCE there is often any kind of internet connection possible, and for this reason I think T.38 (leg from subscriber to SPCE) would make the things more stable like  G.711a.

So I think T.38 on subscriber side and G.711a on Peering side would be the most effective way to have successful fax services. Therefore SPCE has to transcode T.38 to G.711a for the peering or G.711a to T.38 for subscriber if the subscriber is supporting it.

I hope I descriped it now better 😊

Von: Spce-user <spce-user-bounces at lists.sipwise.com <mailto:spce-user-bounces at lists.sipwise.com> > Im Auftrag von Daniel Grotti
Gesendet: Donnerstag, 15. November 2018 12:00
An: spce-user at lists.sipwise.com <mailto:spce-user at lists.sipwise.com> 
Betreff: Re: [Spce-user] T.38 to G.711a transcoding for peerings and vice versa

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 <mailto: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 <mailto: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/mailman/private/spce-user_lists.sipwise.com/attachments/20190808/f03f6bef/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5585 bytes
Desc: not available
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20190808/f03f6bef/attachment.p7s>