May 21, 2018, 11:36:30 am *
Welcome, Guest. Please login or register.
News:
 
   Forum Home   Search Login Register OBiTALK  
Pages: 1 ... 12 13 [14]
  Print  
Author Topic: Firmware update for 20x series  (Read 232399 times)
zorlac
Full Member
***
Posts: 213



« Reply #260 on: May 14, 2018, 06:33:08 pm »

Just let the system push the update to your device automatically.
The only way for me to get to SoftwareVersion 3.2.2 (Build: 5859EX) was to delete my obi200 from the portal and reconfigure sp1-3 from scratch.
***6 or rebooting got me nowhere with my existing 3.2.1 (Build: 5794EX) fw.
So much for their "push" service.  Huh
I'd just like the ability to flash it myself, other ATA's & routers expect you to be able to flash their device so just give me the option!

Please PolyCom put up a REAL ftp site.....PLEASE!!!
« Last Edit: May 14, 2018, 06:47:40 pm by zorlac » Logged
SteveInWA
Hero Member & Beta Tester
*****
Posts: 4513



« Reply #261 on: May 14, 2018, 06:39:10 pm »

Just let the system push the update to your device automatically.
The only way for me to get to SoftwareVersion 3.2.2 (Build: 5859EX) was to delete my obi200 from the portal and reconfigure sp1-3 from scratch.
***6 got me nowhere with my existing 3.2.1 (Build: 5794EX)

Please PolyCom put up a REAL ftp site.....PLEASE!!!

So far, the reported cases of 200/202s not upgrading automatically were caused by user modifications to the device.  Factory resetting and re-doing everything fixes it.  Manually downloading the firmware would not likely have helped, in this particular case, as you'd probably never figure out which customization was causing the problem.
Logged

zorlac
Full Member
***
Posts: 213



« Reply #262 on: May 14, 2018, 07:02:25 pm »

Manually downloading the firmware would not likely have helped, in this particular case, as you'd probably never figure out which customization was causing the problem.
But I'd still be able to flash the obi fw if I could just get the stupid file!
Now I have to re-figure out how to fix the pregnant pause after Anveo's 911 test, that used to work before I deleted Anveo from SP3.  Roll Eyes

In case it helps someone else, this is the delay fix courtesy of AZROBERT

When you don't explicitly define a rule for a number in a DigitMap, the dialed number will match the catch all rule "xx.". When this happens you will get a 10 second delay. Without seeing your configuration I guessing you have 911 defined, but not 933.

Find the 911 definition. It should be in the Phone Port DigitMap or the DigitMap for Anveo.

Physical Interfaces -> Phone Port -> DigitMap

Change 911 to 911S0|933S0

When you define 911 there will be a 2 second delay.
With the S + zero suffix there will be no delay.

