SIP Provider net-cloud (AT)

General

The SIP trunk of net-cloud was first tested and released with SwyxWare 11.20.0.0.

The SIP trunk of net-cloud is a SIP trunk with user authentication, i.e. you get information about user ID, user name and password from net-cloud. The names may differ, or you will only receive a name or ID with password. In this case the user ID is identical to the user name when configuring the SIP trunk in SwyxWare.

The actual interoperability tests were performed by net-cloud itself, not by the Enreach TAP.

Platforms 

SwyxWare

The SIP Trunk of net-cloud can be used without restrictions from SwyxWare 11.20.0.0 on.

SwyxON

The SIP Trunk of net-cloud is suitable for central connection in the data center.

Configuration 

When creating the SIP trunk group, select the profile 'net-cloud (AT)'.

SIP URIs

When creating the actual SIP trunk, a SIP URI must be entered after entering the phone number range so that incoming calls can be assigned. The assigned number block must be taken into account in the correct format.

Example
Number block: +43 1239988776600 ... +43 1239988776699
In this case, the SIP URI must be entered in the format 4312399887766*@*.

Codec configuration

For FAX transmission it is necessary to select the option "Remove T.38 from first negotiation (SIP INVITE)" via the tab "Codecs/Channels" of the properties of the created SIP trunk.

Tested Features 

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

Restrictions

None

Tests

11/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.