The SIP Trunk from Node4 was first tested and released with a SwyxWare 2011R2.
The SIP Trunk from Node4 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 SIP Trunk from Node4 can be used according to the settings listed below from SwyxWare 2011R2.
The SIP Trunk from Node4 is not released for central connection in the data center.
During creation of the SIP Trunk Group, the profile 'Node4 (UK)' must be selected.
Node4 is operating with a number of different servers. Therefore it is not possible to preconfigure the Proxy Server in the "SIP" tab of the Trunkgroup Properties dialog. In this field, please enter the IP address that Node4 has named you.
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.
Node4 expects a Session interval of 600 (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 600 (decimal). After creating this value, the LinkMgr service must be restarted.
Important: This setting will affect all SIP Trunks.
For FAX transmission it is necessary to select the option 'Remove T.38 codec from initial invite' in the codec settings of the trunk properties.
- Incoming/outgoing national calls
- Incoming/outgoing international calls
- Correct Calling Line Identification (CLI) on national and international calls
- CLIP No Screening in accordance with RFC3325
- Holding and retrieving calls
- Toggeling between two calls
- Call transfer
- Mutually supported codecs: G.711a/ G.711µ/ G.729/ T.38 for FAX Negotiation
- Incoming/outgoing DTMF signaling in accordance with via RFC2833
- T.38 Negotiation and FAX Transmission
- Occasionally, problems with correct CLI were observed with international calls.
- Due to the different servers that Node4 is running, interoperability issues may occur, that are currently unknown.
06/09/2012 with SwyxWare2011R2, QF3
09/07/2013 with SwyxWare2013
06/11/2014 with SwyxWare2015
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.