vicidial.org

- ViciBox Redux v.5.0.2-130821
Asterisk 1.8.23.0-vici

Hi All,

When dialing wrong numbers (and some even working numbers) via a US Carrier (VoIP Innovations), instead of getting a busy signal and giving a BUSY / CONGESTION status, asterisk answers the call.

Here are some sample numbers:
3013861953
4075427088
9513327861
4025589681

Can anyone please provide me some insight on how I can tackle this issue? Is this carrier related or asterisk (local) issue OR carrier(VoIP Innovations) issue ?

1) Welcome to the Party!

2) As you are obviously new here, I have some suggestions to help us all help you:

When you post, please post your entire configuration including (but not limited to) your installation method and vicidial version with build.

This IS a requirement for posting along with reading the stickies (at the top of each forum) and the manager's manual (available on EFLO.net, both free and paid versions)

You should also post: Asterisk version, telephony hardware (model number is helpful here), cluster information if you have one, and whether any other software is installed in the box. If your installation method is "from scratch" you must post your operating system and should also post the .iso version from which you installed your original operating system. If your installation is "Hosted" list the site name of the host.

If this is a "Cloud" or "Virtual" server, please note the technology involved along with the version of that techology (ie: VMware Server Version 2.0.2). If it is not, merely stating the Motherboard model # and CPU would be helpful.

Similar to This:

Vicibox X.X from .iso | Vicidial X.X.X-XXX Build XXXXXX-XXXX | Asterisk X.X.X | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation | Intel DG35EC | Core2Quad Q6600

3) I note you listed your installer version and your asterisk version ... but you MUST list your Vicidial Version with Build. So I posted the entire 'welcome' packet above. enjoy. LOL

4) You should run sip debug and find out who answers the call. I doubt it's YOUR asterisk server deciding to answer the call without an indication from the carrier that the call has indeed been answered. But sip debug will tell you who initiates the answer. I recommend this test have NO other traffic on the server to ease the debugging process.

We are currently running 4-vicibox servers in cluster:
- ViciBox Redux v.5.0.2-130807
VERSION: 2.8-410a
BUILD: 130824-2319
© 2013 ViciDial Group

Server1: Database only
Server2: Asterisk + Web + Agent Login
Server3: Asterisk only
Server4: Asterisk + Web + Agent login

All servers were installed using standard installation (vicibox-install)

Another way to debug this is to call the numbers via a different carrier (you do have a backup VoIP provider right?). if you get a different result you know where the issue is.

I guess it was a carrier issue.
VI seems to have fixed it on their end.

Good postback

Was this outbound or inbound? Just to let you know many of these VoIP wholesalers resell a bunch of carriers through their own sip proxies. A lot of times what can happen is one of their carriers can introduce extended rings or kick back their own recorded errors. Good chance if this was outbound... VI probably found the carrier doing this and threatened to pull them or flat out shut them down. I am not a big fan of VI though. I have had TONS of billing issues. Had them over charge quite a bit too and had to argue with them.

that's weird, cuz I've never had anything like that and we have many customers using VOIPInnovations. Their pricing isn't great, but I've never had anyone complain about anything beyond an occasional technical hiccup (and they were down for 20 minutes once last year and freaked everyone out). But aside from not being the best pricing (ie: not cheap), I've never had a complaint about them regarding billing for something other than their stated pricing.