Voice Mail: Message Waiting Indicator - Must Press # to Send

Posts: 1389 · Posted: Sat Oct 29, 2005 6:11 pm Post subject:

Now Galion,
If you are going to leave yourself wide open with a comment like that... Wink

Posts: 2

ChrisFix wrote:

From my experimentation, in order to have VM set the Message Waiting Indicator (light and stutter dial-tone), you must press # # after recording the message. If you just hang up, the message is recorded and shows up in your VM, but no indicator is sent.

Is this consistent with other users systems and experiences? It would seem logical to me that if the VM is going to be saved when you hang-up, that it would also send the MWI as well.

For reference, my setup is:

TWC -> WRT54G -> PAP2

I have recently - within the past week - had a problem with the stutter and MWI. I have email message enabled and have found that on the first message left, the email states that there are Zero unreviewed messages when the caller did leave a new voice mail. I am not sure if it maybe related to an older - saved - vm left over when the new call comes in. If a second vm comes in, the email message then states the correct number of unreviewed messages.

I am also using a WRT54G -> PAP2

Posts: 282 · Posted: Tue Nov 01, 2005 2:40 pm Post subject:

After leaving myself more messages than I care to admit, what I've discovered is that I'm getting MWI about 50% of the time overall - it doesn't matter whether I press # at the end of the recording or not (although initially it appeared that way to me). I also noticed that when MWI wasn't sent, and then another message is left that does send MWI, it then sends multiple MWI messages, with the result often being that the MWI is out of synch with the actual state of the message - blinking when the messages are deleted, not blinking when there are new messages.

In talking with CS they stated they are relocating the VM servers and that I should give it a couple of weeks to see if it gets corrected. I don't use VM that much, so for me it isn't a big deal, but I would like it to work consistently which it currently isn't.

Posts: 233 · Posted: Tue Nov 01, 2005 4:49 pm Post subject:

I'm beginning to wonder when we see anomalies like this if we should tally which adapter is involved. Why? Because I have had no problems with my PAP2. I am beginning to think that juggling an array of adapters and keeping the code current could be a clue. If you are reading this thread and have voice mail indicator problems with the PAP2 please post.

I know a lot of you guys like having the router built into the adapter, but I feel like separating the two may help. But, that is strictly an opinion and I have no technical foundation to solidify the statement.

Posts: 3198 · Posted: Tue Nov 01, 2005 4:59 pm Post subject:

did you look two posts above yours? it contains reference to that users device (pap2) and a quote from chrisfix earlier in the thread, who also states he's using a pap2.

Posts: 282 · Posted: Tue Nov 01, 2005 5:02 pm Post subject:

galion wrote:

Why? Because I have had no problems with my PAP2. I am beginning to think that juggling an array of adapters and keeping the code current could be a clue. If you are reading this thread and have voice mail indicator problems with the PAP2 please post.

I started this thread because I was seeing problems with my VM notification, and my setup is actually the same as yours:
TWC -> WRT54G -> PAP2

Posts: 233 · Posted: Tue Nov 01, 2005 5:14 pm Post subject:

Oops. I should have looked back further. Now I am going to go home and tinker.

Posts: 282 · Posted: Tue Nov 01, 2005 5:23 pm Post subject:

Hey, we'll cut you some slack - after all you are the Member of the Week!! Very Happy

Posts: 26 · Posted: Wed Nov 02, 2005 12:15 pm Post subject:

Same problem here and I'm using a PAP2. My VMWI problems started back on Oct. 15th.

CS has already sent me a replacement PAP2 and that didn't work. They wanted me to send THAT one back as well. I mean, what are the odds that two would go bad in a row?

No. This has to be something else.

Posts: 282 · Posted: Wed Nov 02, 2005 1:48 pm Post subject:

I agree with you, it's not very likely to be the PAP2 at fault here. The MWI is simply a data packet that is sent, not much different than receiving caller id, and as far as I can tell, MWI works correctly IF the MWI info is actually sent by Vonage. One of the two techs in NJ I spoke to said that they were physically relocating the VM servers, and while not able to specifically point to why that would be the problem, it makes more sense than the PAP2 being bad.