The SIP Trunk from EmslandTel.net was first tested and released with a SwyxWare 11.00.
EmslandTel.net is offering SIP trunks with and without user authentication. The tested SIP Trunk is without user authenication, this means that the authentication is based on the public IP address of the SwyxWare server. Therefore, you need a static, public IP address from your ISP.
The SIP Trunk from EmslandTel.net can be used according to the settings listed below from SwyxWare 13.10 on. If you use an earlier version of SwyxWare, incompatibilities cannot be excluded and you are responsible for your own usage.
The SIP Trunk from EmslandTel.net is not released for central connection in the data center.
During creation of the SIP trunkgroup, profile'ETN VoIP (DE)' has to be selected.
Important: In case that the SwyxWare server is running with a private IP address and the static, public IP address is provided by NAT gateway, it is necessary to configure a STUN server in the properties of the SIP trunk group, under the tab 'SIP'. A list of public STUN servers can e.g. be found at http://www.voip-info.org/wiki/view/STUN. In this case, it is necessary to configure the correct portwarding in the NAT gateway, such that inbound SIP requests are being forwarded to port 65002 of the SwyxWare server.
If no NAT gateway is necessary, the provider has to be consider that inbound SIP requests are being directly sent to port 65002 of the SwyxWare server.
- 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
- Mutually supported codecs:
- T.38 for FAX Negotiation
- Incoming/outgoing DTMF signaling in accordance with via RFC2833
- Fax transmission via T.38
09/01/2018 with SwyxWare 11.00.1.0
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.