General
The Vodafone One Fix SIP Trunk from VodafoneZiggo (NL) was first tested and released with a SwyxWare 2013 R4.
The Vodafone One Fix SIP Trunk from VodafoneZiggo (NL) is a registerless SIP trunk. 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 assigned to the SwyxWare server.
The actual interoperability tests were performed by VodafoneZiggo, not by the Enreach TAP.
Platforms
SwyxWare
The Vodafone One Fix SIP Trunk from VodafoneZiggo (NL) can be used without restrictions from SwyxWare 2013R4 on.
SwyxON
The Vodafone One Fix SIP Trunk from VodafoneZiggo (NL) is not released for central connection in the data center.
Configuration
For the Vodafone One Fix SIP Trunk, the profile "VodafoneZiggo VOF (NL)" has to be selected when creating the SIP Trunk group.
Codec Configuration
In the codec dialog, only G.711A and G.729 have to be selected.
Session-Interval
VodafoneZiggo (NL) expects a Session interval of 1800 (seconds) on outbound calls. The prevent reINVITES which would slow down the call establishment, underneath the registry key HKLM\Software\Wow6432Node\Swyx\LinkMgr\CurrentVersion\Options two new DWORD values SipMinSessionTimerIntervalSeconds and SipSessionTimerIntervalSeconds can be created with an assigned value of 1800 (decimal). After creating this value, the LinkMgr service must be restarted.
Important: This setting will affect all SIP Trunks.
Misc.
VodafoneZiggo (NL) is offering SIP trunks for two different services. While Vodafone One Fix (VOF) provides access to the usual public telephone net (PSTN), Corporate Net over IP (CNoIP) is offering access to the mobile telephone network and to so called closed user groups. A customer does not necessarily need both services.
If a customer is using both services, two SIP trunkgroups with the corresponding profile and a respective SIP trunk must be created within the SwyWare. The preconfigured IP address for the proxy server should be checked and modified if necessary. For the CNoIP trunkgroup, two routing records must be cerated:
- For calls into the mobile network: Destination +316* with a priority of 600
- For calls into the Closed Mobile User group. Destination i.e. 7* with a priority of 600 if the user groups covers the number range from 7000 to 7999.
For both trunkgroups, the Calling Right should be set to 'Internal Destinations'.
For the VOF trunk, only G711A and G.729 should be selected as audio codecs; for the CNoIP trunk G711A only.
Tested features
- Incoming/outgoing national calls
- Incoming/outgoing international calls
- Correct Calling Line Identification (CLI) on national and international calls
- Holding and retrieving calls
- Toggeling between two calls
- Call transfer
- Conferencing
- Mutually supported codecs: G.711a/ G.729 (VOF only)/ T.38
- Incoming/outgoing DTMF signaling in accordance with RFC2833
- FAX transmission via T.38
Restrictions
- CLIP No Screening is not allowed in the Netherlands
Tests
04/06/2014 with SwyxWare 2013 R4
09/06/2015 with SwyxWare 2015 R2
07/03/2018 with SwyxWare 11.00.0.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.