Get Digit Scripting

[sandeepkaran]

Hi

I am trying to fix a script that has got Get Digit node.

The issue is if 5 digit wrong pin is entered ( CED) then it should get followed to default path case 4 after playing 3 attempts INvalid Pin.wav (PM), which is not happening, even though config param is 5,5,Y,3,5,3,2,N,Y,# and VRU name as GD,EnterPIN2,A

Attached is the snap shot of it.

Please advise if it is wrongly configured.

Regards,
SK

[sandeepkaran]

Attached is the config param....

[Chintan Gajjar]

lets say if user enters wrong PIN(1234), what call path does call take?

[sandeepkaran]

Hi Chintan,

Then it takes default path case 4 ( the reason is interdigit timeout - 3 secs gets over and goes thru fail node).

[Chintan Gajjar]

does the call comes out of failure path of run ext script node or case 4 of CED?

if it does come out of the failure path, than before call progress through failure path and based on your configuration it should give two retries for digit entering and on max failure come out of failure path.

Whats the behaviour?

[sandeepkaran]

Hi Chintan,

Yes it does come out of the failure node of Run External script of Get Digit and is been routed to case 4. It is the case when you have entered 1234 ( not 5 digits ) default retry limit is passed.

If you enter 12345 then it come out of failure node of CED then goes into a loop ( invalid pin .wav file and please enter digit 5 pin) and does not come out of failure node of Get digit. 

[Chintan Gajjar]

oh ok, so when you entered 12345 the GD microapp has successfully done its job of collecting 5 valid digits of the caller and put the value in Call.CallerEnteredDigits .

Now you have to have different logic to validate what's collected in Call.CallerEnteredDigits and drive call flow further.

In Your case, your CED node does not have any match for "12345" , so fails out of failure path. if you want 12345 as one of the valid PIN, Edit the CED node attach 12345 to existing case or new case.

[sandeepkaran]

If the entered digit does match in CED then it should allow 3 times and then route it case 4 which is not happening.

[Chintan Gajjar · Accepted solution]

Then you have to do two things, lets say you want to allow over all 3 retries (if customer enters invalid digits(1234) or customer enters invalid PIN(12345) ), any case only 3 retires will be given.

1. reduce the number of retries in GD parameter from 2 to 1

2. implement a counter.

to implement counter, you can initialize the some CPV to 0 before menu, and increment its value by 1 whenever you come out of false path of VRU or CED node.

3. play invalid PIN message

4. check counter

You can check after playing invalid PIN message, if counter value is <= 3 then play back the GD Microapp, else connect to the case 4.

Check the sample script attached and modify your script likewise.

Please rate if you find it helpful.

[sandeepkaran]

Hi Chintan,

Apologizes for the delay. I used your method and it worked and got fixed.

I figured out what was happening.

 In Customer Voice Portal, the Collected digits will only be cached for a CAPTURE microapp following

the digit collection node. If a non-digit collect nodes follows a digit collect node, Customer Voice Portal’ s

CED variable will get nulled out and inturn Call.CallerEnteredDigits  also get nulled out .

Note

 For example, if the script is START  > GD (Get Digit node)  > CAPTURE NODE  > PM (Play Media)  >

CAPTURE NODE . In this case, user has to cache the collected data via ICM peripheral (or call) variables.

Thanks for helping it out.

I have attached my document. Just for your and anybody else looking for.

Regards,
Sandeep Karan