Can't Make Calls Anymore with Providers

[richard]

Hello

Recently NONE of my calls through the “providers” I setup on Voxalot has been going through.

I have two providers setup (vBuzzer and SipDiscount). Both use to work fine with Voxalot.

When I try to make a call, I get the eyebeam system message “Called failed: Not found”

All calls go through via my other SIP Accounts.

Can you help?


Richard

[richard]

Hello

Still can't make any calls using the setup "providers".

Can Support help at all?

Richard

[affinity]

Do you have any dial plans?

If so, maybe do a test on the dial plan page and see what the result should be... if it isn't right, then you may need to adjust your dial plan rules.

[richard]

Hi Affinity

Yes I use dialplans to tell Voxalot which provider to use.

When I use the test functionality, it works fine and says it will route the call through the expected VSP, but when I dial using eyeBEAM through Voxalot, the call fails.

It used to work fine before and I made no changes.

Also, It fails not on one provider, but two.

Any ideas? Support?

Richard

[ctylor]

You probably need to troubleshoot more to narrow down the problem. Does configuring your softphone to directly use the providers (instead of going through Voxalot) still work for you or is that down too? How about does Voxalot's webcall service still work for you?

[richard]

I have no dialplan or special configuration in the softphone (eyeBeam 1.5.5) setup. The WebCall service works fine!

Bascially, the call should be sent directly to the Voxalot Proxy and processed per the Voxalot (on Voxalot's server) dialplan, which says to use the appropriate VSP (provider) based on the number dialed.

It does not do this.

Here are my test results:

A call to:18001234567 will get forwarded to sip:18001234567@tf.voipmich.com

A call to:1416123456 will get forwarded to sip:1416123456@vbuzzer.com:80

A call to:12121233456 will get forwarded to sip:0012121233456@sip1.sipdiscount.com

Only the first one to the 800 number works. ( i think tf.voipmich.com is a built in provider in Voxalot)

The 2nd & 3rd ones fail. They use to work before.

I was hoping Voxalot Support would take a look at my Voxalot config. Its seems pretty correct to me.

Thanks in advance for your help.


Richard

[richard]

Oh yes, configuring the softphone to directly use the providers also work.

[martin]

Please confirm:

1. 600 reaches our echo test
2 *393616 reaches FWD echo test
3 18005551212 reaches tellme

If the above 3 work ok, as a test could you try pointing your ATA to voxalot.com.au instead of voxalot.com and retry your 2 providers.

[richard]

Hi Martin

Thanks for your reply.

Okay, leaving the proxy at voxalot.com, here are the results of the tests:

600 - Call Failed
*393613 - Call Failed
18005551212 - Call Completes

So, I then proceeded to change the proxy to voxalot.com.au, results were:

600 - Call Completes
*393613 - Call Completes
18005551212 - Call Completes

In addition, my previous posting saying my MWI indicator was no longer working has been resolved. Only when logged into voxalot.com.au does the MWI work.

I'm curious. Is there any real difference between voxalot.com and voxalot.com.au? Any idea why one seems to work and the other doesn't on my eyeBeam or Network?

BTW, when I go back to voxalot.com, the calls were fail again.

Again, thanks for your help in resolving this annoying issue.

Richard

[richard]

Hi Martin

The calls are working fine now, but the MWI will not go off even after I have cleared the calls. Would ou mind checking my account to see if the Voxalot server is still sending VM Available Info?

Thanks


Richard