Supported devices
ATA Adaptors
IP Phones
Cordless IP Phones
IP Conference Phones
IP PBX Software/Hardware
Desktop Softphones
Mobile Softphones

Security considerations for Callcentric customers

3CX Version 6
3CX Version 12
3CX Version 12.5
3CX Version 15
3CX Version 16
3CXPhone (for Windows)
3CXPhone (Mobile)
Aastra 6753i
Acrobits/Groundwire for iPhone
Android SIP Client
Apivio MWP1100
Asterisk 1.4 and 1.2
Asterisk 1.6
Asterisk 1.6.2, 1.8, and 10
Asterisk 14
Asterisk 17 CHAN_SIP (Vanilla)
Asterisk 17 PJSIP (Vanilla)
Asterisk Admin GUI v2.11
Asterisk Admin GUI v12
Asterisk Admin GUI v13
Asterisk Admin GUI v15
Bria Solo
Bria Desktop
Bria Mobile
Callcentric Android Click2Dial App
Callcentric iPhone Click2Dial App
Callcentric Softphone
Cisco ATA 186/188
Cisco SPA112/SPA122
CloudTC Glass 1000
D-Link DVG-1402S
Gigaset A510 IP
Gigaset C610A IP
Gigaset DX800A
Grandstream DP715/710
Grandstream DP750/720
Grandstream DP752/730/722
Grandstream GAC2500
Grandstream GRP2612
Grandstream GRP2613
Grandstream GRP2614
Grandstream GRP2615
Grandstream GXP1450
Grandstream GXP1620
Grandstream GXP1625
Grandstream GXP1630
Grandstream GXP1760
Grandstream GXP1782
Grandstream GXP2110
Grandstream GXP2130
Grandstream GXP2140
Grandstream GXP2160
Grandstream GXP2170
Grandstream GXP2200
Grandstream GXV3140
Grandstream GXV3240
Grandstream GXV3275
Grandstream GXV3370
Grandstream GXV3380
Grandstream HandyTone 286
Grandstream HandyTone 486
Grandstream HandyTone 702
Grandstream HandyTone HT802
Grandstream HandyTone HT814
Grandstream HandyTone HT818
Grandstream UCM6102
Grandstream UCM6204
Grandstream Wave Lite
Grandstream WP820
Htek UC803
Htek UC860
Htek UC924
Htek UC926
Innomedia SIP MTA-6328
Innomedia BuddyTalk 110
Linksys PAP2
Linksys SPA3102
Linphone Desktop (v4.1.1)
Linphone Desktop (v3.4.3)
Linphone Mobile
Linphone Mobile (v.3.2.3)
NCH Express Talk
Nokia E90
pbxnsip Version 3
Polycom SoundPoint IP 601
Polycom SoundStation IP 5000
snom 1xx/2xx/3xx
snom 820
snom D717
snom D735
snom D785
snom M9
snom ONE
Telco AC-211
trixbox / Elastix / pbx-in-a-flash
Windows Messenger
Unidata ICW1000G
Uniden EXP1240
UTStarcom F3000
Vodia PBX (v5)
Vodia PBX (v64.0)
VTech VCS754
VTech VDP650
VTech VSP600
VTech VSP725
VTech VSP726
VTech VSP735
VTech VSP736
X-Lite / X-Pro / eyeBeam
Yealink T32G
Yealink T41S
Yealink T42G
Yealink T42S
Yealink T46G
Yealink T46S
Yealink T48S
Yealink W52P
Yeastar MyPBX U100
ZoIPer 3.2
ZoIPer 5
ZoIPer Mobile
Zoom 5801
Zycoo CooVox U20
Other Linksys/Sipura products
Generic / Other Device

DID-Based Routing with Asterisk
DID-Based Routing with trixbox / Asterisk Admin GUI / Elastix / PBX-in-a-Flash
DID-Based Routing with trixbox / Asterisk Admin GUI / Elastix / PBX-in-a-Flash
Regular Asterisk users click here
In this guide we will configure inbound routing based on the DID (number) information returned by Callcentric. Since you are not able to initially configure DID based routing with Callcentric and Asterisk Admin GUI / trixbox / Elastix / PBX-in-a-Flash you will need to do further editing.

*NOTE: This will only work with Asterisk Admin GUI / trixbox / Elastix / PBX-in-a-Flash since those are the systems which contain the ext-did context.

