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 188.8.131.52 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)'. 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.
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]*
Numberblock: +33 970 112230 ... +33 970112239
In this case the SIP URI must be entered in the format +3397011223*@* .
For your convenience the generated CustomProviderProfiles.config is available for download at the end of this article. Extended information about how to use this file can be found at Configuration and Adaptation of SIP Providers via Provider Profiles (kb3436).
- 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
OpenIP does not support the T.38 protocol, which is strongly recommended for FAX transmission in an IP environment. The alternative method for FAX transmission via G.711 is supported from SwyxWare2015R3 on. In oder to prevent the intended T.38 stream switch, it is necessary to remove the T.38 codec from the list of supported codecs.
Note: Quality and reliability of a FAX transmission via G.711 strongly depends on the end-to-end network connection. Since the control and redundancy information from the T.38 protocol are missing, especially the transmission of larger documents may fail.
15/01/2014 with SwyxWare2013 R3
30/06/2015 with SwyxWare2015 R2
27/11/2017 with SwyxWare 11
CustomProviderProfiles OpenIP (FR)
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.