Can't make obi to obi calls anymore using **9 (got busy tone)
drgeoff:
Have a look at the Call History. This is what mine showed for a successful call to the echo test number.
Terminal ID PHONE1 OBiTALK1
Peer Name
Peer Number **9ob222222222 ob222222222
Direction Outbound Outbound
19:45:52 New Call
19:45:54 Call Connected
19:46:25 End Call
Are your two Peer Numbers the same as above and is the second Terminal ID 'OBiTALK1'?
azrobert:
I have the exact same problem.
This has happened to me before and deleting the OBi from the dashboard, factory reset and re-adding the device to the dashboard fixed the problem.
This time it's not working.
Up to now OBiHai support has been zero help.
Are you having any better luck?
tsaisfamily:
Terminal ID PHONE1 OBiTALK1
Peer Name
Peer Number **9ob222222222 ob222222222
Direction Outbound Outbound
23:03:24 New Call
This is my call history and I don't see "Call Connected" because I got fast busy tone.
tsaisfamily:
No luck at all so far, I have tried all kind of things possible to try to fix it. I deleted my device from the web portal, hard reset the unit, and try to make **9 222222222, just got busy tone. I plan to downgrade my firmware from 2824 to something else older like 2774 but they don't allow you to do it any more.
The support guy is not helping either so far. I asked them is there a way to at least force upgrade the firmware again even it's the same version but no response.
drgeoff:
I don't know the details of OBiTalk connections but I don't see how it can work without an OBi server (or servers) being involved at least at the initial stage of placing a call. I'm beginning to think there is nothing amiss with your OBi unit and the problem is with the OBi server. A corrupted entry for your unit in OBi's database?
Navigation
[0] Message Index
[#] Next page
[*] Previous page