Voicemail Down or being upgraded?

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

Quote:

---

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.

Quote:

---

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.

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!

Voicemail is not working on my end either.

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

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

123 not working for me.

360-552

123 not working for me.

Quote:

---

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.

Quote:

---

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.

Quote:

---

Originally Posted by varaonaid

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.

Quote:

---

Originally Posted by varaonaid

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.

Tim were you able to migrate me?

Quote:

---

Originally Posted by VOIPoTim

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.

Voicemail dialing 123 seems to be working fine now on both my residential as well as my beta lines. Much better and cleaner system. The only drawback is the internal timer. It averages about 7 seconds on the residential line from the time 1-2-3 is dialed. It takes about 12 seconds on the beta line. 7 seconds may not seem long, but it does seem to be a little bit if you are expecting the voicemail response to kick in. The 12 seconds on the beta is definitely long, but it's the beta line so I don't really care about that one. 7 seconds on the residential is fine. Just need to let my wife know to just hang in there for an extra second or two. Thx for getting it taken care of. Later... Mike.....

When these issues started coming up today, I had all the VM stuff checked over because this was a pretty sloppy transition after seeing the issues from today.

Everything should be fixed now with the exception of MWI and the timezone when listening to the timestamp on the phone. Those two items should be fixed next week.

The timezones should be correct for e-mailed messages, the Web UI, etc.

Everyone is on the new system now. If anyone is seeing issues besides those two things, please send in a ticket.

I apologize for the messy transition. Like I said, we addressed that situation today and future upgrades should be smoother.

Quote:

---

Originally Posted by christcorp

Voicemail dialing 123 seems to be working fine now on both my residential as well as my beta lines. Much better and cleaner system. The only drawback is the internal timer. It averages about 7 seconds on the residential line from the time 1-2-3 is dialed. It takes about 12 seconds on the beta line. 7 seconds may not seem long, but it does seem to be a little bit if you are expecting the voicemail response to kick in. The 12 seconds on the beta is definitely long, but it's the beta line so I don't really care about that one. 7 seconds on the residential is fine. Just need to let my wife know to just hang in there for an extra second or two. Thx for getting it taken care of. Later... Mike.....

---

I use 123# and it is extremely fast. I program that into the uniden phone so the wife just hits the voicemail button and it auto dials.

Quote:

---

Originally Posted by VOIPoTim

When these issues started coming up today, I had all the VM stuff checked over because this was a pretty sloppy transition after seeing the issues from today.

Everything should be fixed now with the exception of MWI and the timezone when listening to the timestamp on the phone. Those two items should be fixed next week.

The timezones should be correct for e-mailed messages, the Web UI, etc.

Everyone is on the new system now. If anyone is seeing issues besides those two things, please send in a ticket.

I apologize for the messy transition. Like I said, we addressed that situation today and future upgrades should be smoother.

---

So was it normal then to lose the greeting that we previously had?

Quote:

---

Originally Posted by darylo

So was it normal then to lose the greeting that we previously had?

---

I lost our greeting.

Quote:

---

Originally Posted by darylo

So was it normal then to lose the greeting that we previously had?

---

I was told that wasn't supposed to happen because it was one of the things on the migration checklist, but it sounds like the greetings were not copied over from the posts.

I'll find out exactly what happened with those Monday.

I'll be the first to say this voicemail migration did NOT go as planned, so this coming week we've got to first address any remaining issues with it and then determine where the breakdown in the plan was in terms of what caused it to have so many issues.

It may not have gone as planned; but the voicemail system is shoulders about the previous system. Plus, we are still in beta, so crap should happen at times. As long as you know why, that is all that matters. I definitely think the new voicemail works fine. later... mike....

Just another observation:

When the voice mail notification gets sent to my e-mail address, the date is off by 39 years........:eek:

Voicemail from "Bob's AT&T Cell - Bob's Samsung Blackjack II" <61758XXXX> 00:00:25Message From "Bob's Cell 617584XXXX
Created: Wednesday, December 31 1969, 07 00 PM
Duration: 00:00:25
Account: 212372XXXX@sip.voipwelcome.com

Quote:

---

Originally Posted by NY Tel Guy

Just another observation:

When the voice mail notification gets sent to my e-mail address, the date is off by 39 years........:eek:

Voicemail from "Bob's AT&T Cell - Bob's Samsung Blackjack II" <61758XXXX> 00:00:25Message From "Bob's Cell 617584XXXX
Created: Wednesday, December 31 1969, 07 00 PM
Duration: 00:00:25
Account: 212372XXXX@sip.voipwelcome.com

---

At least we went backwards so we look innovative. Who knew VOIPo'd be emailing out voicemails 15 years before I was born? Now that's an accomplishment.

I'll add this to Monday's list.

Quote:

---

Originally Posted by VOIPoTim

