“stutter” dial tone for Google Voice message indication
OBiSupport:
http://www.obihai.com/FAQ.html#12
Stutter tone is played by OBi to indicate there is/are "outstanding" voicemail(s).
This indication is sent by the Service Provider to OBi.
If you have GV on your SP1 and SP2, from phone connected to OBi 's PHONE port
Dial your Google Voice number1 to check your SP1's voicemail.
Dial **2 your_Google_Voice_Number2, and check your SP2's voicemail.
Also Make sure you don't have "Place missed calls in the inbox" checked:
http://www.obihai.com/googlevoiceFAQ.html#11
crystal19:
I have ObiTalk110 with Googlevoice set as SP1.
I am having problems with not getting voicemail indicator that I have a voicemail. If I dial my own number I can hear the voicemail. But my phone does not indicate me that I have voicemail. I have following settings
MWIEnable has value of grayedout checked box with red ! mark. and device default is unchecked and ObiTalk setting is checked with *
Same thing with X_VMWIEnable
and some how I cannnot find MessageWaiting checkbox anywhere on the menu.
1) Is all this red ! marks are bad? How do I reset the whole thing? I tried to reset the ObiTalk device by doing hardware reset - red ! mark did not go away. Also there are many other places where there is red ! marks.
2) How do I get voicemail indicator to come on?
3) People talk about system logs, where can I find them? I believe I am using webportal I believe.
RonR:
Google Voice voicemail checking is not working in the OBi at the present time. There is nothing you can do to fix it.
crystal19:
Ok Now I am not using webportal but direct ip address to connect. I do see Message Waiting and when I turned on, I do get indicator on my phone that I have a new voice mail. However, it does not get turned off when I delete GV thru GV interface. Any idea?
Also again anybody know how can I view syslogs?
Thanks
RonR:
Did you miss the post just prior to your last one? All OBi's are currently failing to check VM properly:
[Jan 08 21:55:10]<7> GTALKVM:Checking VM....
[Jan 08 21:55:10]<7> GTALKVM:state changed from 2 to 1
[Jan 08 21:55:11]<7> TCP:Connect OK(lhttpc)39
[Jan 08 21:55:11]<7> Trying to connect ssl
[Jan 08 21:55:12]<7> TC:ssl connected
[Jan 08 21:55:12]<7> LHC:set Retrying:www.google.com, 0
[Jan 08 21:55:12]<7> LHC:retrying...www.google.com
[Jan 08 21:55:12]<7> TCP:Connect OK(lhttpc)40
[Jan 08 21:55:12]<7> Trying to connect ssl
[Jan 08 21:55:13]<7> TC:ssl connected
[Jan 08 21:55:13]<7> LHC:status code:302
[Jan 08 21:55:13]<7> LHC:set Retrying:www.google.com, 1
[Jan 08 21:55:13]<7> LHC:retrying...www.google.com
[Jan 08 21:55:13]<7> TCP:Connect OK(lhttpc)41
[Jan 08 21:55:13]<7> Trying to connect ssl
[Jan 08 21:55:14]<7> TC:ssl connected
[Jan 08 21:55:14]<7> LHC:status code:302
[Jan 08 21:55:14]<7> GTALKVM:Google login failed!
I suspect a firmware update will be required to correct this problem.
You can run a syslog server on your PC and point the OBi toward it at:
System Management -> Device Admin -> Syslog -> Server
Navigation
[0] Message Index
[#] Next page
[*] Previous page