Voicemail Down or being upgraded?

[VOIPoTim]

Hey there,

Just curious, should the 123 work now for checking VM? It's isn't working for me. I was getting a stutter tone and flashing on the Grandstream but rebooted it when the 123 wasn't working and when I realized that the VM service was being upgraded. The stutter tone and flashing light weren't working when it rebooted (even though I have new VM) and 123 didn't either. Dialing the 832-878-7000 does work to access it. Also strange, when I dialed either my own VOIPo number (from my VOIPo phone) or 123, it goes to my failover number rather than to VM. I have call forwarding completely disabled so it has to be going via the failover which I don't understand since the VOIPo number (other than the few VM glitches listed above) is working perfectly.

Any thoughts?

Thanks!
Rae

Try 123 now. You were partially pointed to old and partially to new, so I'm assuming the failover was triggered when it could not route to old.

[Zarniwoop]

If I dial 123 it just goes to the failover number, my wife's cell phone, after about 15 seconds...

If I call my own # from itself, it goes to failover instantly with no delay.

If I call 832-838-7000 it asks for my phone # but it works.

801-649-xxxx

Thanks for the help Tim!

[darylo]

Voicemail is not working on my end either.

[christcorp]

Both my residential number and my beta number still give dead air when i dial 123. I rebooted both adapters. mike....

[chpalmer]

If I call 832-838-7000, I get some insurance company right now.

123 not working for me.

360-552

[GTOJim]

123 not working for me.

[varaonaid]

Try 123 now. You were partially pointed to old and partially to new, so I'm assuming the failover was triggered when it could not route to old.

123 works now to access primary VM. However, Virtual Number is completely down now - doesn't work to call it at all and have tried it from several phones. This seems to be directly related to it's VM. When I disabled it, calls go through. Now that I re-enabled it, calls won't go through - I get various error numbers from different phones/cell providers ("your call cannot be completed as dialed", or "the network is busy").

I rebooted the GS but no difference.

[VOIPoTim]

123 works now to access primary VM. However, Virtual Number is completely down now - doesn't work to call it at all and have tried it from several phones. This seems to be directly related to it's VM. When I disabled it, calls go through. Now that I re-enabled it, calls won't go through - I get various error numbers from different phones/cell providers ("your call cannot be completed as dialed", or "the network is busy").

I rebooted the GS but no difference.

I have someone working on this for your right now.

[VOIPoTim]

123 works now to access primary VM. However, Virtual Number is completely down now - doesn't work to call it at all and have tried it from several phones. This seems to be directly related to it's VM. When I disabled it, calls go through. Now that I re-enabled it, calls won't go through - I get various error numbers from different phones/cell providers ("your call cannot be completed as dialed", or "the network is busy").

I rebooted the GS but no difference.

Please test this now and confirm that it is resolved.

[varaonaid]

Please test this now and confirm that it is resolved.

Thanks for sorting it out so quickly. Yes, I can confirm that it's working now. I can tell a change was definitely made because I lost my previous VM greeting (no big deal at all, I needed to rerecord anyway) so it's definitely working now. Again, many thanks.

On a side note, when I call myself from my VOIPo line, it routes to my failover number then back to VOIPo VM. I have no problem with that but wondered if that is the expected behavior. For some reason, I thought failover was for network outages rather than the line being busy (which is what I'm assuming it's interpreting is the case when I call myself from my VOIPo line) but more than likely, my understanding was simply incorrect.