Configuration Guides

3CX

DIDWW SIP Trunks can be used with 3CX IP PBX for Inbound calls. The following guide will explain the steps necessary to configure the 3CX IP PBX.

Note

This guide has been created with 3CX Version 16.0.9.

Getting Started

Before you begin, you will need to create Inbound trunks on DIDWW User Panel.

Create an Inbound trunk. Assign the DIDs with the preferred trunk

Inbound

To add the DIDWW Inbound SIP Trunk into your 3CX console, proceed with the following steps.

Step 1. In the management console of 3CX navigate to your “SIP Trunks”.

../../_images/sip_trunk.png

Fig. 1. “Main SIP Trunk” window.

Step 2. In the SIP Trunks section click on Import Provider and a new window will pop-up (Fig.2).

../../_images/import_provider.png

Fig. 2. “Import Provider” window.

Step 3. Upload the file depending on the type of traffic (inbound).

Note

If the file opens as a New Tab with XML source code, use “Save As” on this new tab to save this file as XML.

Step 4. Once file has been uploaded enter the DID number in “Main Trunk No” field that you wish to assign to this trunk. (Fig.3)

../../_images/import_trunk_DID_number.png

Fig. 3. “Main trunk No” window.

Step 5. Navigate to the “Extensions” menu category, and click on Create an Extension associated with the DID. (Fig.4)

../../_images/extension_creation.png

Fig. 4. “Extension creation” window.

Step 6. You may enter all details for “Phone” provisioning (Optional Step). (Fig.5)

../../_images/extension_registration_details.png

Fig. 5. “Softphone provisioning details” window.

Step 7. Create an inbound rule to forward the calls from the DID to the extension. (Fig.6)

../../_images/inbound_rules_settings.png

Fig. 6. “Inbound Rules creation” window.

Note

Outbound call configuration guide for 3CX can be found here

Asterisk

extensions.conf:

[from-didww]
exten => _X.,1,Ringing
exten => _X.,n,Answer
exten => _X.,n,Echo
exten => _X.,n,Wait(600)
exten => _X.,n,Hangup

SIP

sip.conf:

[didww-ny]
host=46.19.209.14
dtmfmode=rfc2833
dtmf=rfc2833
type=peer
context=from-didww
insecure=invite,port
nat=never
allow=all

[didww-fra]
host=46.19.210.14
dtmfmode=rfc2833
dtmf=rfc2833
type=peer
context=from-didww
insecure=invite,port
nat=never
allow=all

[didww-la]
host=46.19.212.14
dtmfmode=rfc2833
dtmf=rfc2833
type=peer
context=from-didww
insecure=invite,port
nat=never
allow=all

[didww-mia]
host=46.19.213.14
dtmfmode=rfc2833
dtmf=rfc2833
type=peer
context=from-didww
insecure=invite,port
nat=never
allow=all

[didww-sg]
host=46.19.214.14
dtmfmode=rfc2833
dtmf=rfc2833
type=peer
context=from-didww
insecure=invite,port
nat=never
allow=all

IAX

iax.conf:

[didww-iax-us]
type=user
permit=46.19.209.42
context=from-didww

[didww-iax-eu]
type=user
permit=46.19.210.42
context=from-didww

Note

If asterisk will not be able to find extension within given context you will get an unhelpful No such context/extension IAX2 debug error. Thus, it’s better to use catch-all extension pattern _X. during debugging

You can find detailed explanation of asterisk IAX authentication here.