English (GB) Deutsch
Print Friendly and PDF

Articles in this section

SIP Provider Alphalink (FR)

Avatar
Swyx Info
  • Updated

General

The SIP Trunk from Alphalink was first tested and released with a SwyxWare 2013.
Alphalink offers a SIP Trunk with User Authentication, i.e. you receive information about UserID, UserName and UserPassword from PYUR Business. The names can be different, or you receive only the user name and password. In this case the UserID is identical with the UserName.

Platforms

SwyxWare

The SIP Trunk from Alphalink can be used according to the settings listed below from SwyxWare 2013 on.

SwyxON

The SIP Trunk from Alphalink is not released for central connection in the data center.

Configuration

During creation of the SIP trunk group, profile 'Alphalink (FR)' must be selected.

Alphalink is operating with a number of different servers. Therefore it is not possible to preconfigure the Proxy Server in the "SIP" tab of the Trunkgroup properties. In this field, please enter the IP address or server name that Alphalink has named you. 

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:
Assigned number range: +33 970 1234560 ... +33 970 1234569. Since Alphalink is signalling the destination number in the request URI in format canonical without plus, the SIP URI for the trunk must be configured as '33970123456*@*'.

Tested Features

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

Restrictions

None

Tests

01/07/2013 with SwyxWare 2013

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.

Related articles

Comments

0 comments

Please sign in to leave a comment.