We've Moved! Please visit our new and improved forum over at our new portal: https://portal.plumvoice.com/hc/en-us/community/topics
Identify server down
Identify server down
Our Telephony application is installed in our database server. Application URL is provided in the Plum box applications setup. In case if the database server is powered down, Plum plays "We are experiencing technical difficulties" as that is the exception handler for that vxml file. But after that we call 'disconnect.vxml' for a clean application exit. Since the database server is powered down, 'disconnect.vxml' cannot be accessed from Plum box. After this nothing happens other than the line being connected always. The line is not disconnected. We understand the fact that it's expecting <disconnect/> but is there a time limit after which the line will be disconnected automatically or is there a different solution for this scenario.
behavior for when the IVR system receives a fetch error
Hello,
If the IVR system receives a fetch error when attempting to retrieve your initial application it will play the IVR error message and then immediately disconnect the line. The only case where an IVR application will loop "forever" is if an application is collecting input from the user and does not make use of the count attribute of the <noinput> tag to force a disconnect. This is not an issue if the IVR system is unable to fetch the initial application.
If your IVR application attempts to collect input from the user without trapping the <nomatch>, an infinite loop detection system will trigger a error/disconnect after 100 iterations. The time that it takes to hit the infinite loop counter depends on how long your prompts take to play.
Regards,
Plum Support
If the IVR system receives a fetch error when attempting to retrieve your initial application it will play the IVR error message and then immediately disconnect the line. The only case where an IVR application will loop "forever" is if an application is collecting input from the user and does not make use of the count attribute of the <noinput> tag to force a disconnect. This is not an issue if the IVR system is unable to fetch the initial application.
If your IVR application attempts to collect input from the user without trapping the <nomatch>, an infinite loop detection system will trigger a error/disconnect after 100 iterations. The time that it takes to hit the infinite loop counter depends on how long your prompts take to play.
Regards,
Plum Support