FIXED: PIAF 1.8 and VoicePulse "All Circuits are Busy"

[jribbing13]

I just installed the Purple edition of PIAF and I use VoicePulse for my SIP provider.

Inbound works great, but OUTBOUND gives me an error:

"All Circuits are Busy."

My trunks are showing they are registered.

Does anyone have any ideas?

Thanks...

 

[randy7376]

I know this is going to sound dumb, but have you defined an outbound route?

 

[rossiv]

I had voicepulse once upon a time - I think they require 1NXXNXXXXXX dialing on their trunks. Do you have their Voicepulse FreePbx module installed? If not, the module makes the configuration a matter of three steps and everything works when the module does it.

 

[jribbing13]

I have the outbound route set up, and yes I do have the 1NXXNXXXXXX dial plan added on the trunk.

I copied the trunks and the dial plans from an earlier version of PIAF using VoicePulse on a working PIAF install.

I've notice that the VoicePulse "auto configuration mode" is not working:

"function: core_routing_getroutenames has been deprecated and removed."

And it has not worked in months on any install that I have.

I really wish VoicePulse would fix this and upgrade their module so it works.

Thanks for the advice. I'll keep searching.

 

[kenn10]

Could Be the Asterisk Version

You might submit a ticket with Voicepulse after you do some more analysis. Back when I upgraded from 1.4 to 1.6, a couple of my carriers rejected the calls because their system did no recognize the handshake saying "Asterisk 1.6". Since Asterisk 1.8 is relatively new, that could be the case again. I no longer use Voicepulse so I cannot comment on them specifically in your case.

I'd recommend you do a sip debug from the CLI and study the error messages for more of a clue. You'll see a call reject and a code which will give more information in the debug results.

 

[amygrant]

I was getting this error using a different provider and realized it was due a bad dialing pattern on a trunk.

 

[jribbing13]

I got it fixed.
He supplied me with the wrong username and password for VP...

Thanks everyone.