English (GB) Deutsch

Articles in this section

See more

SIP Provider media.tel (AT)

Avatar
Swyx Info
  • Updated

General

The SIP trunk from media.tel (AT) was first tested and released with a SwyxWare 13.31.

Media.tel is offereing a SIP trunks 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.

It is important to inform media.tel that a SwyxWare will be connected to the SIP Trunk, so media.tel can set the proper profile.

Platforms

SwyxWare

The SIP Trunk from media.tel (AT) can be used according to the settings listed below from SwyxWare 13.31.

SwyxON

The SIP Trunk of media.tel (AT) is not released for central connection in the data center.

Configuration 

During creation of the SIP Trunkgroup, profile 'media.tel (AT)' has to be selected. If the profile is not included in the corresponding list, you can download the required CustomProviderProfiles.config for SwyxWare at the end of this article. For more information about using this file, see Configuration and Adaptation of SIP Providers via Provider Profiles.

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
Numberrange: +43 66 1234560 ... +43 66 1234569
In this case, the SIP URI must be entered in the format 4366123456*@*.

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
    • T.38 for FAX transmission
  • Incoming/outgoing DTMF signaling in accordance with via RFC2833
  • T.38 Negotiation and FAX Transmission.

Restrictions

None

Tests

18/03/2024 with SwyxWare 13.31

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. Enreach in no way guarantees the accuracy of this third-party contact information nor is responsible for it's content.

Related articles

Comments

0 comments

Please sign in to leave a comment.