The following information are valid for a SwyxWare 11 or later and cannot necessarily applied to earlier versions.
OpenIP 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.
There is a dedicated SwyxWare profile for the OpenIP SIP trunks available. OpenIP therefore must be informed if a SwyxWare is connected to their SIP trunk. Otherwise there is a risk of problems in the SIP communication and number format.
The SIP Trunk from OpenIP can be used from SwyxWare 18.104.22.168 on. When using an earlier version of SwyxWare incompatibilities cannot be excluded and use is at your own risk.
The SIP Trunk from OpenIP is suitable for central connection in the data center.
When creating the SIP trunk group, select the profile 'OpenIP (FR)'.
After creating the trunk group, in the property settings of the trunk group, on tab 'Profile', it is necessary to to add special number replacement rules. The following rules need to be added for inbound, calling party:
+* -> +*
* -> +[cc]*
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: +33 970 112230 ... +33 970112239
In this case the SIP URI must be entered in the format +3397011223*@* .
During creation of the actual trunk, in the codec configuration dialog, T.38 has to be deselected as supported codec. This step could also be performed afterwards in the properties of the SIP trunk, underneath the 'Codecs' tab.
- Incoming/outgoing national calls
- Incoming/outgoing international calls
- Correct Calling Line Identificaion (CLI) on national and international calls
- Holding and retrieving calls
- Toggeling between two calls
- Call transfer
- Mutually supported audio codec: G.711u
- Incoming/outgoing DTMF signaling in accordance with via RFC2833
- FAX transmission via G.711
15/01/2014 with SwyxWare2013 R3
30/06/2015 with SwyxWare2015 R2
27/11/2017 with SwyxWare 11
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.