([1-9]x?*(Mpli)|[1-9]S9|[1-9][0-9]S9|911S0|933S0|**0|***|#|##|**70(Mli)|**8(Mbt)|**81(Mbt)|**82(Mbt2)|**1(Msp1)|**2(Msp2)|**3(Msp3)|**4(Msp4)|**9(Mpp)|(Mpli))

Default config below.

([1-9]x?*(Mpli)|[1-9]S9|[1-9][0-9]S9|911|**0|***|#|##|**70(Mli)|**8(Mbt)|**81(Mbt)|**82(Mbt2)|**1(Msp1)|**2(Msp2)|**3(Msp3)|**4(Msp4)|**9(Mpp)|(Mpli))
« Last Edit: May 14, 2018, 07:42:40 pm by zorlac » Logged
chilirock
Jr. Member
**
Posts: 76


« Reply #263 on: May 15, 2018, 09:35:42 am »

But, that setting usually comes into play AFTER you connect to the called party, and you are saying that the friend can't even key in *123 to reach CC VM?  That's sounds like a digit map problem.  Can it call ANY number?
Regarding "Can it call ANY number?", yes, dialing other numbers and connecting to calls are working as normal, fine.

Regarding, "Sounds like digit map problem", that's what I suspected as well. It seems like the Obi is just not registering the number string that I dialed. It must not be matched to one of the dialing strings so it waits and eventually gives me a fast busy tone.

After looking closer at the settings, and comparing against those from another Obi200 device setup with a different CallCentric account, I noticed that the "*123" was missing from the DigitMap under Service Providers >> ITSP Profile (for Callcentric) >> General. I don't know why this would be missing from one device and not the other. I thought I set them both up the same way using the ObiTalk portal, yet one had the "|*123|" in the DigitMap and the other did not.

I tried removing the CallCentric account from the Obi with the missing string and re-adding it. That did not help. When I re-added the CallCentric account it seems to have retained all of the previous ObitTalk portal settings associated with the deleted account, e.g. I set a static IP for the Obi200. Is that normal? I expected it to delete all settings associated with the CC account and require me to add them back.

I had to manually go uncheck the two boxes next to DigitMap and add the missing string then submit the changes for them to be applied. All is working now with the CC VM, I just haven't determined the root cause for the missing string in the first place. Any ideas?
Logged
RFC3261
Full Member
***
Posts: 171


« Reply #264 on: May 15, 2018, 10:59:31 am »

But I'd still be able to flash the obi fw if I could just get the stupid file!
Perhaps I am reading too much into the words, but it seems to me that those that are paid by the companies involved (either directly, or indirectly) have made it pretty clear that if you want to use an OBi (especially with GV), you are going to have to learn to live within their ecosystem and the way they have chosen to move forward and deliver service.  If you do not like what Obihai and Google are doing (and some will not), you should probably start the planning of your move to one of the alternatives available to you.  A number of vendors (some actively participating on this board) have offered to help you move to their service(s).  The OBi devices (and/or the GV service) were never for everyone.
Logged
JohnRadu
Newbie
*
Posts: 1


« Reply #265 on: May 15, 2018, 08:23:54 pm »

After spending hours trying to fix a seemingly defective automatic firmware update (power light flashed green, then after unplugging/replugging flashed red/green), I finally found a solution that worked for me. It does not seem like the flashing process is the problem. The problem seems to be when the device reboots and tries to reinitialize. That's when it gets hung up.

The solution:  Factory-Reset. (***Note: it may take several factory resets to actually get solid green power light***)

Instructions: https://www.obitalk.com/info/faq/Troubleshooting-sec/How-to-Factory-Reset

I really had to factory reset several times for it to finally boot up correctly and have a solid power light, but then I was able to re-register the device on obitalk.com and been working like a charm. Hope this helps.
Logged
zorlac
Full Member
***
Posts: 213



« Reply #266 on: May 15, 2018, 08:24:12 pm »

But I'd still be able to flash the obi fw if I could just get the stupid file!
Perhaps I am reading too much into the words, but it seems to me that those that are paid by the companies involved (either directly, or indirectly) have made it pretty clear that if you want to use an OBi (especially with GV), you are going to have to learn to live within their ecosystem and the way they have chosen to move forward and deliver service.  If you do not like what Obihai and Google are doing (and some will not), you should probably start the planning of your move to one of the alternatives available to you.  A number of vendors (some actively participating on this board) have offered to help you move to their service(s).  The OBi devices (and/or the GV service) were never for everyone.
Then why not just take away the ability to upload a fw file directly to the device (the fw update ability is still available with the current fw)? If the manufacturer doesn't want provide access to the fw files having a user flash routine is rather pointless isn't it? Also, the device's fw is something that can affect normal sip services not just GV.

If you go back to the beginning of this topic you'll see that the fw was pretty readily available years ago not to mention quite a few active links to outdated fw.
If they provided a normal ftp site at least the fw revisions would be in some type of logical hierarchy.

On a more positive note, I was on the phone today for over two hours with two different people and the annoying delay that makes GV pretty frustrating at times has been GREATLY reduced, less than probably 1/2 what it used to be. So this update was certainly a BIG improvement for GV IMO!!

FWIW, these stats used to be a lot worse with this amount of data.


« Last Edit: May 15, 2018, 10:09:24 pm by zorlac » Logged
RFC3261
Full Member
***
Posts: 171


« Reply #267 on: May 16, 2018, 09:28:00 am »

Then why not ...
As you state, Obihai decided to end formal firmware distribution to customers not using their automated upgrades (or via partners who have a different contractual arrangement) quite a long time ago.  That some people that participate here have managed to "guess" the new firmware locations, and then share how to access them, is not a fully supported solution.  It just happened to work.  Times may change.  It is impossible to accurately predict the future.  Polycom (last I knew) offers free downloads of firmware, but charges substantially more upfront (which presumably helps pays for the future software development).  That is certainly one way to move forward.  Another is to keep the lower upfront cost and move to a more formal licensing model for future software updates.  The fact that Obihai decided in this case to release the firmware for the new (and improved?) GV integration for free via their automated processes is a really nice gift.  I would have fully expected to have to pay for that upgrade (I had been using the device for many years without paying a dime for that software development work).  In any case, their business, their choices, so all we can do is wait and see what happens.  If the current situation, or any changes, are not to ones liking, it will be time to move on to another solution that meets ones expectations.
Logged
ma678
Jr. Member
**
Posts: 22


« Reply #268 on: May 20, 2018, 09:54:08 am »

It seems GV took sometime to settle up. Now all accounts connect without any drops.

My three GV accounts show "Connecting to 64.9.240.172" every few minutes. May I change setting anywhere to keep alive interval longer?

Thanks.

NO.  Do NOT change the keep-alive interval.  Google Voice will specifically block connections if the endpoint is sending rapid keep-alives.  Leave it at the default.  In fact, the error you describe can be caused by changing the keep-alive settings.

If you can't get your device to connect and stay connected, then delete it off of the OBiTALK portal, restore it to factory defaults, re-add it to the portal, and re-configure Google Voice.  Do not make any "expert mode" changes to the Google Voice SPx settings.
Logged
NomadTech
Newbie
*
Posts: 4


« Reply #269 on: Today at 07:55:39 am »

Is there a working url for their ftp sever to download the latest revision of fw?
I wish they had a normal ftp site that I could peruse.  Embarrassed

This works:  http://fw.obihai.com/OBi202-3-2-1-5794EX.fw

But this doesn't:  http://fw.obihai.com/OBi202-3-2-2-5859EX.fw

Thanks

Try this https://www.obitalk.com/images/OBi202-3-2-2-5857EX-19283837473.fw and don't worry abou it saying 5857 as it is 5859.  I am using it on my second OBI202 that didn't update no matter what I did, while the first one did.
Logged
Pages: 1 ... 12 13 [14]
  Print  
 
Jump to:  

Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC