Voicemail Down or being upgraded?

[VOIPoTim]

what is a shame that my damn hair fell out so early.

Then the bags under my eyes and it's like a roller coaster that stops going up and only goes down...lol

Was it mostly in the last year or so while you were a VT customer?

I mean let's give credit where credit is due.

[NY Tel Guy]

Was it mostly in the last year or so while you were a VT customer?

I mean let's give credit where credit is due.

Yes, the one where I have all my hair was January 06 and then current one is after I tried to unsuccessfully to complete 3 calls in a row on VT.

[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

[usa2k]

| 734-437-XXXX | zeus.voipwelcome.com |

Well ... I thought the GS was under VOIPo control?
I changed it to "welcome" and it seemed to stick.

The GS immediately gets the green flash on the GS.
No MWI though.
Definitely a Stutter Tone.

And now about 90 seconds later, MWI showed up.
Thank you!

Is there something VOIPo needs to do to ensure it is managed by VOIPo?
Time is 4 hours ahead of my EST time right now.

[VOIPoTim]

Is there something VOIPo needs to do to ensure it is managed by VOIPo?
Time is 4 hours ahead of my EST time right now.

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.

[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.....

[VOIPoTim]

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.

[usa2k]

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.

[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!