General
The SIP trunk of provider Servercom was first tested and released with a SwyxWare 11.20.0.0.
Serveurcom is offering a SIP trunk with user authentication. Along with the assigned number range and server information, you also need UserID, UserName and UserPassword. Please be aware that the naming may differ, or you might have only received UserName and -password. In this case, UserID and UserName are identical.
Platforms
SwyxWare
The SIP Trunk of Serveurcom can be used without restrictions from SwyxWare 11.20.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 of Serveurcom is not released for central connection in the data center.
Configuration
When creating the SIP trunk group, the profile 'Serveurcom (FR)' has to be selected.
Codec Configuration
For T38 negotiation, it is necessary to set the two options "Remove T.38 from initial negotiation (SIP INVITE)" and "Prohibit T.38 re-invite by sender" in the Codecs/Channel tab of the Trunk Properties dialog.
Registry Keys
In order to use the Serverucom SIP Trunk, it is necessary to create the following registry keys:
| Registry Key | Type | Value |
| HKLM\Software\Wow6432Node\Swyx\IpPbxSrv\CurrentVersion\Options\EnableTrunkCallEarlyMedia | DWORD | 0 |
| HKLM\Software\Wow6432Node\Swyx\LinkMgr\CurrentVersion\Options\IgnoreSIPDiversionHeader | DWORD | 1 |
Important: These registry keys will affect all SIP Trunks.
Tested Features
- Incoming/outgoing national calls
- Incoming/outgoing international calls
- Correct Calling Line Identificaion (CLI) on national and international calls
- CLIP No Screening
- Holding and retrieving calls
- Toggeling between two calls
- Call transfer
- Conferencing
- Mutually supported audio codec: G.711a/ G.729
- Incoming/outgoing DTMF signaling in accordance with via RFC2833
- FAX transmission via T.38
Restrictions
None
Test date
23/07/2018 with SwyxWare 11.20.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.