News:

On Tuesday September 6th the forum will be down for maintenance from 9:30 PM to 11:59 PM PDT

Main Menu

Firmware update - Jan 30, 2012 2675

Started by Rick, February 01, 2012, 05:21:37 AM

Previous topic - Next topic

Rick

I just noticed that on January 30th Sherman updated the firmware post.  Unfortunately, instead of posting a reply, which would have utilized the "notify" function if you subscribed to the topic, he just edited the post itself.  I've sent him a message asking in the future that he post a reply to utilize that feature.

I don't know what the difference is between 2672 (which OBi pushed to me during testing) and 2675.  The update is listed as:


Enhancements & Fixes in Maintenance Release 1.3.0(2669/2675):
- Fixed Message Waiting indicator (Follow-on corner case fix in 2675)
- Polarity Reversal not enabled by default


I don't know what "corner case fix" means.  And I don't know what the difference is between what I got (2672) and 2675, but I guess I'm going to manually update it.

It would be nice if 2669 was listed separately, explaining what it really did fix, and then 2675 was listed as what it fixed from 2669, i.e. the GV voicemail indicator.

UPDATE 4:15PM

Got a message a while ago, deleted it on GV, indicator that had come on didn't go away.  So I just updated to 2675, must have been an improvement over the 2672 they gave me last week.

RonR

I'm still seeing a lot of failures followed by a ton of retries, so I wouldn't get my hopes up for responsive behavior:

[Feb 01 13:37:30]<7> GTALKVM:Checking VM....
[Feb 01 13:37:30]<7> GTALKVM:state changed from 0 to 1
[Feb 01 13:37:31]<7> TCP:Connect OK(lhttpc)31
[Feb 01 13:37:31]<7> Trying to connect ssl
[Feb 01 13:37:32]<7> TC:ssl connected
[Feb 01 13:37:32]<7> LHC:status code:500
[Feb 01 13:37:32]<7> GGSVC:Invalid response:500
[Feb 01 13:37:32]<7> GTALKVM:Google login failed!
[Feb 01 13:37:32]<7> GTALKVM:state changed from 1 to 2
[Feb 01 13:40:32]<7> GTALKVM:Checking VM....
[Feb 01 13:40:32]<7> GTALKVM:state changed from 2 to 1
[Feb 01 13:40:33]<7> TCP:Connect OK(lhttpc)48
[Feb 01 13:40:33]<7> Trying to connect ssl
[Feb 01 13:40:33]<7> TC:ssl connected
[Feb 01 13:40:34]<7> LHC:Response OK
[Feb 01 13:40:34]<7> LHC:set Retrying:www.google.com, 1
[Feb 01 13:40:34]<7> LHC:retrying...www.google.com
[Feb 01 13:40:34]<7> TCP:Connect OK(lhttpc)49
[Feb 01 13:40:34]<7> Trying to connect ssl
[Feb 01 13:40:35]<7> TC:ssl connected
[Feb 01 13:40:35]<7> LHC:set Retrying:www.google.com, 1
[Feb 01 13:40:36]<7> LHC:retrying...www.google.com
[Feb 01 13:40:36]<7> TCP:Connect OK(lhttpc)50
[Feb 01 13:40:36]<7> Trying to connect ssl
[Feb 01 13:40:36]<7> TC:ssl connected
[Feb 01 13:40:37]<7> LHC:set Retrying:www.google.com, 1
[Feb 01 13:40:37]<7> LHC:retrying...www.google.com
[Feb 01 13:40:37]<7> TCP:Connect OK(lhttpc)51
[Feb 01 13:40:37]<7> Trying to connect ssl
[Feb 01 13:40:38]<7> TC:ssl connected
[Feb 01 13:40:39]<7> LHC:set Retrying:www.google.com, 1
[Feb 01 13:40:39]<7> LHC:retrying...www.google.com
[Feb 01 13:40:39]<7> TCP:Connect OK(lhttpc)52
[Feb 01 13:40:39]<7> Trying to connect ssl
[Feb 01 13:40:40]<7> TC:ssl connected
[Feb 01 13:40:40]<7> LHC:Response OK
[Feb 01 13:40:40]<7> TCP:Connect OK(lhttpc)53
[Feb 01 13:40:40]<7> Trying to connect ssl
[Feb 01 13:40:41]<7> TC:ssl connected
[Feb 01 13:40:41]<7> LHC:set Retrying:www.google.com, 0
[Feb 01 13:40:41]<7> LHC:retrying...www.google.com
[Feb 01 13:40:41]<7> TCP:Connect OK(lhttpc)54
[Feb 01 13:40:41]<7> Trying to connect ssl
[Feb 01 13:40:42]<7> TC:ssl connected
[Feb 01 13:40:42]<7> LHC:set Retrying:www.google.com, 0
[Feb 01 13:40:42]<7> LHC:retrying...www.google.com
[Feb 01 13:40:43]<7> TCP:Connect OK(lhttpc)55
[Feb 01 13:40:43]<7> Trying to connect ssl
[Feb 01 13:40:43]<7> TC:ssl connected
[Feb 01 13:40:44]<7> LHC:set Retrying:www.google.com, 0
[Feb 01 13:40:44]<7> LHC:retrying...www.google.com
[Feb 01 13:40:44]<7> TCP:Connect OK(lhttpc)56
[Feb 01 13:40:44]<7> Trying to connect ssl
[Feb 01 13:40:44]<7> TC:ssl connected
[Feb 01 13:40:46]<7> LHC:Response OK
[Feb 01 13:40:46]<7> GTALKVM:Check VM Succ
[Feb 01 13:40:46]<7> GTALKVM:state changed from 1 to 0
[Feb 01 13:40:46]<7> GTALKVM:VM:0

