Page 1 of 1

Dial plan setup

PostPosted: Thu Apr 23, 2009 9:25 am
by cottonking2000
I need a few hints. I am trying to set up this type of feature:

Dial 9 before number = IAX
Dial 8 before number = SIP

My endpoint devices at the VOIP provider are set up fine. We currently test and call on Vicidial now.

In the Dial Plan entry I can handle this type of mod by changing the following:

exten => _71999NXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _7 1999NXXXXXX,2,Dial(${TESTIAXTRUNK}/${EXTEN:2},,tTor)
exten => _7 1999NXXXXXX,3,Hangup

_81999NXXXXXX

_7 to my desired 8 or 9 and match the rest of the set up:

[SIP Voipstreet]
disallow=all
allow=gsm
....

Kinda reverse learning the admin setups.....from the config files...

PostPosted: Thu Apr 23, 2009 10:01 am
by mflorell
That should work fine, let us know if you run into any issues.

trunk setting

PostPosted: Thu Apr 23, 2009 11:06 am
by cottonking2000
I understand context=trunkinbound

If

context=trunkoutbound

Would this be appropriate in the truck setup for 8-9 IAX or SIP setup?

PostPosted: Thu Apr 23, 2009 11:15 am
by mflorell
You should not need to set the outgoing context for a carrier configured through admin.php.

More config admin dial plan setup

PostPosted: Thu Apr 23, 2009 11:28 am
by cottonking2000
[general]
bindport=4569
iaxcompat=yes
bandwidth=high
allow=all
allow=gsm ; Always allow all, ulaw,or, it's cool :)
jitterbuffer=no
tos=lowdelay

Where do we set this up in the dial plan config admin file? Or could this be added into the template?

PostPosted: Thu Apr 23, 2009 11:45 am
by mflorell
Is this for a carrier record?

If so you can either put it into the "Account Entry" field or you can create a template for it.

If it has to be part of the [general] context then you need to edit the iax.conf file directly.

Ok

PostPosted: Thu Apr 23, 2009 12:08 pm
by cottonking2000
Thats exactly what I needed. Thank you

PostPosted: Thu Apr 23, 2009 2:29 pm
by williamconley
You may also want to remember that:
exten => _71NXXNXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _71NXXNXXXXXX,2,Dial(${DIAL7SERVICE}/${EXTEN:2},,tTor)
exten => _71NXXNXXXXXX,3,Hangup

would work as well under most circumstances and allow you to redefine the trunk variable "DIAL7SERVICE" in [globals] (which i include from a seperate file because it is usually the only context which requires editing) as whatever you want (IAX or SIP) without having to rename the variable (or have it "wrong" by being SIP when it says IAX, which can confuse a later technician).

I've found "dial x" descriptive variables like that to be quite helpful as time passes. My [globals] file has descriptive variables for dial9,8,7,6,5 in most cases for mutliple carriers in use for multiple campaigns and backups. They rarely get changed, but they are easily identified and do not require modification of the actual dialplan to add/modify a carrier later.