December 16, 2017, 08:44:07 am *
Welcome, Guest. Please login or register.
News:
 
   Forum Home   Search Login Register OBiTALK  
Pages: [1] 2 3 ... 5
  Print  
Author Topic: 3.0.1 (4303) Can No Longer Receive Calls  (Read 104052 times)
IrwinFamily
Newbie
*
Posts: 9


« on: February 27, 2014, 11:54:35 pm »

I just updated my OBi 202 to the latest 4303 firmware and now I can not receive calls.
Everything looks fin on the ObiTalk portal. SP1 and SP2 are both registered with different extensions on CallCentric. The CallCentric Dashboard shows all extensions registered. I can place calls At first I would get either a busy signal or ring when calling my numbers from other phones. Now they direct straight to Voice Mail. CallCentric shows all the calls received, even before they were directing to VM. It's like something in the device changed where CallCentric can no longer ring or deliver to the device. My OBi 110 is also registered with a CallCentric extension, and it still works fine.
I saw previous posts with Static/DHCP troubles after upgrading, so I changed from Static to DHCP. The IP address of the device changed, but still could not receive calls. I switched back to my static address. That part works fine, but still no receive. I use this for work obviously, and am scheduled to be on the phones in the morning. HELP!
Logged
QBZappy
Hero Member & Beta Tester
*****
Posts: 2322



« Reply #1 on: February 28, 2014, 05:25:39 am »

@IrwinFamily

Not a solution, but until you figure this out you might need to use a softphone on your computer registered directly to your voip service provider. At least you can keep working.
Logged

Owner of the 1st OBi110/100 units in service in Canada & South America. 1st OBi202 on my street. 1st OBi1032 in Montreal.
DrJay
Jr. Member
**
Posts: 43


« Reply #2 on: March 01, 2014, 12:00:06 pm »

I had the same problem after the update today. Here's how I fixed it:

1. Deleted CallCentric from SP1 on ObiTalk.com
2. Added CallCentric account back to SP1 on ObiTalk.com
3. Cycled power on the ObiHAI 202.

Not sure if steps 1 & 2 alone, step 3 alone or a combination of all three steps did the trick but everything is back to normal.

1. Calls to my Google Voice number still forward to the OBiHAI via my CallCentric account's native number
2. Outbound calls on SP1 go through CallCentric with the outbound CID spoofed as my GV number.
3. Calls to my CallCentric number - which no one knows but me. Well and GoogleVoice  Wink - ring the phones connected to the OBiHAI.
Logged
carl
Sr. Member
****
Posts: 457


« Reply #3 on: March 01, 2014, 03:43:55 pm »

will not work for me.
Logged
Mango
Sr. Member
****
Posts: 498


« Reply #4 on: March 01, 2014, 07:01:17 pm »

RonR at DSLR suggests: Voice Services -> SPx Service -> X_EnforceRequestUserID : (unchecked)

Anyone who is having the problem, please test and report if this solves it.
Logged

gderf
Sr. Member
****
Posts: 490



« Reply #5 on: March 01, 2014, 07:22:50 pm »

Anyone who is having the problem, please test and report if this solves it.

I can confirm that the suggestion fixes the problem.
Logged

Help me OBiHai PhoneOBi. You’re my only hope.
DrJay
Jr. Member
**
Posts: 43


« Reply #6 on: March 01, 2014, 09:02:19 pm »

OBiHAI Support confirms this: http://www.obitalk.com/forum/index.php?topic=7367.msg47103#msg47103
Logged
IrwinFamily
Newbie
*
Posts: 9


« Reply #7 on: March 01, 2014, 09:06:10 pm »

RonR at DSLR suggests: Voice Services -> SPx Service -> X_EnforceRequestUserID : (unchecked)

Anyone who is having the problem, please test and report if this solves it.

That did not work for me. I disconnected the 202 from the network, reset to default with a paperclip, removed the device from Obitalk and started fresh. After reconfiguring everything, I performed the suggested fix and still cannot receive calls. I purchased an OBI100 locally to get me through and it is working perfectly.
I like to idea of blocking the SIP Bots, but only if it WORKS. This has effectively bricked my 202. Amy other suggestions?
Logged
gderf
Sr. Member
****
Posts: 490



« Reply #8 on: March 02, 2014, 08:17:30 am »

@IrwinFamily

Have you tried downgrading to the previous firmware 3-0-1-4269?

That solved my problem.
Logged

Help me OBiHai PhoneOBi. You’re my only hope.
carl
Sr. Member
****
Posts: 457