[Feb 01 13:49:53]<7> GTALKVM:Checking VM....
[Feb 01 13:49:53]<7> GTALKVM:state changed from 0 to 1
[Feb 01 13:49:54]<7> TCP:Connect OK(lhttpc)25
[Feb 01 13:49:54]<7> Trying to connect ssl
[Feb 01 13:49:55]<7> TC:ssl connected
[Feb 01 13:49:55]<7> LHC:status code:500
[Feb 01 13:49:55]<7> GGSVC:Invalid response:500
[Feb 01 13:49:55]<7> GTALKVM:Google login failed!
[Feb 01 13:49:55]<7> GTALKVM:state changed from 1 to 2
[Feb 01 13:52:55]<7> GTALKVM:Checking VM....
[Feb 01 13:52:55]<7> GTALKVM:state changed from 2 to 1
[Feb 01 13:52:55]<7> TCP:Connect OK(lhttpc)27
[Feb 01 13:52:55]<7> Trying to connect ssl
[Feb 01 13:52:56]<7> TC:ssl connected
[Feb 01 13:52:56]<7> LHC:Response OK
[Feb 01 13:52:56]<7> LHC:set Retrying:www.google.com, 1
[Feb 01 13:52:57]<7> LHC:retrying...www.google.com
[Feb 01 13:52:57]<7> TCP:Connect OK(lhttpc)28
[Feb 01 13:52:57]<7> Trying to connect ssl
[Feb 01 13:52:57]<7> TC:ssl connected
[Feb 01 13:52:58]<7> LHC:set Retrying:www.google.com, 1
[Feb 01 13:52:58]<7> LHC:retrying...www.google.com
[Feb 01 13:52:58]<7> TCP:Connect OK(lhttpc)29
[Feb 01 13:52:58]<7> Trying to connect ssl
[Feb 01 13:52:59]<7> TC:ssl connected
[Feb 01 13:52:59]<7> LHC:set Retrying:www.google.com, 1
[Feb 01 13:53:00]<7> LHC:retrying...www.google.com
[Feb 01 13:53:00]<7> TCP:Connect OK(lhttpc)30
[Feb 01 13:53:00]<7> Trying to connect ssl
[Feb 01 13:53:00]<7> TC:ssl connected
[Feb 01 13:53:01]<7> LHC:set Retrying:www.google.com, 1
[Feb 01 13:53:01]<7> LHC:retrying...www.google.com
[Feb 01 13:53:01]<7> TCP:Connect OK(lhttpc)31
[Feb 01 13:53:01]<7> Trying to connect ssl
[Feb 01 13:53:02]<7> TC:ssl connected
[Feb 01 13:53:02]<7> LHC:Response OK
[Feb 01 13:53:02]<7> TCP:Connect OK(lhttpc)32
[Feb 01 13:53:02]<7> Trying to connect ssl
[Feb 01 13:53:03]<7> TC:ssl connected
[Feb 01 13:53:03]<7> LHC:set Retrying:www.google.com, 0
[Feb 01 13:53:03]<7> LHC:retrying...www.google.com
[Feb 01 13:53:03]<7> TCP:Connect OK(lhttpc)33
[Feb 01 13:53:03]<7> Trying to connect ssl
[Feb 01 13:53:04]<7> TC:ssl connected
[Feb 01 13:53:04]<7> LHC:set Retrying:www.google.com, 0
[Feb 01 13:53:04]<7> LHC:retrying...www.google.com
[Feb 01 13:53:04]<7> TCP:Connect OK(lhttpc)34
[Feb 01 13:53:04]<7> Trying to connect ssl
[Feb 01 13:53:05]<7> TC:ssl connected
[Feb 01 13:53:05]<7> LHC:set Retrying:www.google.com, 0
[Feb 01 13:53:06]<7> LHC:retrying...www.google.com
[Feb 01 13:53:06]<7> TCP:Connect OK(lhttpc)35
[Feb 01 13:53:06]<7> Trying to connect ssl
[Feb 01 13:53:06]<7> TC:ssl connected
[Feb 01 13:53:07]<7> LHC:Response OK
[Feb 01 13:53:07]<7> GTALKVM:Check VM Succ
[Feb 01 13:53:07]<7> GTALKVM:state changed from 1 to 0
[Feb 01 13:53:07]<7> GTALKVM:VM:0

