General
The SIP Trunk from IP Austria was first tested and released with a SwyxWare 2015 R40.
The SIP Trunk from IP Austria is available in 54 countries, including the porting of call numbers. For internationally linked installations, call numbers from different countries can be offered on one single SIP trunk.
The IP Austria SIP DDI trunk is a SIP trunk with user authentication. You have received information about UserID, UserName and UserPassword, whereas the naming may differ, or you have only received UserName and -password. In this case, UserID and UserName are identical.
IP Austria is operating with a number of different servers. Therefore it is not possible to preconfigure the Registrar / Proxy Server in the "SIP" tab of the Trunkgroup Properties dialog. In field of Registrar / Proxy Server, please enter the server name or IP address provided by IP Austria.
Platforms
SwyxWare
The SIP Trunk of IP Austria can be used according to the settings listed below from SwyxWare 2015 R40.
SwyxON
The SIP Trunk of IP Austria is not released for central connection in the data center.
Configuration
During creation of the SIP Trunkgroup, profile 'IP Austria (AT)' has to be selected.
Codec Configuration
In the codec dialog for FAX transmission via T.38 the two options "Remove T.38 codec from initial invite" and "Prohibit T.38 reinvite by sender" must be activated.
SIP URIs
In order to assign incoming calls to the correct trunk, it is necessary to configure a SIP URI for the trunk. The assigned number block and the numberformat must be considered.
Numberblock: +43 40 1234560 ... +43 40 1234569
In this case, the SIP URI must be entered in the format 4340123456*@*.
A connection to an IP Austria SIP trunk requires a STUN server, which is provided by IP Austria themselves. This STUN server uses the default port 3478. The networking environment (NAT, firewall) has to allow communication with that port.
Tested Features
- Incoming/outgoing national calls
- Incoming/outgoing international calls
- Correct Calling Line Identification (CLI) on national and international calls
- CLIP No Screening
- Holding and retrieving calls
- Toggeling between two calls
- Call transfer
- Conferencing
- Mutually supported codecs:
- G.711A
- G.729
- Incoming/outgoing DTMF signaling in accordance with via RFC2833
- FAX transmission via T.38
Restrictions
None
Tests
16/05/2024 with SwyxWare 14.00
24/10/2023 with SwyxWare 13.29
20/06/2017 with SwyxWare 2015 R40.3.0
Disclaimer
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.
Comments
0 comments
Please sign in to leave a comment.