External Transfer over ATM problem

[ids12345]

Hi there,

I have a problem with my IP Office 406v2 system, with an analogue ATM 4 card installed. The system works fine, but when I transfer an incoming call to an external number, the transfer works OK but both the incoming and outgoing lines are never released. I have to reboot the system to free the lines again. Any ideas why!??

 

[intrigrant]

The solution depends on the location you are.
If you are in the US then either the "Disconnect clear" option is unselected or the lines don't give a proper disconnect clear signal.
For the civilised world ( hehe ) you must adjust the busy signal settings in the system > telephony tab accoring to the busy tones you receive on your alog trunks.

If these values are unknown then try to make a recording of the busy tone and use a program like CoolEdit Pro ( now called Adobe Audition ) were you can analyze the signal.
With this you can determine wich tones are used and the on/off time of the signal.
If you have bad luck then the two lines will both give a busy signal, if these signals are not synchronous then the busy tone detection will fail even if the settings are ok.
You can see if the busy tone detection has been activated but failed in sysmon, trace the ATM and look for the message like "Sloppy busy tone detected".
There is a work around for this : create a special feature code for transferring calls to a external line and set a timeout on it for lets say 10 minutes by adding a "t10" after the telephonenumber.

 

[ids12345]

Hi there, thanks for the reply. I recorded the busy tone, it's a continuous 400Hz signal. So, I set the busy tone properties accordingly. However, the incoming and outgoing lines still aren't released! It looks like IP Office is recognising the busy tone, it just doesn't drop the lines.

If I look at a sysmon trace, I see something like this when the incoming line is dropped:

701424mS PRN: AtmChannel1: Sloppy timeout (was 250 ms)
701534mS PRN: AtmChannel1: Sloppy timeout (was 110 ms)
707106mS PRN: AtmChannel1: Busy Tone Message Rx'd:
707106mS PRN: 0x2000
707106mS PRN:
707106mS PRN: AtmChannel4: Busy Tone Message Rx'd:
707106mS PRN: 0x2003
707106mS PRN:
713106mS PRN: AtmChannel1: Sloppy timeout (was 6000 ms)
713106mS PRN: AtmChannel4: Sloppy timeout (was 6000 ms)

I'm not sure what the sloppy timeout messages are - is that something to do with the disconnect clear signal? It looks like the busy tone is seen on both lines at the same time - could this be a problem?

If I physically disconnect the line from the exchange, the lines are then freed. Could this be a bug? I'm running v3.1(56)

 

[intrigrant]

Sloppy timeout means the ipo has recognized the busy tone but it did not match the settings for busy tone detection for at least six seconds.

 

[IPGuru]

Where exactly in the wold are you IDS

Disconnect clear is the prefered option if at all posible, this IS available in the UK as well as in the US but you would probably have to request BT to enable it. For the rest of Europe you would have to check with your telco.

You also need to tick the relavant box in the Analog trunk to tel your IPO to expect it.