Block specific NXX in DNC list

[globalmarksol]

Hello All!

So we received a big bill from our VoIP company for dialing out 411 numbers from data we've entered into the system. The 411 numbers have a NXX of 555 in them. There are currently still numbers in our system that are being dialed out since we have hundreds of thousands of numbers in our system it is difficult for me to isolate on each individual number (also I don't know if there would be a script that I could write to remove these numbers from a list I have).

Is there a way to add a NXX (for example just NPX555XXXX) into the DNC list so the system blocks out the number before even dialing a call?

Has anybody here faced a similar situation with their VoIP company? I'm also interested in hearing about other VoIP companies you guys may recommend because I believe we're not getting such a good deal.

Thank you in advance!

[gardo]

Try our VoIP service at http://justgovoip.com. And if you're using GOautodial CE you automatically get discounted rates for outbound calls to the US.

What kind of deal are you getting (that's not so good)?

Has anybody here faced a similar situation with their VoIP company? I'm also interested in hearing about other VoIP companies you guys may recommend because I believe we're not getting such a good deal.

[williamconley]

Sorry to interrupt the sales pitch Gardo, LOL ...

We only recommend Carriers to Clients, so I'll stick to technical discussions.

You can add a dialplan entry to BLOCK any pattern.

For instance, if your normal dialplan is:

Code: Select all

exten=>_81NXXNXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten=>_81NXXNXXXXXX,n,Dial(${DIAL8TRUNK}/${EXTEN:1},,To)
exten=>_81NXXNXXXXXX,n,Hangup

You would modify it to:

Code: Select all

exten=>_81NXX555XXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten=>_81NXX555XXXX,n,Hangup
exten=>_81NXXNXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten=>_81NXXNXXXXXX,n,Dial(${DIAL8TRUNK}/${EXTEN:1},,To)
exten=>_81NXXNXXXXXX,n,Hangup


Notes: In older Asterisk, the "more precise" entries would always take precedence. In 1.8 (and beyond?) the FIRST match could win. So always put these "override" entries ABOVE the actual carrier dialplan to be sure they intercept.
You could also insert a set pri cause line before the hangup if you wanted to be a little more detailed. Look in extensions.conf for "Set(PRI_CAUSE" for a few possible examples. Try a few and see how they appear in the list after you set the cause to any one of the various values and see which one is appropriate for your ability to "identify and eradicate" if that's what you want to do.

OK, Back to you Gardo! LOL

[mflorell]

From the default extensions.conf included with Vicidial:(commented out)

; block calls to 555 numbers
; exten => _91NXX555NXXX,1,AGI(agi://127.0.0.1:4577/call_log)
; exten => _91NXX555NXXX,n,Dial(${TRUNKloop}/8889990011112,,to)
; exten => _91NXX555NXXX,n,Hangup()

[globalmarksol]

First off, mflorell I want to personally thank you and your team for all of the time and effort you've guys have put into this project and I am floored on how much support you guys offer for this open sourced product, you guys are truly truly a blessing for us small business guys and then some.

I actually found the dialplan before in the forum before and implemented it however I did not place it above the carrier dialplan. Thank you for that insight, I have adjusted it and will let you know the results. On the second message, should I also do that in Asterisk on top of the dialplan?

Gardo, we're getting less than a cent a minute through the company we are working through, however the charge starts as soon as the phone starts ringing with no forgiveness on shortcalls plus $0.50 for each 411 call the bill racks up rather quickly.

Again thank you for your time guys!

[williamconley]

should I also do that in Asterisk on top of the dialplan?

To be certain to kill it in all circumstances in asterisk 1.8 ... this would need to appear in EACH dialplan entry for each Carrier dialplan pattern. if you only have one carrier, then one is fine. but if you have multiple carriers, you'd need one for each carrier

If you have multiple dial patterns per carrier, you'd need one for each pattern