Message waiting indicator not working

Have a question or problem with your Fongo application? This forum is the place to get help from both staff and fellow community members.
Fongo recommends Fongo Home Phone for a fully supported Home Phone system for only $4.95/mo
streetcore
Quiet One
Posts: 43
Joined: 11/19/2012
SIP Device Name: OBihai OBi200
Firmware Version: 3.1.1 (Build: 5463EX
ISP Name: Cogeco (Cable)
Computer OS: Mac OSX 10.11.6, Windows 8
Router: D-Link DIR-615
Location: Canada

Message waiting indicator not working

Post by streetcore »

I bought the VOIP unlock key today and got things set up with the Linksys PAP2T-NA. Everything seems to be working okay, except for the message waiting indicator (change in dial tone or blinking light on phone when someone has left a voice message). I've left a few messages myself, so I know there's a message waiting, and I've also checked that the ATA settings for MWI and VMWI are set to "yes".

Am I missing anything? Does this feature even work with freephoneline?

Thanks.
User avatar
Jake
Technical Support
Posts: 2837
Joined: 10/18/2009

Re: Message waiting indicator not working

Post by Jake »

Yes it does work. Sometimes there is a bit of a delay in the MWI being activated or deactivated on FPL's side. Wait a couple of minutes and see if it comes on before you listen to the message.
streetcore
Quiet One
Posts: 43
Joined: 11/19/2012
SIP Device Name: OBihai OBi200
Firmware Version: 3.1.1 (Build: 5463EX
ISP Name: Cogeco (Cable)
Computer OS: Mac OSX 10.11.6, Windows 8
Router: D-Link DIR-615
Location: Canada

Re: Message waiting indicator not working

Post by streetcore »

Thanks for your reply. I left the message at 7:30pm last night. It's now almost 10am the next morning and there's still no indication that a message is waiting. I called in to make sure the message was there and the voice said "you have one new message".
streetcore
Quiet One
Posts: 43
Joined: 11/19/2012
SIP Device Name: OBihai OBi200
Firmware Version: 3.1.1 (Build: 5463EX
ISP Name: Cogeco (Cable)
Computer OS: Mac OSX 10.11.6, Windows 8
Router: D-Link DIR-615
Location: Canada

Re: Message waiting indicator not working

Post by streetcore »

I was just checking the PAP2T configuration again and on the Info page for Line 1 it says "Message Waiting:No" even though there are now two messages waiting since I left a new one this morning. Other fields such as "Last Called Number" are showing the correct info.
streetcore
Quiet One
Posts: 43
Joined: 11/19/2012
SIP Device Name: OBihai OBi200
Firmware Version: 3.1.1 (Build: 5463EX
ISP Name: Cogeco (Cable)
Computer OS: Mac OSX 10.11.6, Windows 8
Router: D-Link DIR-615
Location: Canada

Re: Message waiting indicator not working

Post by streetcore »

Can anyone help with this please? If freephoneline supports this feature, I'd really like to get it working.

Thanks.
Bing Kol
Active Poster
Posts: 117
Joined: 07/23/2010
SIP Device Name: PAP2T
Firmware Version: 5.1.6 (LS)
ISP Name: CarryTel 25/10 DSL
Router: pfSense i5-3470
Location: GTA

Re: Message waiting indicator not working

Post by Bing Kol »

streetcore wrote:Can anyone help with this please? If freephoneline supports this feature, I'd really like to get it working.

Thanks.
The lack of comment from moderators after 2 days should tell you enough that the feature is not worth it.


Investing in a DECT 6.0 handset with a good voicemail (aka answering machine) could save yourself from possible cardiac arrest trying to make the FPL voicemail work properly.

Once you have that, go to your online account and change the number of rings before voicemail to 5. Then set your handset to pickup calls that you don't answer after the 4th ring.

Good luck!
streetcore
Quiet One
Posts: 43
Joined: 11/19/2012
SIP Device Name: OBihai OBi200
Firmware Version: 3.1.1 (Build: 5463EX
ISP Name: Cogeco (Cable)
Computer OS: Mac OSX 10.11.6, Windows 8
Router: D-Link DIR-615
Location: Canada

Re: Message waiting indicator not working

Post by streetcore »

Thanks for your response. I do have a DECT 6.0 handset now with an answering machine, but using that machine would seem like a step backward. The MWI is not a deal breaker and the email notification works, which is nice, but if MWI is supposed to work I would like to figure out why it isn't.

Cheers.
Bing Kol
Active Poster
Posts: 117
Joined: 07/23/2010
SIP Device Name: PAP2T
Firmware Version: 5.1.6 (LS)
ISP Name: CarryTel 25/10 DSL
Router: pfSense i5-3470
Location: GTA

Re: Message waiting indicator not working

Post by Bing Kol »

The feature DOES work, I did not say it doesn't! However, it could take from a minute to several hours to receive your message and the same length of time to get them deleted. :(
streetcore
Quiet One
Posts: 43
Joined: 11/19/2012
SIP Device Name: OBihai OBi200
Firmware Version: 3.1.1 (Build: 5463EX
ISP Name: Cogeco (Cable)
Computer OS: Mac OSX 10.11.6, Windows 8
Router: D-Link DIR-615
Location: Canada

Re: Message waiting indicator not working

Post by streetcore »

I didn't disagree with you and said Thanks and Cheers for taking the time to try and help. So why the angry face?

I understand it may take some time for the MWI indicator to work, but I've had new messages for two days now and I'm still not receiving any indication they are there.

Thanks again.
Bing Kol
Active Poster
Posts: 117
Joined: 07/23/2010
SIP Device Name: PAP2T
Firmware Version: 5.1.6 (LS)
ISP Name: CarryTel 25/10 DSL
Router: pfSense i5-3470
Location: GTA

Re: Message waiting indicator not working

Post by Bing Kol »

streetcore wrote:I didn't disagree with you and said Thanks and Cheers for taking the time to try and help. So why the angry face?

I understand it may take some time for the MWI indicator to work, but I've had new messages for two days now and I'm still not receiving any indication they are there.

Thanks again.
That is not an angry face...it is a sad face! And it is for the MWI feature that had not been fixed for as long as I can remember.
Bing Kol
Active Poster
Posts: 117
Joined: 07/23/2010
SIP Device Name: PAP2T
Firmware Version: 5.1.6 (LS)
ISP Name: CarryTel 25/10 DSL
Router: pfSense i5-3470
Location: GTA

Re: Message waiting indicator not working

Post by Bing Kol »

streetcore wrote: ..., but I've had new messages for two days now and I'm still not receiving any indication they are there.

Thanks again.
Exactly my point...several hours could extend to days...weeks (I hope not)!
streetcore
Quiet One
Posts: 43
Joined: 11/19/2012
SIP Device Name: OBihai OBi200
Firmware Version: 3.1.1 (Build: 5463EX
ISP Name: Cogeco (Cable)
Computer OS: Mac OSX 10.11.6, Windows 8
Router: D-Link DIR-615
Location: Canada

Re: Message waiting indicator not working

Post by streetcore »

Sorry if I misunderstood the emoticon. I've been doing lots of searching and have read others complaining about the MWI, so it's good to know I'm not alone.

I was also trying different settings on the SIP and under User 1 if I set "Message Waiting" to "yes" the indictors on my phones (stuttering tone, flashing light, and VM on display) all work properly. This setting seems to force it into the message waiting mode and the indicators stay on whether there are messages or not, but at least I know the phones are communicating with the SIP. So I guess my problem lies with the fpl servers.
User avatar
FONGO_steve
Site Moderator
Posts: 2131
Joined: 07/16/2009
SIP Device Name: Grandstream 286 & 701
ISP Name: Worldline.ca
Computer OS: Windows 7 Ultimate / Mac OS X
Router: TR1043ND w/ DD-WRT Mega
Smartphone Model: Galaxy S3
Android Version: 4.0.4
Location: Cambridge

Re: Message waiting indicator not working

Post by FONGO_steve »

At this time we can't find any MWI related issues on our end. My test on the Grandstream on my desk yielded a fairly fast MWI response (within about a minute or so, but I wasn't timing).

I notice you're both using PAP2T ATAs. Do we have any other forum members reading the board who are using PAP2Ts and can maybe chime up with their configuration, or whether they're having issues?
Steve
Fongo
Development Support Specialist.
cu2o2o2
Lightly Seasoned
Posts: 227
Joined: 04/06/2010
SIP Device Name: Double-NAT PAP2T-NA
Firmware Version: 5.1.6 (LS)
ISP Name: Rogers Express with SB5101
Computer OS: Win7 32-bit for DV softphone
Router: WNR3500L behind DIR-615C1
Location: Brampton, ON

Re: Message waiting indicator not working

Post by cu2o2o2 »

FONGO_steve wrote:At this time we can't find any MWI related issues on our end. My test on the Grandstream on my desk yielded a fairly fast MWI response (within about a minute or so, but I wasn't timing).

I notice you're both using PAP2T ATAs. Do we have any other forum members reading the board who are using PAP2Ts and can maybe chime up with their configuration, or whether they're having issues?

Interesting! Although I have a PAP2T, I never had used the native FPL MWI. I have a setup on my own that works for me.

I do receive voicemails on my DV softphone but never bothered to check the time the caller actually left the voicemail. So I wouldn't know if there was a substantial delay in receiving them.

I did a few tests today from 3 different cellphone providers (Rogers, Telus and Mobilicity) that I have access to, and found out that I get the voicemail fairly fast (all within a minute). From my few tests, it suggests that FONGO_steve's observation about MWI is valid. But then again, it could be just a fluke!

If we can get more inputs (positive/negative) from those with PAP2T's (or any Linksys ATA), then we can draw a better perspective of the "problem".
.

You agree to read my posts at your own risk.
tyuen
One Hit Wonder
Posts: 1
Joined: 12/09/2012

Re: Message waiting indicator not working

Post by tyuen »

Hi, I am a new Freephoneline user, and I am using a Cisco SPA-112. I am experiencing something similar. I have cleared my voice messages, but the Message Waiting Indicator is still set to "Yes", even after I have restarted the Cisco device. Is there still some kind of known problems with the Message Waiting Indicator?

One more point, when I tested having a voice message, I got the email from Freeephoneline almost instantly. However, the Message Waiting Indicator came perhaps quite a few minutes afterwards. Since then, it hasn't gone away.