The SIP Connect Trunk from Netvoip was first tested and released with a SwyxWare 13.10.
Netvoip offers a SIP Trunk with User Authentication, i.e. you receive information about UserID, UserName and UserPassword from Netvoip. The names can be different, or you receive only the user name and password. In this case the UserID is identical with the UserName.
The SIP Connect Trunk from Netvoip 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 Connect Trunk from Netvoip is not released for central connection in the data center.
During creation of the SIP trunk group, profile 'Netvoip (CH)' must be selected. If the profile is not included in the corresponding list, you can download the required CustomProviderProfiles.config for SwyxWare at the end of this article. For more information about using this file, see Configuration and Adaptation of SIP Providers via Provider Profiles.
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: +41 61 9988776600 ... +41 61 9988776699
In this case, the SIP URI must be configured in the format 06199887766*@*.
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.
- 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:
- Incoming/outgoing DTMF signaling in accordance with via RFC2833
- Fax transmission via G.711
08.04.2022 with SwyxWare 13.10
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.