Avaya IPO500 Busy Tone Detection

[Obinzzz]

Hi guys,

I have trouble with Avaya IPO500 Busy Tone detection program.

We have an issue with one of our client's system that upon auto attendant, when the caller drops the call, the call is still connected (based on system status) which causes GHOST CALL in the fallback extension. Avaya doesn't disconnects the call even busy tone is sent to the system.

By using Audacity software, i have gathered the frequency and on/off interval. The said data gathered is not working in busy tone detection.

To further isolate the problem, I have brought another unit. I have connected and used the analogue trunk line of our client and test busy tone detection and it works normally! Calls are disconnected when the caller drops the call during auto attendant greeting.

Based on testing and isolation done, I have concluded that our client's Avaya IPO500 has problem. Do you think the version of the system has effects? Client's PBX is 9.1.336.1 while the unit i brought is 9.0.0.829. Busy tone detection works normally in 9.0 version. Can you give me some advice for the said scenario?

 

[intrigrant]

Best thing to get is a disconnect clear signal from the analog trunk.
Then regarding your question, it depends on the settings in the system.
Although both systems are IP Office there can be significant differences in hardware.
So note all the hardware details of both systems (PCS levels, card numbers etc.) and compare them.
Use monitor on both systems and select all of the ATM filter and compare the logs.
Did you change the busy tone settings to the right values?
Is the AA on Embedded VM or VM Pro?

 

[Obinzzz]

@intrigant

auto attendant used is embedded only.

Yes I have changed the busy tone to right value I think. I used audacity to gather frequency and ON/OFF time. I used those values on both system. Busy tone detection is not working in our client's pbx (v9.1.336.1) while on my testing unit (v9.0.0.829)it works fine. Note that I have used the same trunk line on both units for isolation.

I tried the Disconnect signal but I have no proper data to input.

 

[amriddle01]

So upgrade them, if it isn't fixed tell Avaya. It can only be a bug if you have checked with another firmware, assuming you have used the exact same cards in your testing as Intrigrant eluded to, if one is a combo and one a v2 combo it's not a valid test...swap the cards