SIP Provider i4IP (NL)

General

The SIP Trunk from i4IP(NL) was first tested and released with SwyxWare 11.25.0.0.

i4IPis offering a SIP trunk with user authentication. You have received information about UserID, UserName and UserPassword, whereas 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 from i4IP can be used without restrictions from SwyxWare 11.25.

SwyxON

The SIP Trunk from i4IP(NL) is not released for central connection in the data center.

Configuration

In the operator portal, the Swyx profile has to be selected. Please be aware that changes in the settings must be reflected by the SwyxWare settings and adopted accordingly.

When creating the SIP trunk group, select the profile 'i4IP (NL)'.

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.

Example:
Number block: +31 20 9988776600 ... +31 20 9988776699
In this case, the SIP URI must be entered in the format 02099887766*@*.

When creating the actual SIP trunk, the audio codec G.729 can be deselected in the codec dialog.

Codec Configuration

For T.38 FAX transmission, the checkbox "Remove T.38 codec from initial invite" has to be selected in the codec dialog.

Tested features

• Incoming/outgoing national calls
• Incoming/outgoing international calls
• Correct Calling Line Identification (CLI) on national and international calls
• Holding and retrieving calls
• Toggeling between two calls
• Call transfer
• Conferencing
• Mutually supported codecs: G.722/G.711a/ G.711u/ T.38
• Incoming/outgoing DTMF signaling in accordance with via RFC2833
• T.38 negotiation and FAX transmission

Restrictions

• CLIP No Screening is not allowed in the Netherlands

Tests

04/09/2018 with SwyxWare 11.25.0.0
12/01/2020 with SwyxWare 12.00.0.0
14/02/2022 with SwyxWare 13.05

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.