Voicemail Down or being upgraded?

**christcorp** · 09-25-2008 05:45 PM

I just opened an online ticket for voicemail. Probably should have started searching here first. The 123 doesn't work. The 832-838-7000 works fine. I went in there and retrieved the messages from my Beta number and then deleted it. Unfortunately, my phone's MWI light is still flashing and I still get a stutter dialtone on the beta number. Another strange thing is that I can't get into the vpanel for my beta number either, so I couldn't go there and delete the voicemail from there.

On my primary ported residential number, I can get to vpanel and delete voicemails. However, when I called my residential to see if voicemail was working, I no longer have my vm message. It has the default voice saying the number is not available, or whatever, please leave a message. I still can't dial 123 and get voicemail, but at least I can access it from the vpanel or 832 number. Later.... Mike.....

**VOIPoTim** · 09-25-2008 06:06 PM

Originally Posted by christcorp

I just opened an online ticket for voicemail. Probably should have started searching here first. The 123 doesn't work. The 832-838-7000 works fine. I went in there and retrieved the messages from my Beta number and then deleted it. Unfortunately, my phone's MWI light is still flashing and I still get a stutter dialtone on the beta number. Another strange thing is that I can't get into the vpanel for my beta number either, so I couldn't go there and delete the voicemail from there.

On my primary ported residential number, I can get to vpanel and delete voicemails. However, when I called my residential to see if voicemail was working, I no longer have my vm message. It has the default voice saying the number is not available, or whatever, please leave a message. I still can't dial 123 and get voicemail, but at least I can access it from the vpanel or 832 number. Later.... Mike.....

Try 123 now and see if that is resolved. Your account was pointed to the new system in one place and not in the other so the 123 was accessing the old system.

We're looking into the other issues in ticket.

**VOIPoTim** · 09-25-2008 06:07 PM

Originally Posted by varaonaid

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** · 09-25-2008 07:49 PM

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** · 09-25-2008 07:50 PM

Voicemail is not working on my end either.

**christcorp** · 09-25-2008 08:32 PM

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

**chpalmer** · 09-25-2008 09:29 PM

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

123 not working for me.

360-552

**GTOJim** · 09-26-2008 12:46 AM

123 not working for me.

**usa2k** · 09-26-2008 04:29 AM

Originally Posted by VOIPoTim

It needs to have the "Config Server Path" set to provision.voipo.com and the MAC in our system.

I know some of the very very early ones were never setup like that and put in the system so that's why some lingering ones weren't/aren't being updated.

It has the right provision path.

VOIPo pushed a firmware back when GS glitched with a release.
I'll sent MAC via ticket to have it rechecked.

**varaonaid** · 09-26-2008 08:46 AM

Originally Posted by VOIPoTim

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.