Below we will provide the necessary information to configure your Asterisk Admin GUI / trixbox / Elastix / PBX-in-a-Flash installation to route based on the called DID in your Callcentric account.

Please understand that this guide presents the most basic configuration for configuring DID based routing and is meant as a learning tool to configure your own complex routing. This is only a single method of many which may be applicable in this type of situation.

The setup information below is based on Asterisk Admin GUI 2.1.3 and Asterisk 1.4; although most other older and newer versions should be very similar.

Please note that Callcentric is not responsible for preventing unwanted physical or remote access your IP PBX. If your IP PBX is compromised then you will be responsible for any damage caused.
Please be sure to read this guide regarding securing your IP PBX solution.

Main Projects:
trixbox -
PBX-in-a-Flash -
PBX-in-a-Flash -
Asterisk -
elastix -

Help and Support:
AussieVoIP sip_header information - sip_header
AussieVoIP context information - contexts
AussieVoIP extension information - extensions
Elastix support - click here
PBX-in-a-Flash support - click here

In order to use this guide you will need a properly configured Asterisk Admin GUI / trixbox installation which can receive incoming calls from Callcentric. You may double check our Asterisk Admin GUI / trixbox setup guides to make sure that your system can at least initially receive incoming calls.

Once you can receive incoming calls properly you may configure DID based routing by following the instructions below:
1 Required edit to Callcentric trunk and default configuration options
In your sip.conf, or sip_general_custom.conf, file please make sure that the following values are present. Note that there should only be a single line like the following in the file being edited:


Once the change has been made please save the file.

Next please find your current configured Callcentric trunk, either through the web interface command line or method of your choice. Then make sure that the following values are present in the PEER details:


Then in your register string please make sure that your 1777 number is NOT present at the end of the string, "/1777MYCCID". Your register string should be formatted in the following manner:

* Where 1777MYCCID is your Callcentric account number and SUPERSECRET is the same password you create when you sign up for your Callcentric account. Optionally you may change your SIP password in your preferences.

Once done save your changes and reload your Asterisk process.

2 Creating or editing the inbound context
Here we will configure the inbound context which will be used to handle the routing of inbound calls to your Asterisk Admin GUI / trixbox installation. To create this context you can either use the command line, a text editor of your choice or the trixbox interface to edit the extensions_custom.conf file.

Once you are able to access the extensions_custom.conf file you can follow the steps below:

1. Enter the following context:
exten => s,1,Set(Var_FROM_DOMAIN=${CUT(CUT(SIP_HEADER(TO),@,2),>,1)})
exten => s,2,GotoIF($["${Var_FROM_DOMAIN}" = ""]?5:3)
exten => s,3,GotoIF($["${Var_FROM_DOMAIN}" = ""]?5:4)
exten => s,4,GotoIF($["${Var_FROM_DOMAIN}" = ""]?5:7)
exten => s,5,Set(Var_TO_DID=${CUT(CUT(SIP_HEADER(TO),@,1),:,2)})
exten => s,6,GotoIF($["${Var_TO_DID}" != ""]?ext-did,${Var_TO_DID},1:7)
; Users may edit the lines below to route incoming calls to other locations/contexts.
; If you don't know what this means then you should likely skip the lines below and
; allow the script to run unmodified
exten => s,7,GoTo(from-pstn,s,1)
exten => h,8,Playback(ss-noservice)
exten => h,9,Macro(hangupcall)

You may also replace "ext-did,${Var_TO_DID}" with your own desired context information; however this is ONLY recommended for advanced users.

2. Save the file.

3 Configure your inbound routing to route to your desired location
In Asterisk Admin GUI / trixbox / Elastix / PBX-in-a-Flash make sure to configure an inbound route with your 1777 number as the "DID Number" and the "Caller ID Number" as blank. For example:

1777MYCCID / any CID

Then configure the various routes for your DIDs/number with the specific number as the "DID Number" and the "Caller ID Number" as blank. For example:


Set the destination for these inbound calls to your desired location. For example MYCCDID1 can go to an IVR while MYCCDID2 can be sent to the sales department.

4 Placing Test Calls
Once you are done save your changes and then test incoming calling to see that your Asterisk setup now routes inbound calling based on the number called.

To test inbound calls from Callcentric to your new DID based routing setup, follow the directions listed in this FAQ. You will also want to test calls directly to your DID from a PSTN phone if you have a DID on your account.