Node4 is offering registerless SIP trunks. 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.
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 GammaTelecom has named you.
During creation of the SIP Trunk Group, the profile 'Node4 (UK)' must be selected.
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.
GammaTelecom 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:
- 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