vicidial.org

we're gettings a lot ot this in our logs and we encountered a lot of abandon calls

can you help us what this means and why we encountered abandon calls.


[Oct 11 14:05:22] VERBOSE[4852] logger.c: [Oct 11 14:05:22] -- Got SIP response 503 "Service Unavailable" back from 69.94.226.174
[Oct 11 14:05:22] VERBOSE[23955] logger.c: [Oct 11 14:05:22] -- SIP/Accela-0000003f is circuit-busy
[Oct 11 14:05:22] VERBOSE[23955] logger.c: [Oct 11 14:05:22] == Everyone is busy/congested at this time (1:0/1/0)
[Oct 11 14:05:22] VERBOSE[23955] logger.c: [Oct 11 14:05:22] -- Executing [921001117757772012@default:3] Dial("Local/921001117757772012@default-3e3a,2", "sip/Accela2/1001117757772012||tToR") in
new stack
[Oct 11 14:05:37] VERBOSE[4852] logger.c: [Oct 11 14:05:37] -- Got SIP response 503 "Service Unavailable" back from 66.194.8.2

1) Welcome to the Party!

2) 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) Service unavailable is your carrier refusing to complete the call. This can be because you dialed an impossible number, or because you have exceeded your channel limit, or because you dialed too many channels in one second (too quickly). But mostly: The only one who can tell you why they refused the call ... is the carrier doing the refusing.

potpot wrote:we're gettings a lot ot this in our logs and we encountered a lot of abandon calls

can you help us what this means and why we encountered abandon calls.


[Oct 11 14:05:22] VERBOSE[4852] logger.c: [Oct 11 14:05:22] -- Got SIP response 503 "Service Unavailable" back from 69.94.226.174
[Oct 11 14:05:22] VERBOSE[23955] logger.c: [Oct 11 14:05:22] -- SIP/Accela-0000003f is circuit-busy
[Oct 11 14:05:22] VERBOSE[23955] logger.c: [Oct 11 14:05:22] == Everyone is busy/congested at this time (1:0/1/0)
[Oct 11 14:05:22] VERBOSE[23955] logger.c: [Oct 11 14:05:22] -- Executing [921001117757772012@default:3] Dial("Local/921001117757772012@default-3e3a,2", "sip/Accela2/1001117757772012||tToR") in
new stack
[Oct 11 14:05:37] VERBOSE[4852] logger.c: [Oct 11 14:05:37] -- Got SIP response 503 "Service Unavailable" back from 66.194.8.2

it means that there is a problem between your asterisk servers connection going to your carrier which is 66.194.8.2, it could mean:

1. No internet connection to that route
2. Authentication problem (Accela usually does IP authentication so check with them if your ip address is authorized to send a call to their servers)
3. Wrong dial prefix (Check with accela)

boybawang wrote:

potpot wrote:[Oct 11 14:05:22] VERBOSE[4852] logger.c: [Oct 11 14:05:22] -- Got SIP response 503 "Service Unavailable" back from 69.94.226.174

1. No internet connection to that route

Actually, internet worked because you got a response. So networking is not it.

There is no "standard" for SIP responses that is enforced in any meaningful way. Which means that you could get a SIP 503 if you did not pay your bill just as easily as you could get one because you dialed a number that does not exist (because you forgot the country code or added an extra 1 in front). The only thing you know for sure is that they refused to connect the call.

My guess, however, would be this: "sip/Accela2/1001117757772012||tToR" 100111? That seems very unlikely to be the proper beginning of a valid phone number.