At least we went backwards so we look innovative. Who knew VOIPo'd be emailing out voicemails 15 years before I was born? Now that's an accomplishment.

I'll add this to Monday's list.

---

Wake up, Tim....

You must stop living in the past..;)

Quote:

---

Originally Posted by burris

Wake up, Tim....

You must stop living in the past..;)

---

Yeah reminds me of that movie that was out in the year 2000 entitled "Memento"

If you have not seen it, it is worth picking up a DVD or whatever:

http://www.imdb.com/title/tt0209144/

A rather dark movie, but alright.
IMO If you like that, be sure to see "The Butterfly Effect".
The sequel does not compare though.

Quote:

---

Originally Posted by usa2k

A rather dark movie, but alright.
IMO If you like that, be sure to see "The Butterfly Effect".
The sequel does not compare though.

---

yeah, the sequel definitely wasn't on the same scale. but deja vu is another pretty decent one if you're in to the whole multi-dimensional time travel sort of thing.

maybe if i wasn't so busy watching movies... voicemail would be working now ;)

Quote:

---

Originally Posted by VOIPoRay

yeah, the sequel definitely wasn't on the same scale. but deja vu is another pretty decent one if you're in to the whole multi-dimensional time travel sort of thing.

maybe if i wasn't so busy watching movies... voicemail would be working now ;)

---

lol

As of 12:13 EDT, the 832 838-7000 number is dumping calls to it from my Verizon Wireless cell, and from my AT&T cell it gives me a "your call cannot be completed as dialed message" From my employer's Global Crossing Voip line, it just dumps the call.
If I call myself and let it answer and press *, that works.
Figured you'd want to know.

Quote:

---

Originally Posted by NY Tel Guy

lol

As of 12:13 EDT, the 832 838-7000 number is dumping calls to it from my Verizon Wireless cell, and from my AT&T cell it gives me a "your call cannot be completed as dialed message" From my employer's Global Crossing Voip line, it just dumps the call.
If I call myself and let it answer and press *, that works.
Figured you'd want to know.

---

how about now? i noticed that and it should be fixed as of right now.

Quote:

---

Originally Posted by VOIPoRay

how about now? i noticed that and it should be fixed as of right now.

---

Yup, working now. What was it?

Quote:

---

Originally Posted by NY Tel Guy

Yup, working now. What was it?

---

you don't really wanna know.

more to the point, i dont' really wanna tell you ;-)

it was actually just a small oversight where the two vm systems were "fighting" over that number

MWI should now be working correctly. Anyone still having problems with this please post back.

So, out of curiosity, does this mean that everyone should be migrated to the new system now?

Quote:

---

Originally Posted by fisamo

So, out of curiosity, does this mean that everyone should be migrated to the new system now?

---

That's the theory, yes.... barring any more small issues that might come up. Are you having issues? not noticing anything changed, etc?

Quote:

---

Originally Posted by VOIPoRay

That's the theory, yes.... barring any more small issues that might come up. Are you having issues? not noticing anything changed, etc?

---

I'd wager that "some" of the members here have enough "issues" to write a book.:eek:

Quote:

---

Originally Posted by NY Tel Guy

I'd wager that "some" of the members here have enough "issues" to write a book.:eek:

---

speaking of "issues" are your timestamps still of by several decades?

Quote:

---

Originally Posted by VOIPoRay

That's the theory, yes.... barring any more small issues that might come up. Are you having issues? not noticing anything changed, etc?

---

Sorry for inducing any panic... I haven't noticed any issues, but I haven't checked much, either. One minor issue I had noticed was that some of the old messages were showing up in my vpanel, but when I deleted them, they stayed gone. I haven't tested the system much in the past few days--maybe some tonight, and if I have issues (at least, those I'm willing to discuss... :eek: ), I'll be sure to let you know. :)

Quote:

---

Originally Posted by VOIPoRay

speaking of "issues" are your timestamps still of by several decades?

---

The timestamp on the email and SMS notifications are now correct. The voicemail system voice time stamp is still 4 hours ahead of EDT.
I just left myself a message at 4:57 and that's what the email said however the voice said: 8:57 PM.

We are making progress.
Thanks

How is voicemail working for everyone now since the switch?

Quote:

---

Originally Posted by VOIPoTim

How is voicemail working for everyone now since the switch?

---

Ok since no one else has responded, I'll chime in.

All seems well with:

1. The e-mail time stamp is current
2. The Vpanel time stamp entry is current
3. The 832 838-7000 number works
4. Pressing * when dialing yourself breaks through the outgoing message allowing you to retrieve messages that way.

Still to be resolved:

1. The voice time stamp on the voice mail system is still 4 hours ahead of EDT
2. The "press 5 to return this call" still gets you to a different menu tree.

But overall,it is a much improved system over Aunt Bea....
Anyone else have any additional observations?