RevKev

I still don't get any voice mail notification - from LINE (cable co.) or sp1 (GV).

pc44

Any chance this is a problem on Google's end?  On one of my Obis, I am still using Firmware 1.2.1 (Build: 2384) and seem to have lost the voicemail notification right about the same time you guys did too.

pc44

everest1

I got touch tone errors after this upgrade. I called a calling card (408-385-0100) to make international calls tonight and it kept saying that I provided an invalid phone number. Then, I tried my AT&T landline, which worked.

So, I rolled back to 2669, called the calling card #  again, everything is back to normal.

I will stay on 2669 for now.

Stewart

Quote from: everest1 on February 08, 2012, 08:21:59 PMI called a calling card (408-385-0100) to make international calls tonight ...
IMO, a calling card is rarely a good value.  You can almost always get better quality and reliability and/or a lower price from a VoIP provider (that's what the OBi is for!).  In addition, you avoid the hassle of two-stage dialing and get faster call setup.

I'll try to suggest better alternatives.  Who is the calling card company?  What countries are you calling?  Landlines or cellular? Approximate monthly minutes usage?

everest1

#6
Well, I totally agree. That's likely to be the last calling card. I bought OBiTalk 110 less than a month ago.
I may go with Google Voice's international long distance. Before I do that, I need to use all (or most) minutes on that card.

The calling card is still needed for my cell phones.

The calling card costs 1.5 cents/min to China, which is slightly better than GV's 2 cents/min.

Stewart

Quote from: everest1 on February 08, 2012, 09:56:54 PMThe calling card is still needed for my cell phones.
Most VoIP providers include calling card access.  For those that don't, you can call the OBi from your cell phone, then use the auto-attendant to call out on another service.

The ratings below are my personal opinion.  Prices to China are in US cents per minute, billing is 60/60 unless otherwise noted.

Tops in quality, reliability and support are Anveo (1.3 - 1.6, 30/6 billing) and Callcentric (1.32).  Either of these also recommended for 911 service.  Callcentric includes calling card.  I believe that Anveo offers a few minutes free trial.

Voxbeam (Premium route) (0.77 - 0.91, 1/1 billling) is high quality, but lower reliability.  Only practical for heavy use; minimum payment of $50 expires after one year.  $1 free trial.

Localphone (1.0 - 1.2) and Rebtel (1.9), in addition to VoIP access, allow you to dial a local number for each contact, which rings them directly.  Rebtel has access in China, so your contacts can easily call you.  They also have a scheme where the called party hangs up and calls back the local number displayed; there are then no charges by Rebtel (though your contact may have to pay for the local call).  Both offer a few minutes free trial.

CallWithUs, Future-Nine and VoIP.ms allow choice of multiple routes, at different price/quality levels, some less than one cent.  CWU and F9 include calling card access.

Bottom of the barrel, try Betamax http://backsla.sh/betamax .  Some offer "free" calls, but those come with complex rules and may not be a good deal.  Some offer straightforward calling at 0.5 cents.  All have calling card access (including from China), but some have a surcharge for non-VoIP calls.  Some offer a few minutes free trial.

Rick

Today I rec'd a voicemail, and the indicator lit up on the phone.  I deleted the message online on GV, and minnutes later the indicator on the phone turned off.  So it appears to be working fine for me.

everest1

Thank you so much, Stewart.
It's very helpful!


Quote from: Stewart on February 08, 2012, 11:09:14 PM
Most VoIP providers include calling card access.  For those that don't, you can call the OBi from your cell phone, then use the auto-attendant to call out on another service.

The ratings below are my personal opinion.  Prices to China are in US cents per minute, billing is 60/60 unless otherwise noted.

Tops in quality, reliability and support are Anveo (1.3 - 1.6, 30/6 billing) and Callcentric (1.32).  Either of these also recommended for 911 service.  Callcentric includes calling card.  I believe that Anveo offers a few minutes free trial.

Voxbeam (Premium route) (0.77 - 0.91, 1/1 billling) is high quality, but lower reliability.  Only practical for heavy use; minimum payment of $50 expires after one year.  $1 free trial.

Localphone (1.0 - 1.2) and Rebtel (1.9), in addition to VoIP access, allow you to dial a local number for each contact, which rings them directly.  Rebtel has access in China, so your contacts can easily call you.  They also have a scheme where the called party hangs up and calls back the local number displayed; there are then no charges by Rebtel (though your contact may have to pay for the local call).  Both offer a few minutes free trial.

CallWithUs, Future-Nine and VoIP.ms allow choice of multiple routes, at different price/quality levels, some less than one cent.  CWU and F9 include calling card access.

Bottom of the barrel, try Betamax http://backsla.sh/betamax .  Some offer "free" calls, but those come with complex rules and may not be a good deal.  Some offer straightforward calling at 0.5 cents.  All have calling card access (including from China), but some have a surcharge for non-VoIP calls.  Some offer a few minutes free trial.