SIP Provider TNG (DE)

General

The SIP Trunk from TNG was first tested and released with SwyxWare 11.31.0.0.

The SIP Trunk from TNG is a SIP Trunk with user authentication, i.e. you receive information on user ID, user name and password. The names may differ, or you may 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.

TNG offers direct dial SIP trunks with a number block as well as MSN numbers with just a single number. The setup is identical here. When using multiple MSN trunks, forwarding rules must be defined so that the correct trunks are used for outgoing calls.

Platforms

SwyxWare
The SIP Trunk from TNG can be used from SwyxWare 11.31.0.0 on. 

SwyxON
The SIP Trunk from TNG is released for central connection in the data center.

Configuration

When creating the SIP trunk group, select the profile 'TNG (DE)'.

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, called party:
[ac]*  -> +[cc][ac]*

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.

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
Numberblock: +49 431 1234560 ... +49 431 1234569
In this case, the SIP URI must be entered in the format 431123456*@*.

CLIP No Screening

To activate the feature CLIP No screening in the SwyxWare, it is necessary to set the option "Always use originator's number" in the tab "Number signalling" of the SIP trunk settings.

Tested features

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

Restrictions

-

Tests

05/11/2024 with SwyxWare 14.10
04/10/2018 with SwyxWare 11.31.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.