Campaign Dial Prefix Options

[enjay]

I think it would be cool if there was a feature to setup within system preferences local area codes.

This way within a campaign you could have the ability to disable the "dial prefix" and have it dynamically based on your local area codes settings append a 1 to the beginning of long distance numbers or remove the 1 from local numbers.

This would be very useful for people who leverage PRI's that are specifically for local (and cannot dial LD) and vice versa for Long Distance circuits.

Thoughts?

[gerski]

i think putting "X" on dial prefix will not use any dial prefix.

also since 2.0.3 when loading leads it will automatically add 1 prefix(if you leave it blank), don't have any idea to disable it since all our campaign are calling states(1 prefix)

[enjay]

This is not a support question it is a feature request. If its hard to understand here is the scenario.

1 Local PRI (can only dial local area codes)
1 Long Distance PRI (can only dial long distance area codes)

a campaign setup with local numbers may have an area code that is not local in it. So by having a variable with local area codes set you could hypothetically have the campaign dynamically determine if it needs to place a 1 before the prefix (for long distance "non local" numbers) or if it should just dial the 10 digit (area code plus number) without placing the 1 in front of it. As the dialplan will be configured accordingly to dial out of the Local PRI for numbers matching $X area codes or to dial out of the Long Distance PRI for numbers with an appended 1.

Make sense?

[mflorell]

I usually just do the dialing logic through extensions.conf instead of trying to program the logic into VICIDIAL. This is mostly because on multi-server setups you can have several different dial prefixes so customizing per server through extensions.conf works better.

As for the default 1 dial prefix default in the lead loaders, it should only populate if there is no phone_code in the data file.

[enjay]

for "example" my extensions.conf looks like so:

1NXXNXXXXXX,1,Dial(Zap/g0/${EXTEN}||o)

The above states anything with a 1 in front of it dial out g0 (a PRI only capable of dialing long distance if it tries to dial local it will not work)

480NXXXXXX,1,Dial(Zap/g1/${EXTEN}||o)

The above states anything matching just 480 dial out g1 (A local PRI if you try to dial long distance on it, it will fail).

So you see my dilemma? Im trying to have it dynamically place a 1 or leave it out.

[mflorell]

Why not just do this:


1480NXXXXXX,1,Dial(Zap/g1/${EXTEN:1}||o)

1NXXNXXXXXX,1,Dial(Zap/g0/${EXTEN}||o)

[enjay]

mmmm yeaaaaa.