Setup Alphalink SIP (PJSIP) Trunk

Alphalink Common Parameters

Code

This is the identifier for the account. It is generated automatically when creating the account.
It is in the form 0991NNNNNNNNN for a class 4 account, and 0990NNNNNNNNNN for a class 5 account.

Label

Account name.

Number ID

This is a number assigned to the account and serving as a reference number. It cannot be modified or deleted from the account.

Simultaneous communications

This setting allows you to limit the number of calls in progress simultaneously for an account. A call is counted from its initiation (receipt of a SIP INVITE message by the OpenVNO panel) until it hangs up.Its values are contractually defined when the account is created.

Three values are defined:

Incoming simultaneous communications
Maximum number of simultaneous calls initiated by customer equipment.

Simultaneous outgoing communications
Maximum number of simultaneous calls made to customer equipment.

Simultaneous communications
Maximum total number of simultaneous calls initiated on the account.

Subscriber number

33XXXXXXXXX 

This is the first number allocated to your trunk 

Authentication

Two authentication modes are available for the accounts

Authentication by IP address only

This authentication mode verifies that the IP address used by the client equipment during signalling exchanges appears in the list of addresses assigned to the account.

Combined authentication IP address - login / password

This mode adds authentication by login / password.

Our Tested Environment

Introduction

In our tests, we've utilised the first one of the two authentication methods. We informed in advance the Alphalink support team about the PBX public IP address presented during SIP signalling and RTP flows.

Platform: PBXact / FreePBX version 15 with Asterisk 16 engine.

Configuring the interconnection with Alphalink requires a few parameters to be set in the SIP/PJSIP configuration module of your PBXact. Three main modules are involved:

• Asterisk SIP Settings

• Trunks

• Config Edir

Asterisk SIP Settings

Chan PJSIP Settings

In the module Asterisk SIP Settings go to tab Chan PJSIP Settings and configure the settings in this suggested way

Open

Enable transport for udp/tcp/tls on IP address 0.0.0.0 (if you prefer you can define any other socket choosing the right one for you)

Open

Check at the very bottom of this page which ports are in use for each protocol: adjust the value of Port to Listen On with your preferred. It's strongly suggested to set the external IP address of your PBX in the "External IP Address" field

Trunks

In the module “Trunks” create a new trunk selecting  "Add SIP (chan_pjsip) Trunk" type

General

In the General section of the new Trunk, give the trunk the name of the assigned username (have a look at the code section) and define the Outbound Caller ID with the assigned Subscriber Number, optionally define “Maximum Channels” value.

Pjsip Settings / General

Go to pjsip Settings and in the General sub tab insert:

• Username: Your Subscriber Number

• Secret: 

• Registration: None

• SIP Server: sip2.openvno.net

• SIP Server Port: 5060

• Context: from-pstn

• Transport: choose between udp or tcp (tls at the moment is not tested)

Pjsip Settings / Advanced

Go to pjsip Settings and in the Advanced sub tab insert:

• Contact User: Your Subscriber Number

Tips

Useful asterisk commands:

• pjsip show aors

  • Shows all the AORs in memory

• pjsip show aor <trunk-name>

  • Shows specific trunk status

• pjsip show registrations

  • Shows all the remote registration in memory

• pjsip show registration <trunk-name>

  • Shows specific trunk registration status

Config Edit

Resolving emergency numbers
This service allows end-users to reach emergency numbers, by ensuring the translation of these after the INSEE code entered on the call. To enable this, a little tweak is needed on the PBX itself going in to the module Config Edit.

You'll be presented with this screen

You can copy and paste from the following line in the extensions_custom.conf file you find in Configuration File Editor

Don't forget to Save and Apply Configuration

Multiple CODE INSEE

If CODE INSEE is not a fixed value for every extension/trunk calling, you can define the related CODE INSEE in the Account Code field of each Extension calling through your trunk in the Modules >> Applications >> Extensions >> <extension> >> Advanced tab

You need also to change this way just one line of the code reported above in the extensions_custom.conf

Don't forget to Save and Apply Configuration

Inbound Routes

For configuring Inbound Routes refer to the related section of the wiki Inbound Routes Module