SIP Provider Tele2 (AT)

General

The Tele2 SIP Connect trunk was first tested and released with a SwyxWare 2015 R40.

The Tele2 SIP Connect trunk is a SIP trunk with user authentication. You have received information about UserID, UserName and UserPassword, whereas the nameing may differ, or you have only received UserName and -password. In this case, UserID and UserName are identical.

Using a Swyx UC system may be announced when ordering the SIP Connect trunk or adjusted later via support. The Tele2 settings will then match exactly to the provider profile in SwyxWare.

Platforms

SwyxWare

The Tele2 SIP Connect trunk can be used according to the settings listed below from SwyxWare 2015 R40. If you use an earlier version of SwyxWare, incompatibilities cannot be excluded and you are responsible for your own usage.

SwyxON

The SIP Trunk of PYUR Business is not released for central connection in the data center.

Configuration

During creation of the SIP Trunkgroup, profile 'Tele2 (AT)' has to be selected.

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.

Session timer

The Provider Tele2 expects a session interval of 1800s for outgoing calls. Therefore create the following registry keys and set them to 1800.

Pfad (64-bit): HKLM\Software\Wow6432Node\Swyx\LinkMgr\CurrentVersion\Options

Name: SipMinSessionTimerIntervalSeconds, Typ: DWORD, Wert: 1800 (dezimal)

Name: SipSessionTimerIntervalSeconds, Typ: DWORD, Wert: 1800 (dezimal)

After these keys are created, the service 'LinkMgr' must be restarted.

Important: These registry keys will affect all SIP trunks.

• 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 codec: G.711a
• Incoming/outgoing DTMF signaling in accordance with via RFC2833
• FAX transmission via T.38

Restrictions

None

Tests

26/07/2017 with SwyxWare 2015 R40.3.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.