Guys,
The following is the call progress on a 1.4.5 system, it shows the handset as state 16 (busy) but it is not. A restart of the service removes the issue.
dialparties.agi: priority is 1
dialparties.agi: Caller ID name is ‘08703501284’ number is '08703501284’
dialparties.agi: Methodology of ring is ‘none’
– dialparties.agi: Added extension 5141 to extension map
– dialparties.agi: Extension 5141 cf is disabled
– dialparties.agi: Extension 5141 do not disturb is disabled
dialparties.agi: Extension 5141 has ExtensionState: 16
– dialparties.agi: Checking CW and CFB status for extension 5141
dialparties.agi: Extension 5141 is not available to be called
dialparties.agi: Extension 5141 has call waiting disabled
Any ideas as to what might be causing this? The problem goes away after a restart for approx 4 days. The handset is a GXP2000.
Thanks.
Andy
For info.
The problem occurs after a call is transferred or a feature code is used.
Any ideas?
Im asuming this is a freepbx install going by the agi.
The problem is the Extensionstate thats being reported AFAIK 16 isnt valid
Im sure your not the only one with the problem have a google for Extensionstate: 16 as the valid option only go upto 8
or raise is with the freepbx guys
Ian
Yes, this is AGI based.
I have raised this issue in multiple places. It does look like the call is not getting hungup for it to show busy after a tranfer though.
Andy,
I had the exact same issue in a call center. After upgrading to Asteirsk 1.4.X (4-5). It’s certainly a new bug that new to be posted on the bugs tracker.
I have updated the box to 1.4.6 of * and the problem seems to have gone, however, when a call is transferred to an extension for the first time, the second time a transfer is attempted the handset reports busy.
Any ideas?
The status 16 in HOLD and not BUSY.
I think this is the same bug i reported here:
bugs.digium.com/view.php?id=10165
But nobody has replied this bug report and i think this is a serious bug ;(
The status 16 in HOLD and not BUSY.
I think this is the same bug i reported here:
bugs.digium.com/view.php?id=10165
But nobody has replied this bug report and i think this is a serious bug ;(