Calls abandonded at AA causing "phantom" calls 1

[wheelma2]

We have an office that is experiencing an abundance of "phantom" calls to their Merlin Messaging system's Auto Attendant 0/Timeout rollover path.

We've isolated this to calls which have been abandoned at the AA. Apparently the system is not processing the disconnect signal from the remote end, therefore the timeout occurs and a dead air call is placed to the timeout path.

It doesn't seem to matter which CO line the call is on, so I connected an analog phone to one of the CO's and I'm pretty sure the disconnect signal is present... although I'm not necessarily sure what to expect. I hear a sort of "click" on the near end when I terminate the call on the remote end (my mobile). Is this enough of a signal, or should I be expecting something more from the CO?

Is there anything in the Magix or Messaging config I could be missing?

We have an identical (as far as I can tell) setup in a couple of other offices that do NOT have this issue.

Any suggestions?

 

[tekguy125]

belcan,

There is a reliable disconnect feature in the Merlin system that can be enabled, if you haven't done this you should. Assuming the telephone company is sending a disconnect signal this should help.

Press Menu, System Program, Start or Exit at bottom, LinesTrunks, TT/LS Disc, LS Disconnect, choose Yes, press Enter.

Try that out.

Jesse

 

[SYQUEST]

What end office switch is serving the Magix?

There is a known issue with the GTD5 EAX with CENTRANET lines providing a DELAYED disconnect signal in California in GTE/VZN land. The delay can be up to 45 seconds. At that point it would be obvious that the call will go to the CASO.

Another way to see how long it takes to get the disconnect signal and drop the call, is to place the answered call on HOLD and hangup the calling end and time from that point until the lite goes out.

....JIM....

 

[wheelma2]

tekguy125's suggestion was the fix... oddly enough I was on the "LS Reliable Disconnect" screen (in WinSPM) as I received the email alert for his post. This value was set to "No". I verfied that it is set to "Yes" at another of our offices with lines from the same CO. I went ahead and changed it to "Yes" and placed a test call... sure enough... no phantom call this time.

THANKS!!!!!!

 

[tekguy125]

Thanks for the star!