Firmware update for 20x series
zorlac:
Quote from: SteveInWA on May 14, 2018, 12:04:54 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. ???
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!!!
SteveInWA:
Quote from: zorlac on May 14, 2018, 06:33:08 pm
Quote from: SteveInWA on May 14, 2018, 12:04:54 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.
zorlac:
Quote from: SteveInWA on May 14, 2018, 06:39:10 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. ::)
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))
chilirock:
Quote from: chilirock on May 13, 2018, 01:29:15 pm
Quote from: SteveInWA on May 12, 2018, 10:03:18 pm
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?
RFC3261:
Quote from: zorlac on May 14, 2018, 07:02:25 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.
Navigation
[0] Message Index
[#] Next page
[*] Previous page