The SIP Trunk from DNS:NET was first tested and released with SwyxWare 11.32.0.0.
The SIP Trunk from DNS:NET is a SIP Trunk with user authentication, i.e. you receive information on user ID, user name and password. The names may differ, or you may only receive a name or ID with password. In this case the user ID is identical to the user name when configuring the SIP trunk in SwyxWare.
Platforms
SwyxWare
The SIP Trunk from DNS:NET can be used from SwyxWare 11.32.0.0 on. When using an earlier version of SwyxWare incompatibilities cannot be excluded and use is at your own risk.
SwyxON
The SIP Trunk from DNS:NET is suitable for central connection in the data center.
Configration
When creating the SIP trunk group, select the profile 'DNS:NET (DE)'. 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.
SIP URIs
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: +49 40 1234560 ... +49 40 1234569
In this case, the SIP URI must be entered in the format 4940123456*@*.
Afterwards, the LinkMgr service has to be restarted.
STUN
A connection to DNS:NET trunk requires a STUN server, which is provided by DNS:NET themselves. This STUN server uses the default port 3478. The networking environment (NAT, firewall) has to allow communication with that port.
NAT
To avoid the NAT binding time-out problems, one of the two solutions has to be applied:
- Increasing the UDP timeout on the NAT gateway to a greater value than the registration interval of 180 seconds.
- Activating the keep-alive packets with a time interval less than the UDP timeout of the used NAT gateway. The actual value depends on the NAT gateway configuration.
Use the following power shell cmds to activate the sending of the keep-alive messages. In this example, the keep-alive messages will be sent every 30 seconds.
Connect-IpPbx
Set-IpPbxGlobalConfigItem -Section "Server" -SubSection "LinkMgr" -Key "KeepAliveTimeout" -Value 30
Disconnect-IpPbx
Afterwards, the LinkMgr service has to be restarted.
Important: These setting will affect all SIP trunks.
Tested Features
- Incoming/outgoing national /international calls
- Correct Calling Line Identification (CLI) on national / intenational calls
- Holding and retrieving calls
- Toggeling between two calls
- Call transfer
- Call forwarding
- Conferencing
- Mutually supported codecs: G.722/ G.711a/ G.711u/ G.729
- Incoming/outgoing DTMF signaling in accordance with via RFC2833
- FAX transmission via T.38/G.711
Restrictions:
CLIP No Screening is currently not possible
FAX transmission on inbound FAX is done via G.711
Test date:
12/03/2019 with SwyxWare 11.32.0.0
CustomProviderProfiles_DNS:NET (DE)
kb5198_CustomProviderProfiles_DNS-NET(DE).zip
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.