I upgraded the firmware on my 1032s on 04/17/2018 to the latest version. After that, the 1032s that were using OBiWIFI would not stay connected. One of them would be connected to the wireless router, but non functional. The other one would disconnect from the wifi altogether. The first one would go down after a couple of hours, the second would stay up about a day. I could reboot the devices and get them working again. I factory reset the first one and it now appears that that fixed the problem. It remained connected over night. The second one had disconnected from the router when I go up this morning. The OBIWIFI adapter was not even blinking like it usually does. I plan on factory resetting this 1032 when I get home to see if that will fix the problem with this one.
The 1032 using an Ethernet cable is not experiencing any issues.
Is anyone else seeing these problems with the latest firmware? I am not at home so I cannot tell you what version it is.
Another firmware upgrade is now available. Installing now to see if it fixes issues with wireless.
The 1032 connected with an Ethernet cable worked without any problems. The 2 using OBIWIFI crapped out. I don't know if it installed and the wifi is just down or what. I tried to do the upgrade remotely using OBiTalk portal. The OBiTalk portal is reporting both 1032s as being offline now and the yellow triangle is still showing.
When I got home, they were stuck in a downloading pattern with the line key orange. After a reboot, they were functional again. They got stuck again when I tried to update via the phone. I had to connect each phone to a wired Ethernet connection to perform the upgrade.
New firmware did not fix the problem. It is now worse. I just found one of the 1032s with the OBIWIFI adapter blue light solidly lit. It is not blinking buy constantly on. I rebooted the phone and the display says it is connected to the network, but it will not come back online and I cannot ping the phone. I guess another factory reset is in order. I guess I will wait a few weeks before going to the trouble to reimport the address book again.
The phone that went offline last night and then I factory reset was still online this morning when I got up. The one that I did not rest, was offline. The OBIBlutooth adapter had a solid blue light. I did a factory reset about 2 hours ago and set it back up. I just logged in to OBiTalk from work and OBiTalk is reporting that phone is offline again. I am not sure what to do to fix this one.
Quote from: Boykin on April 20, 2015, 04:08:41 PM
When I got home, they were stuck in a downloading pattern with the line key orange. After a reboot, they were functional again. They got stuck again when I tried to update via the phone. I had to connect each phone to a wired Ethernet connection to perform the upgrade.
My phone also got stuck in a downloading pattern several times, ethernet connection here.
I will test out WiFi tomorrow and will report back any issues encountered.
Both phones connected via wifi have gone down since I got home about 3 hours ago. I think what was going on was the phones connected with wifi kept rebooting until the wifi locked up. I have reverted from firmware version 5.0.0.2595.1311 to 5.0.0.2486. I am hoping the downgrade will fix the connectivity issues with wifi. I am leaving the phone with the wired connection on the 2595 version. It does not appear to be having any issues.
I have today connected an OBi1032 via PoE, OBiWiFI inserted into the top USB port on the real of the phone and it's currently successfully connected to my home WiFi network. I know you probably have yours powered via a main's adaptor, not sure if this will alter my results? If it appears mine works OK with this current setup then I guess I have to test again using a mains adaptor instead. (Damn things are so short though)
One other thing to take note here is that I configure my phone's locally. I do not use the portal, again not sure if this will alter the results of my testing.
Quote from: Boykin on April 20, 2015, 07:17:31 PMI guess I will wait a few weeks before going to the trouble to reimport the address book again.
Personally I hate the phonebook setup on the OBi1000, one of the worst I have ever encountered. I got fed up of the long winded setup I no longer bother to add any! One other pet hate of mine is that the OBi1032 does not match an inbound CLI to that saved in the phonebook. I kept answering my family and friends with my business greeting because the OBi1032 doesn't display the contact name. :-\
UPDATE: So far it's still up and running without issue for me, running 5.0.0 (Build: 2585.1311).
So far so good, no issues.
I just did a ***6 and there is a new firmware release. I pressed 1 to install the new firmware 5.0.0 (Build: 2595.1311) and everything went smoothly over WiFi.
One thing I noticed right off the bat is that my WiFi signal is stronger on this build than on the last. Was getting 3 Bars on 5.0.0 (Build: 2585.1311) but now get 4 with 5.0.0 (Build: 2595.1311).
Will leave WiFi connected and see if I get any issues with this build.
After reverting back to 5.0.0.2486 I have not had any wifi disconnects on those phones. They have been up for about 11.5 hours now. I appear to be back to normal. I wonder if 2595.1311 conflicts with my router or something?
Quote from: Boykin on April 22, 2015, 06:43:49 AMI wonder if 2595.1311 conflicts with my router or something?
Out of interest what router do you have? is it running the latest firmware?
I have an ASUS RT-AC87U. It has the latest firmware.
Interesting, I'm using an ASUS RT-AC68U. Although I am using Merlin's Firmware on my router: http://asuswrt.lostrealm.ca
My phone has been connected rock solid all day. ???
This is the direct link to the merlin build firmware for your router: http://www.mediafire.com/download/iaj0khhbw558jqx/RT-AC87U_378.52_2.zip
It's exactly the same version as mine, give it a try. The web interface is the same as the stock ASUS firmware and if you decide to go back to stock firmware at anytime just download the latest firmware for your router from the ASUS website and update your firmware as normal.
Merlin's Firmware is awesome!
Hello, "One other pet hate of mine is that the OBi1032 does not match an inbound CLI to that saved in the phonebook."
I am extremely concerned about this. I have just bought the 1032 and to display the name of a contact based on the received Caller ID is one of the most basic of funtions of any telephone whether it be mobile or static.
I do hope the above problem will be sorted out soon otherwise as far as I am concerned this product is not fit for purpose!! :'(
I will give Merlin a try when I get home. I will upgrade one of the wifi phones back to the latest firmware and see how it goes.
Quote from: WelshPaul on April 22, 2015, 06:05:11 AM
So far so good, no issues.
I just did a ***6 and there is a new firmware release. I pressed 1 to install the new firmware 5.0.0 (Build: 2595.1311) and everything went smoothly over WiFi.
One thing I noticed right off the bat is that my WiFi signal is stronger on this build than on the last. Was getting 3 Bars on 5.0.0 (Build: 2585.1311) but now get 4 with 5.0.0 (Build: 2595.1311).
Will leave WiFi connected and see if I get any issues with this build.
Is there any network connectivity over the Ethernet cable along with power or just power. I have one 1032 on 2959.1311 that is using wired Ethernet and power adapter. It is having no problems.
I am an OBiPlus premium subscriber so I can factory reset, delete from OBiTalk, add back to OBiTalk and then regen the OBiPlus scripts and my phones are reprogrammed for the most part. I have to manually setup a program key to dial voicemail and change the label on SP1.
I just wish there was a way to backup your contacts so I did not have to unplug my OBiBT and take it to each phone to download and then set the default number on each contact.
Quote from: jedilady on April 22, 2015, 11:50:01 AM
Hello, "One other pet hate of mine is that the OBi1032 does not match an inbound CLI to that saved in the phonebook."
I am extremely concerned about this. I have just bought the 1032 and to display the name of a contact based on the received Caller ID is one of the most basic of funtions of any telephone whether it be mobile or static.
I do hope the above problem will be sorted out soon otherwise as far as I am concerned this product is not fit for purpose!! :'(
I have mentioned this many times in the past, it's on the to do list apparently. I will drop an email off and see if I can get an update on this.
Quote from: Boykin on April 22, 2015, 12:00:15 PM
Is there any network connectivity over the Ethernet cable along with power or just power. I have one 1032 on 2959.1311 that is using wired Ethernet and power adapter. It is having no problems.
I will connect tomorrow via mains adaptor to rule out the PoE making any difference. (actually I will do it now, that way if it's still connected in the morning I know it works)
Quote from: Boykin on April 22, 2015, 12:05:11 PM
I am an OBiPlus premium subscriber so I can factory reset, delete from OBiTalk, add back to OBiTalk and then regen the OBiPlus scripts and my phones are reprogrammed for the most part. I have to manually setup a program key to dial voicemail and change the label on SP1.
I just wish there was a way to backup your contacts so I did not have to unplug my OBiBT and take it to each phone to download and then set the default number on each contact.
I hear you, I mentioned months ago about adding a CSV upload feature to the GUI's Device Update as a bare minimum. I was told it was in the works. I would like to add and remove contacts via the phones GUI too like every other phone I own but I don't think that's going to happen.
Thanks for that WelshPaul. Not only in the spec does it say CallerID name and number. It also says Photo.!!!
I too updated yesterday and have a bricked OBI1032 phone now. I have tried factory reset and connected a direct ethernet cable in lieu of the WiFi adapter but can't get it back to working.
Does anyone from Obihai ever look at this forum? How can I reach them for support?
Thanks!
Quote from: TrekCom on April 22, 2015, 02:06:27 PM
I too updated yesterday and have a bricked OBI1032 phone now. I have tried factory reset and connected a direct ethernet cable in lieu of the WiFi adapter but can't get it back to working.
Does anyone from Obihai ever look at this forum? How can I reach them for support?
Thanks!
Did you update the firmware over WiFi? If you did you may be SOL. Never update any firmware over WiFi as the chance of it failing increase and as a result the chances of a device being bricked high. Almost all manufacturers (I don't know of any) refuse any warranty claims for this type of failure.
I have had issues upgrading my OBi1032's firmware in the past and always proceed to update over Ethernet. Is your phone under warranty? Where did you purchase it? If you get no luck with Obihai you could try going back to the retailer.
Get support from OBIHAI here: http://www.obihai.com/request-support
Quote from: TrekCom on April 22, 2015, 02:06:27 PM
I too updated yesterday and have a bricked OBI1032 phone now. I have tried factory reset and connected a direct ethernet cable in lieu of the WiFi adapter but can't get it back to working.
Does anyone from Obihai ever look at this forum? How can I reach them for support?
Thanks!
This is what I did. You can try it at your own risk.
Connect the 1032 to a wired internet connection and go under settings to see what the ip address is. Using a browser enter the IP address and see if you can log into the local web server on the phone. If you can get to the local web server on the phone, you might be able to manually revert back to the March update. Go to the OBiTalk page and click on documents on the bottom left side under support. Click on OBI Device Firmware and download the March firmware update. Then manually downgrade the phone to the March update using the local web server.
This is what I did and so far I am not having any problems.
Thanks for you help. I followed the next gentlemen's suggestion and downgraded the firmware to the March 15 version But still can't get WiFi to work. It says WiFi not available in the display under settings.
All of my lines show yellow and don't work. Maybe I need to try to delete and re install the phone in ObiTalk. I did put in a support request as the phone is only 5 months old. Bought from Amazon.
Quote from: WelshPaul on April 22, 2015, 02:16:50 PM
Quote from: TrekCom on April 22, 2015, 02:06:27 PM
I too updated yesterday and have a bricked OBI1032 phone now. I have tried factory reset and connected a direct ethernet cable in lieu of the WiFi adapter but can't get it back to working.
Does anyone from Obihai ever look at this forum? How can I reach them for support?
Thanks!
Did you update the firmware over WiFi? If you did you may be SOL. Never update any firmware over WiFi as the chance of it failing increase and as a result the chances of a device being bricked high. Almost all manufacturers (I don't know of any) refuse any warranty claims for this type of failure.
I have had issues upgrading my OBi1032's firmware in the past and always proceed to update over Ethernet. Is your phone under warranty? Where did you purchase it? If you get no luck with Obihai you could try going back to the retailer.
Get support from OBIHAI here: http://www.obihai.com/request-support
My phone just rebooted on its own! I am unable the access the web based GUI although I can make an outgoing phone call still. Looks like there may be an issue with WiFi after all. Will see how it manages through the night! Will run a syslog in the morning.
Quote from: TrekCom on April 22, 2015, 03:06:00 PM
Thanks for you help. I followed the next gentlemen's suggestion and downgraded the firmware to the March 15 version But still can't get WiFi to work. It says WiFi not available in the display under settings.
All of my lines show yellow and don't work. Maybe I need to try to delete and re install the phone in ObiTalk. I did put in a support request as the phone is only 5 months old. Bought from Amazon.
Quote from: WelshPaul on April 22, 2015, 02:16:50 PM
Quote from: TrekCom on April 22, 2015, 02:06:27 PM
I too updated yesterday and have a bricked OBI1032 phone now. I have tried factory reset and connected a direct ethernet cable in lieu of the WiFi adapter but can't get it back to working.
Does anyone from Obihai ever look at this forum? How can I reach them for support?
Thanks!
Did you update the firmware over WiFi? If you did you may be SOL. Never update any firmware over WiFi as the chance of it failing increase and as a result the chances of a device being bricked high. Almost all manufacturers (I don't know of any) refuse any warranty claims for this type of failure.
I have had issues upgrading my OBi1032's firmware in the past and always proceed to update over Ethernet. Is your phone under warranty? Where did you purchase it? If you get no luck with Obihai you could try going back to the retailer.
Get support from OBIHAI here: http://www.obihai.com/request-support
One last thing you might try is unplug the power on the phone, unplug the wifi adapter, plug the wifi adapter back in and plug the phone power back in. If it does not connect, reset up the wifi settings by enabling wifi setup mode and following the OBIWIFI setup instructions. I used to have to do this every time there was a power failure.
At this point it seems the WiFi Dongle went bad coincidentally as the firmware was updated.......
I replaced it with another from one of my other phones and it works. I'm still trying to get the phone reconfigured since I reset to factory while trying to figure out what was wrong.
Well there is an issue with WiFi, seems like mine crashes and reboots around the two hour mark and although it reconnects to WiFi and I can make and receive calls.
Will report this in the Beta Testers forum.
Spent nearly three hours sys logging the phone and it finally failed. This time though no reboot, all lines including obitalk are red and I am unable to make or receive calls. I can not access the web based GUI either...
Weird thing is the syslog server crashed just after the phone? Did the phone cause the crash?
Only way to get phone to work was to power down the device and restore power.
I took a screenshot of the syslog before I lost the report.
After downgrading my firmware, I have not had any issues. I am not going to upgrade the firmware back to the latest version since you are having connectivity issues too.
Quote from: Boykin on April 22, 2015, 06:43:49 AM
After reverting back to 5.0.0.2486 I have not had any wifi disconnects on those phones. They have been up for about 11.5 hours now. I appear to be back to normal. I wonder if 2595.1311 conflicts with my router or something?
I'm also having problems after upgrading to 5.0.0 (Build 2595.1311). How can I revert back to the previous version of firmware? I can't seem to find the previous version anywhere. Any help is appreciated.
http://fw.obihai.com/OBiPhone-latest.fw
This is the March 15 firmware.
Since upgrading to the latest firmware 5.0.0 (Build: 2959.1311) my obi1032 (using wifi) keeps freezing up and rebooting. Can anyone advise where I can find the previous version of Firmware? Thanks for your help.
seemeobi
Quote from: TrekCom on April 25, 2015, 09:16:41 AM
http://fw.obihai.com/OBiPhone-latest.fw
This is the March 15 firmware.
Quote from: TrekCom on April 25, 2015, 09:16:41 AM
http://fw.obihai.com/OBiPhone-latest.fw
This is the March 15 firmware.
Thanks TrekCom... sorry I posted twice. Couldn't find my first post and wasn't sure it went so I posted again. Thanks for your help. Hopefully this will solve the issue for now.
Quote from: seemeobi on April 25, 2015, 10:56:13 AM
Quote from: TrekCom on April 25, 2015, 09:16:41 AM
http://fw.obihai.com/OBiPhone-latest.fw
This is the March 15 firmware.
Thanks TrekCom... sorry I posted twice. Couldn't find my first post and wasn't sure it went so I posted again. Thanks for your help. Hopefully this will solve the issue for now.
Let us know if it fixes your problem.
This has apparently now been fixed. New firmware has been released and although I have installed it I have not actually tested the WiFi myself just yet.
***6 to update people from 28/4.
I will update and see what happens.
New firmware version: 5.0.0 (Build: 2619.1311)
I updated to 5.0.0 (Build 2619.1311) this morning and so far so good. I haven't had any issues yet.
After having no connectivity issues for 24 hours, I was ready to update my last 1032. I wanted to set up programmable keys to work with parking a call first though. I made a call with my cell to my 1032s, and when I answer on the phones that had been upgraded, I could hear nothing on the 1032 and only hear static on the cell. If I answer the call on the phone that was not upgraded, the call was fine. To confirm that the firmware was the problem, I upgraded the last phone and now it does the same as the other 2. Silence on the 1032 and static on the cell. This is happening on wired and wireless internet connected 1032s. I will revert back to the March firmware since now I cannot get incoming calls.
Reverted back to 2486 and now incoming calls are working again.
If your 1032 firmware is current, you better call it from your cell to see if you can hear the caller and see if the caller gets static.
Not getting this issue on my OBi1032. Mine has been running the latest version since I last posted and I just called it from my cell phone without issue.
However... I reported the very same behaviour back in February, only difference then was it only happened when bridging a call. No audio in either direction and static on my cell phone.
QuoteI just attempted to set a divert for a pesky number that keeps ringing. I setup the following rule against sp1:
InboundCallRoute: {(12345):sp1(54321)},{ph}
If I get a call from caller ID 12345 it should divert it over sp1 to telephone number 54321 and although it does do that there is no audio?
I cannot hear anything either side of the call. Both phones are silent?
I tested it on my mobile, Call my obi1032 from my home phone > obi1032 using the above rule forwards the call to mobile without ringing on the Obi1032 > Mobile phone rings and I answer it and no audio on mobile or house phone.
I do believe this was fixed, looks like it may now be happening on inbound calls on the latest version when using a certain codec?
EDIT: The thread is located in the beta forum: http://www.obitalk.com/forum/index.php?topic=9393.0
EDIT 2: I just tested this again and OBIHAI still have not fixed the issue, while the OBi1032 does indeed forward the call the result is that once answered there is no audio in either direction only some minor white noise. I'm sure they are both related.
Syslog results are identical to those I posted back in Febuary
<7> RTP:DtmfTxMtd:1(1),0
192.168.1.5 30/04 09:23:37.509
<7> RTP:Start->c0a8010a:13456(1 0);0;(nil);(nil):0:0;0(59)
192.168.1.5 30/04 09:23:37.510
<6> +++ rtp_alloc_encoder: rtp 0xafddd060 tx_ptime_ts set to 160
192.168.1.5 30/04 09:23:37.510
<7> RTP:DtmfTxMtd:1(1),0
192.168.1.5 30/04 09:23:41.520
<7> RTP:Start->c0a8010a:13456(1 0);0;(nil);(nil):0:0;0(59)
192.168.1.5 30/04 09:23:41.522
<6> +++ rtp_alloc_encoder: rtp 0xafddd060 tx_ptime_ts set to 160
192.168.1.5 30/04 09:23:41.522
<7> RTP:Start->c0a8010a:10384(80 0);0;(nil);(nil):0:0;0(55)
192.168.1.5 30/04 09:23:41.530
<6> +++ rtp_alloc_encoder: rtp 0xafd63378 tx_ptime_ts set to 160
192.168.1.5 30/04 09:23:41.530
<3> RTP_process_audio_frame_ex 4066: Huhh??? 0 vs 80.
192.168.1.5 30/04 09:23:41.531
<3> RTP_process_audio_frame_ex 4066: Huhh??? 0 vs 80.
192.168.1.5 30/04 09:23:41.532
<3> RTP_process_audio_frame_ex 4066: Huhh??? 0 vs 80.
192.168.1.5 30/04 09:23:41.533
<3> RTP_process_audio_frame_ex 4066: Huhh??? 0 vs 80.
192.168.1.5 30/04 09:23:41.533
<7> RTCP:RxPkt[44]=201<--c0a8010a:10385
192.168.1.5 30/04 09:23:46.700
<7> RTCP:RxPkt[44]=201<--c0a8010a:10385
192.168.1.5 30/04 09:23:51.540
<7> RTCP:RxPkt[44]=201<--c0a8010a:10385
192.168.1.5 30/04 09:23:56.539
<7> RTP:Del Channel
192.168.1.5 30/04 09:23:57.961
<7> CCTL:DelChisItem
192.168.1.5 30/04 09:23:57.974
<7> CCTL:AddChisItem
192.168.1.5 30/04 09:23:57.975
<7> RTP:Del Channel
192.168.1.5 30/04 09:23:57.975
I am using OBiPlus Premium with all of my SPs on the OBi202. I wonder if I set up one of my lines on a 1032 directly if I would still have the same problem. I will have to experiment tonight when I get home.
I had to turn off the auto attendant in OBiPlus due to a similar issue. The auto attendant had 2 options, 1 to leave a voice mail and 2 to continue. When the caller pressed 2, I could hear everything they were saying but they could not hear me. I confirmed this with my cell.
I found something that might have caused an issue. In OBiPlus I was using codec B, but the SP was using codec A in the 202. I changed OBiPlus to codec profile A. I will test this when I get home.
QuoteI found something that might have caused an issue. In OBiPlus I was using codec B, but the SP was using codec A in the 202. I changed OBiPlus to codec profile A. I will test this when I get home.
I believe that there is a bug with the way OBi devices negotiate codecs when setting up a bridged call. In your case I don't think it's a problem with which codec profiles are used, it's a problem with which codecs are actually enabled and their priority within the profiles. I managed to get around the bug by only enabling codec G711U in both devices. You may wish to try this as a test.
My setup does not include OBiPLUS, so I cannot comment on how that might affect codec negotiation when bridging calls. However, my problem did include an OBi1032 and an OBi110 and a bridged call between them.
Quote from: ianobi on April 30, 2015, 07:37:14 AM
QuoteI found something that might have caused an issue. In OBiPlus I was using codec B, but the SP was using codec A in the 202. I changed OBiPlus to codec profile A. I will test this when I get home.
I believe that there is a bug with the way OBi devices negotiate codecs when setting up a bridged call. In your case I don't think it's a problem with which codec profiles are used, it's a problem with which codecs are actually enabled and their priority within the profiles. I managed to get around the bug by only enabling codec G711U in both devices. You may wish to try this as a test.
My setup does not include OBiPLUS, so I cannot comment on how that might affect codec negotiation when bridging calls. However, my problem did include an OBi1032 and an OBi110 and a bridged call between them.
You are correct. I turned off all codecs except G711U and now the latest firmware works. I can hear the caller and they can hear me.
When I bypassed the 202 and put a GV line on 1032, it works correctly too.
Even using only G711U, the auto attendant still does not work correctly. I can hear caller, but they still cannot hear me.
Quote from: Boykin on April 30, 2015, 11:43:06 AM
the auto attendant still does not work correctly.
I reported the auto attendant issues a while back also. They should be working on a fix.
The offending codec is G726R32. I enabled the ones I had disabled one by one until I reproduced the problem. I had to disable this codec on the 1032s. The 202 has this codec and all the other default codecs enabled. I tried to disable this codec on the 202 and leave it enabled on the 1032s but that did not fix the problem.