I have a Linksys PAP2T ATA, and I have both the MWI SERV (Message Waiting Indicator Servie) and The VMWI Serv (Voice Mail Waiting Indicator Service) set to Yes (Default Setting), problem is I get the stuttered dial tone all the time whe I pick up the reciever, regardless if there are any messages or not. I've tried changing the settings around, and I can get the stuttered dial tone to stop by doing so, but then when a new message does come in the stutterd dial tone does not work. Not sure if there is a different setting I need to change, any ideas?
Thx
Message Waiting Indicator
-
- Quiet One
- Posts: 46
- Joined: 03/08/2012
- SIP Device Name: Linksys PAP2T
- Firmware Version: 5.1.6
- ISP Name: Cable
- Router: Linksys E4200 V2
-
- Tried and True
- Posts: 362
- Joined: 09/18/2009
- SIP Device Name: Zoiper| Grandstream GXP2000
- ISP Name: Tek Savvy Internet (DSL)
- Computer OS: CentOS, Arch, Widows 7, AIX, AS/400
- Router: Cisco ASA 5520
- Smartphone Model: Samsung Galaxy Ace Q
- Android Version: 2.3.6
- Location: Simcoe County
Re: Message Waiting Indicator
Just from reading other posts. If your voltage/ringer settings aren't correct you may get a stutter tone. Check that you're at 52 and 90, I believe Sinusoidal.
Edit:
(In addition to voice-mail indicators.)
It's been a while since I've used a Pap2T, I believe it has voltage settings by level? Level 8/9 which ever is the last one is 49.5v which should be compatible with any North American system.
Keep us posted as other settings may also play into this.
Edit:
(In addition to voice-mail indicators.)
It's been a while since I've used a Pap2T, I believe it has voltage settings by level? Level 8/9 which ever is the last one is 49.5v which should be compatible with any North American system.
Keep us posted as other settings may also play into this.
-
- Quiet One
- Posts: 46
- Joined: 03/08/2012
- SIP Device Name: Linksys PAP2T
- Firmware Version: 5.1.6
- ISP Name: Cable
- Router: Linksys E4200 V2
Re: Message Waiting Indicator
Thanks for the suggestion Bloodsong, turns out the issue was with FPL and was effecting multiple users, they made some changes on their end and it seems to have resolved the issue.