« Reply #9 on: March 02, 2014, 09:06:06 am »

RonR at DSLR suggests: Voice Services -> SPx Service -> X_EnforceRequestUserID : (unchecked)

Anyone who is having the problem, please test and report if this solves it.

That did not work for me. I disconnected the 202 from the network, reset to default with a paperclip, removed the device from Obitalk and started fresh. After reconfiguring everything, I performed the suggested fix and still cannot receive calls. I purchased an OBI100 locally to get me through and it is working perfectly.
I like to idea of blocking the SIP Bots, but only if it WORKS. This has effectively bricked my 202. Amy other suggestions?

Having the same problem. Obihai is not supportive on this.  The solution they suggest will not work. Closing the thread does not help either.
Logged
Mango
Sr. Member
****
Posts: 498


« Reply #10 on: March 02, 2014, 09:09:39 am »

They locked the other thread because it was a duplicate of this one.  We can still post here.

Give downgrading a try and let us know how it works.

http://www.obihai.com/firmware/OBi202-3-0-1-4269.fw
Logged

carl
Sr. Member
****
Posts: 457


« Reply #11 on: March 02, 2014, 11:03:31 am »

As reported elsewhere, the upgrade apparently messed up everything on the device, Obihai made changes in inbound call routing parameters so now i DO have incoming calls but for outbound calls the SIP providers are still dead.  The firmware downgrade was not able to change that. Sad
Logged
DrJay
Jr. Member
**
Posts: 43


« Reply #12 on: March 02, 2014, 12:39:01 pm »

They locked the other thread because it was a duplicate of this one.  We can still post here.

Give downgrading a try and let us know how it works.

http://www.obihai.com/firmware/OBi202-3-0-1-4269.fw

I downgraded to .4269. All is well again.

Now if I can just ignore the yellow triangle "Firmware Update" indicator on the OBiTALK dashboard...  Cool
Logged
chicobiker
Newbie
*
Posts: 16


« Reply #13 on: March 02, 2014, 02:42:57 pm »

(4318) update is out reverting the previous update.
« Last Edit: March 02, 2014, 02:44:42 pm by chicobiker » Logged
carl
Sr. Member
****
Posts: 457


« Reply #14 on: March 02, 2014, 03:00:46 pm »

(4318) update is out reverting the previous update.
Too late for me. My outbound calling is permanently dead.
Logged
gderf
Sr. Member
****
Posts: 490



« Reply #15 on: March 02, 2014, 03:14:53 pm »

I doubt it is permanently dead. Try deleting your OBi from OBiTALK. Then reset it to the factory defaults. Then downgrade the firmware. Then reconfigure it from scratch.
Logged

Help me OBiHai PhoneOBi. You’re my only hope.
MikeHObi
Sr. Member
****
Posts: 326



« Reply #16 on: March 02, 2014, 03:29:55 pm »

upgraded my 202.  Working fine for incoming and outgoing.  Is currently using GV for both the incoming and outgoing due to the GV issues with fowarding through providers like Anveo and Callcentric.
Logged

Obi202 user & Obi100 using Anveo and Callcentric.
gderf
Sr. Member
****
Posts: 490



« Reply #17 on: March 02, 2014, 03:30:14 pm »

(4318) update is out reverting the previous update.

There is more to this than reverting to the previous configuration of X_EnforceRequestUserID.

I was able to get my OBi working again by reverting from 3.0.1 (4303) back to 3.0.1 (4269).

But when I upgrade to the latest 3.0.1 (4318) my OBi is broken once again.

The only thing I did to fix it again was to downgrade back to 3.0.1 (4269).

Are the OBihai folks reading this post? If so please explain this to us!
Logged

Help me OBiHai PhoneOBi. You’re my only hope.
gderf
Sr. Member
****
Posts: 490



« Reply #18 on: March 02, 2014, 03:31:19 pm »

upgraded my 202.  Working fine for incoming and outgoing.  Is currently using GV for both the incoming and outgoing due to the GV issues with fowarding through providers like Anveo and Callcentric.

There was never a firmware problem with GV for outgoing or incoming.
Logged

Help me OBiHai PhoneOBi. You’re my only hope.
Ostracus
Hero Member
*****
Posts: 581


« Reply #19 on: March 02, 2014, 03:47:54 pm »

Works fine on this end, although the bulk of calls goes through the Obi110.
Logged
Pages: [1] 2 3 ... 5
  Print  
 
Jump to:  

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