The Business Voice SIP Trunk from T-Mobile Austria was first tested and released with a Swyxware 12.00
T-Mobile Austria is offering the Business Voice SIP Trunk with user authentication. You have received information about UserID, UserName and UserPassword, whereas the naming may differ, or you might have only received UserName and -password. In this case, UserID and UserName are identical. Besides, you need an IP address which was assigned by UPC and which gets connected to the SIP trunk.
The actual interoperability tests were performed by the company Data-Way, not by Swyx TAP.
The Business Voice SIP Trunk from T-Mobile Austria can be used without restrictions with SwyxWare 12.00 or higher. When using an earlier version of SwyxWare, incompatibilities cannot be excluded and use is at your own responsibility.
The Business Voice SIP Trunk from T-Mobile Austria is not suitable for central connection in the data center due to its dependence on the assigned IP address.
Numberblock: +43 662 1234560 ... +43 662 1234569
In this case, the SIP URI must be entered in the format 0662123456*@*.
Exclude G.722 in the Codecs/Channel tab of the Trunk Properties dialog.
Support for T.38 and FAX transmission must explicitely be requested from T-Mobile Austria .
On outgoing calls T-Mobile Austria changes some characteristica of the RTP stream call setup and call answering. This may lead to a oneway voicechannel if internal encryption is active. Therefore, in the tab "Encryption" of the SwyxServer properties, you have to deactivate internal encryption.
Support for feature CLIP No SCreening must explicitely be requested from T-Mobile Austria .
There is a dedicated Swyx profile for the Transcoding Gateway from T-Mobile Austria in order to transmit T.38 and DTMF. This must be activated on the UPC side when configuring the trunk.
- Incoming/outgoing national calls
- Incoming/outgoing international calls
- Correct Calling Line Identificaion (CLI) on national and international calls
- Holding and retrieving calls
- Toggeling between two calls
- Call transfer
- Mutually supported codecs: G.711a/G.711µ/G.729/ T.38 for FAX Transmission
- Incoming/outgoing DTMF signaling in accordance with via RFC2833
- T.38 negotiation and FAX transmission
- Deactivation of internal encryption necessary
- Support for feature CLIP No Screening must explicitely be ordered
- Support for T.38 must explicitely be ordered
16.12.2019 with SwyxWare 12.00
Verifying interoperability between different SIP providers and the Swyx solution is part of the Enreach Technology Alliance Programme (TAP) tasks. Due to different implementations of the SIP RFCs, it is necessary to determine and provide an individual configuration for each SIP provider.
Within the TAP, Enreach tests a large number of national and international SIP providers in order to make statements about the interoperability with the Swyx solution and the functional scope of the respective SIP trunk. These results and, if needed, configuration advice are published in Help Center articles.
Enreach is in close contact with selected SIP providers to ensure a quick troubleshooting in case of incompatibilities. In addition, tests are repeated at regular intervals to ensure consistent quality.
Despite regular retests it cannot be excluded that incompatibilities with the Swyx solution may occur due to changes in the SIP connection on the provider side or that the provided profile is no longer valid. After creating the trunk group or SIP trunk, the profile settings should be compared with the provider's information and adjusted accordingly in case of deviations.
However, should incompatibilities or problems occur with a tested SIP trunk, no claims for recourse against Enreach GmbH can be derived from this. In such cases, you can contact Enreach Support via your specialist dealer.
The third-party contact information included in this article is provided to help you find the technical support you need. This contact information is subject to change without notice. Swyx in no way guarantees the accuracy of this third-party contact information nor is responsible for it's content.
Please sign in to leave a comment.