Article ID: 51462 - Last Review: , April 10th, 2012
PROBLEM
A single routing plan hangs up on the caller every attempt where a matched condition should continue to route the call.
SYMPTOMS
If you track the call through the MessageEngine logfile you will find it match a condition, then PROCCESSING Call Event. It will then be followed by something similar to:
Warning: 11/9/2011 8:10:33 PM [1031] - s<ActionBlindTransfer> () Node has timed out. [Timeout: 10000ms] [Diff: 10110ms] (Node - TimeoutExpired)
Warning: 11/9/2011 8:10:33 PM [1031] - t<ActionHangup>: s(<null>) f(<null>) t(<null>) (Callflow - set_CurrentNode)
Warning: 11/9/2011 8:10:33 PM [1031] - Port status changed [ANSWER] --> [HANGUP]. (Port - UpdateStatus)
CAUSE
There is a registry key under HKEY_LOCAL_MACHINE\Software\Mitel networks\6160\Features called IgnoreNewCallOnOriginalPBX whos default value is null. This key needs to have a value to function properly
WORKAROUND
1. Open the registry and locate HKEY_LOCAL_MACHINE\Software\Mitel networks\6160\Features
2. Right click on IgnoreNewCallOnOriginalPBX and choose Modify
3. Enter a value of 0
RESOLUTION
Issue resolved in Fix Pack 8
APPLIES TO
5.8
Keywords: IQ Hangup Callflow 5.8 Registry