The SIP Trunk from DNS:NET was first tested and released with SwyxWare 184.108.40.206.
The SIP Trunk from DNS:NET is a SIP Trunk with user authentication, i.e. you receive information on user ID, user name and password. The names may differ, or you may only receive a name or ID with password. In this case the user ID is identical to the user name when configuring the SIP trunk in SwyxWare.
The SIP Trunk from DNS:NET can be used from SwyxWare 220.127.116.11 on. When using an earlier version of SwyxWare incompatibilities cannot be excluded and use is at your own risk.
The SIP Trunk from DNS:NET is suitable for central connection in the data center.
When creating the SIP trunk group, select the profile 'DNS:NET (DE)'.
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: +49 40 1234560 ... +49 40 1234569
In this case, the SIP URI must be entered in the format 4940123456*@*.
Afterwards, the LinkMgr service has to be restarted.
A connection to DNS:NET trunk requires a STUN server, which is provided by DNS:NET themselves. This STUN server uses the default port 3478. The networking environment (NAT, firewall) has to allow communication with that port.
- Incoming/outgoing national /international calls
- Correct Calling Line Identification (CLI) on national / intenational calls
- Holding and retrieving calls
- Toggeling between two calls
- Call transfer
- Call forwarding
- Mutually supported codecs: G.722/ G.711a/ G.711u/ G.729
- Incoming/outgoing DTMF signaling in accordance with via RFC2833
- FAX transmission via T.38/G.711
- CLIP No Screening is currently not possible
- FAX transmission on inbound FAX is done via G.711
12/03/2019 with SwyxWare 18.104.22.168
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.