INFO

SIP Provider OpenIP (FR) (kb4571)

The information in this article applies to:

  • SwyxWare 11
  • SwyxWare 2015

[ Summary | Information | Links ]


Summary

Information und configuration hints for SIP provider OpenIP (France).


Information

General information

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.

Configuration

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.

Example
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).

Important: From SwyxWare 11.10.0.0 on, the provider profile for OpenIP is already available in the list of provider profiles and the CustomProviderProfiles.config is no longer necessary.
 

Tested Features

  • 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
  • Conferencing
  • Mutually supported audio codec:
    • G.711u
  • Incoming/outgoing DTMF signaling in accordance with via RFC2833
  • FAX transmission via G.711

FAX transmission

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.

Limitations
  • none

Test date:
15/01/2014 with SwyxWare2013 R3
30/06/2015 with SwyxWare2015 R2
27/11/2017 with SwyxWare 11

Overview of tested SIP provider


Links

As far as software supplied or used by us, includes open source elements the additional terms under https://www.swyx.com/open-source apply in addition. An overview which products from the Swyx portfolio include open source elements and which open source license is relevant can be found under https://www.swyx.com/open-source.

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.


Comment

Comment on this article



If we have any follow-up questions, where can we contact you?

E-Mail Address (optional)


Note

This feedback form can't be used for support requests. Those requests must be directed to your Swyx reseller or distributor.