IVR - An IVR port is Idle, but the device log shows it stuck in...

Expand / Collapse
 

IVR - An IVR port is Idle, but the device log shows it stuck in an infinite loop


Article ID:  - Last Review: November 18, 2015

PROBLEM

An IVR port is Idle, but the device log for that port is showing an infinite loop



SYMPTOMS

In the RoutingInbound log (or IVRInbound in previous versions of IVR) you will see lines similar to the following:

Info: 2015-Jul-10 11:12:41.347   1.15|MenuActivity - [1.15: Menu] - Condition branch result - Branch Name: Failure Condition Name: Menu 3722 - 10.192.160.120 (3722 - 10.192.160.120)
Info: 2015-Jul-10 11:12:41.352   <1.27|Branch> [Failure] - Sequence[ -> Invalid -> Goto] (3722 - 10.192.160.120)
Info: 2015-Jul-10 11:12:41.352   <1.27|Branch> [Failure] - Sequence[ -> Invalid -> Goto] (3722 - 10.192.160.120)
Info: 2015-Jul-10 11:12:41.352   <1.27|Branch> [Failure] - Sequence[ -> Invalid -> Goto] (3722 - 10.192.160.120)


 

CAUSE

The Menu activity has a GoTo activity linked back to the top of the menu in the Failed branch.  This means that the workflow can not end once it is in a failure situation. 



RESOLUTION

Do not put a GoTo activity in the Failure branch.

The Failure branch should be used to gracefully end the workflow in the case of a failure.  Ensure that the workflow can flow to an End point, and if desired add an activity into Failure to notify you. 



APPLIES TO

MiCC Version  

Keywords: ivr port loop infinite



Rate this Article:
     

Add Your Comments


Name: *
Email Address:
Web Address:
Verification Code:
*
 

Details
Last Modified:Thursday, November 19, 2015
Last Modified By: AndrewM
Type: FIX
Article not rated yet.
Article has been viewed 4,007 times.
Options