R2511-HP MSR Router Series Voice Configuration Guide(V5)

309
Analysis
After the subscriber presses the # key, the call jumps to node 10 that is not configured with any operation,
and thus the call is terminated.
Solution
Configure functions for node 10: playing voice files and executing normal secondary call.
Loopback node
Symptom
The subscriber dials the IVR access number 300 and presses the # key to jump to node 10, but the call
is terminated.
Following are the configurations:
[Sysname-voice-dial] entity 300 ivr
[Sysname-voice-dial-entity300] match-template 300
[Sysname-voice-dial-entity300] ivr-root 1
[Sysname-voice-dial-entity300] quit
[Sysname-voice-dial] quit
[Sysname-voice] ivr-system
[Sysname-voice-ivr] node 1 jump
[Sysname-voice-ivr-node1] user-input # goto-node 10
[Sysname-voice-ivr-node1] quit
[Sysname-voice-ivr] node 10 service
[Sysname-voice-ivr-node10] operation 1 goto-node 11
[Sysname-voice-ivr-node10] quit
[Sysname-voice-ivr] node 11 service
[Sysname-voice-ivr-node11] operation 1 goto-node 12
[Sysname-voice-ivr-node11] quit
[Sysname-voice-ivr] node 12 service
[Sysname-voice-ivr-node12] operation 1 goto-node 10
Analysis
After the # key is pressed, the IVR process jumps to node 10, and then jumps to node 11, n o d e 12, a n d
jumps back to node 10 again. Node 10 is the loopback node that causes the termination of the call.
Solution
Modify the configuration for node 10, such as configuring a calling operation for it.
Node depth exceeds eight levels
Symptom
When the IVR process jumps to node 8, the call is terminated.
Following are the configurations:
[Sysname-voice-dial] entity 300 ivr
[Sysname-voice-dial-entity300] match-template 300
[Sysname-voice-dial-entity300] ivr-root 1