SIP Provider Alphalink (FR) (kb4488)

The information in this article applies to:

  • SwyxWare 2013

[ Summary | Information | Links ]


Information und configuration hints for SIP provider Alphalink (France).


General information

Alphalink is offering SIP trunks with user authentication and registerless SIP trunks. The authentication for a registerless SIP trunk is based on the public IP address of the SwyxWare server. Therefore, you need a static, public IP address from your ISP assigned to the SwyxWare server. For a registerless SIP trunk, it is not possible to run the SwyxWare with a private IP address behind a NAT gateway with a public IP address.
If you are running the SwyxWare server behind a NAT gateway, you need a SIP trunk with user authentication.  You have received information about UserID, UserName and password. Even for a SIP trunk with user authentication, Alphalink additionally checks the public IP address, but in this case, it could be the public IP address of a NAT gateway.

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.



For an AlphaLink SIP trunk with user authorisation, it is necessary to configure a SIP URI for the trunk in order to assign incoming calls to the correct trunk.

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*@*'.
For your convenience the generated CustomProviderProfiles.config is available for download at the end of this article. Extended information about how to use this file can be found at Configuration and Adaptation of SIP Providers via Provider Profiles (kb3436).

Important: From SwyxWare2013 R4 on, the provider profile for Alphalink is already available in the list of provider profiles and the CustomProviderProfiles.config is no longer necessary.

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



T.38 is not suppported by Alphalink, hence FAX transmission via Swyx FAX Client does not work.

Occasionally, problems with correct CLI was observed with international calls.

Test date: 01/07/2013
SwyxWare: V2013


Further tested SIP providers


As far as software supplied or used by us, includes open source elements the additional terms under apply in addition. An overview which products from the Swyx portfolio include open source elements and which open source license is relevant can be found under

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.


Comment on this article

If we have any follow-up questions, where can we contact you?

E-Mail Address (optional)


This feedback form can't be used for support requests. Those requests must be directed to your Swyx reseller or distributor.