Can't make obi to obi calls anymore using **9 (got busy tone)
giqcass:
Quote from: tsaisfamily on November 15, 2013, 10:59:00 am
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.
Do you mean you can't manually downgrade anymore?
tsaisfamily:
Quote from: giqcass on November 17, 2013, 11:26:37 am
Quote from: tsaisfamily on November 15, 2013, 10:59:00 am
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.
Do you mean you can't manually downgrade anymore?
Right, this is what I got if trying to downgrade the firmware.
Firmware downgrading is prohibited
tsaisfamily:
One interesting observation. If I dial **9 xxx xxx xxx directly, I got fast busy right away. But if I use speed dial (9 # which is configured as **9 222 222 222), I would get one ring back tone, followed by a few seconds of silence, then fast busy tone again. But the call history did show that the call got connected....
Call 1 11/17/2013 17:42:25
Terminal ID PHONE1 LINE1
Peer Name
Peer Number 9 9
Direction Outbound Outbound
17:42:25 New Call
17:42:28 Call Connected
17:42:39 End Call
Call 2 11/17/2013 17:40:44
Terminal ID PHONE1 OBiTALK1
Peer Name
Peer Number **9ob222222222 ob222222222
Direction Outbound Outbound
17:40:44 New Call
azrobert:
I don't think you defined Speed Dial #9 properly.
Your call history should show "ob222222222" going out OBiTalk1, but yours is showing "9" going out Line1. When a Speed Dial is not defined the OBi will pass through the number you dialed and that is what looks like is happening with your Call 1. I'm guessing your Phone Port primary line is PSTN Line.
tsaisfamily:
Oops, you are right. It turns out that the speed dial on this unit has been wiped out when I messed with the configuration. No wonder I got different behavior now.
Navigation
[0] Message Index
[#] Next page
[*] Previous page