General
The SIP Trunk from EWETEL (swb/osnatel NGN) was first tested and released with a SwyxWare 2014R40.
The EWETEL (swb/osnatel NGN) trunk is a SIP trunk with user authentication. You have received information about UserID, UserName and UserPassword, whereas the nameing may differ, or you have only received UserName and -password. In this case, UserID and UserName are identical. Usually, a customer also obtains his internet access from EWE.
EWETEL (swb/osnatel NGN) offers on the one hand a SIP trunk which can only be connected via internet connections of EWETEL (swb/osnatel NGN) and on the other hand a SIP trunk which can be connected via any internet connection.
Platforms
SwyxWare
The SIP Trunk from EWETEL (swb/osnatel NGN) can be used according to the settings listed below from SwyxWare 2014R40 on.
SwyxON
The SIP Trunk from EWETEL (swb/osnatel NGN) is released for central connection in the data center.
Configuration
If the connection is made via an Internet connection from EWETEL (swb/osnatel NGN), 'EWE/swb/osnatel NGN (DE)' must be selected as the profile when creating the SIP trunk group.
If the connection is made via any Internet connection, 'EWE/swb/osnatel NGN Ext. (DE)' must be selected as profile when creating the SIP Trunkgroup. This profile is only available with SwyxWare 13.27 or higher. For previous versions the profile 'EWE/swb/osnatel NGN (DE)' must be selected. Finally, in the properties of the SIP trunk group in the tab 'SIP' the value for registrar and proxy has to be changed from 'siptrunk3.voice.ewetel.de' to 'ext-siptrunk3.voice.ewetel.de'.
SIP URIs
In order to assign incoming calls to the correct trunk, it is necessary to configure a SIP URI for the trunk during the creation of the actual trunk. The assigned number block and the numberformat must be considered.
Example:
Numberblock: +49 441 1234560 ... +49 441 1234569
In this case, the SIP URI must be entered in the format +49441123456*@*.
This configuration can also be made after the trunk was already created in the properties of the SIP trunk, underneath the 'SIP-URIs' tab. In this case, the LinkMgr service has to be restarted.
Codec Configuration
During creation of the actual trunk, in the codec configuration dialog, T.38 has to be deselected as supported codec. This step could also be performed afterwards in the properties of the SIP trunk, underneath the 'Codecs' tab.
CLIP No Screening
To activate the feature CLIP No screening in the SwyxWare, it is necessary to set the option "Always use originator's number" in the tab "Number signalling" of the SIP trunk settings.
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.722
- G.711A
- G.711u
- Incoming/outgoing DTMF signaling in accordance with via RFC2833
- FAX transmission via G.711
Restrictions
None
Test Dates
03/03/2023 with SwyxWare 13.25
20/11/2017 with SwyxWare 11.00.1.1
03/07/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.