Tcl IVR digit collect issue

[Humza Khan]

Assalam-o-Alikum,

I am having an issue regarding TCL IVR digit collection. Calls are working fine but when we dial an extension suppose 6657, on 3rd digit call hits on 6666 automatically, i running same tcl script in HO site. After this issue on remote site some changes done by myself in script but all in vain. i m attaching both actual and current tcl script. This issue checked through debug digit collect command. Debug logs are attached as well. 

Regards,

HK

[Carlo Poggiarelli]

Hi Humza..

Can you please post your actual config?

Thanks

Regards

Carlo

[Humza Khan]

Dear Carlo,

Please find attached actual and tcl related config files.

Regards,

HK

[Carlo Poggiarelli]

Hi.

In configuration you posted , you are missing the queuing part of application and other fundamental variable for a dial-by-extension .

What is the purpose of that application?

Please activate a debug voip application script, make a call to the application and post the output.

Thanks

Regards

Carlo

[Humza Khan]

Dear Carlo,

We are using tcl for basic ivr service. Logs file attached.

Regards, 

HK

[Carlo Poggiarelli]

Hi Humza.

On debug you sent, I don't see the behaviour  you reported.

Please collect following logs:

debug voip diapeer inout

debug voip application script

Of what I understand, this application should play a prompt asking the caller to insert a sequence of digits for desired destination.

Am I correct?

Let me know

Regards

Carlo

[Humza Khan]

Dear Carlo,

Yes, you are correct. Please see log file.

Now client office is close, so i will be with you tomorrow on same time.

Thanks for your support 

Regards,

HK

[Carlo Poggiarelli]

Hi.

Script is good and works correctly.

We have to look at dial plan.

From your debug, you are trying to reach extension 6655 and VG collects and routes the call correctly.

You have 3 diapeers for the same destination 6000,6001 and 2585 pointing to 10.101.100.1 (2 identical diapeers ) and to 10.101.100.2 (1 DP) I suppose they are 2 CUCM 

Can you check on cucm if extension 6655 is working correctly and if there are some active forwarding rules on dn configuration page.

Please try to configure a diapeer as follows

dial-peer voice 6655 voip

destination-pattern 6655

session target ipv4:10.101.100.1

dtmf-relay h245-alphanumeric

codec g711ulaw

no vad

After that try to call your application and select 6655

Activate a debug voip ccapi inout and post the output

Thanks

Regards

Carlo

[Humza Khan]

Dear Carlo,

Actually i m dialing 6587 ext. number from my phone after greeting, but call hitting on 6655 extension. I am unable to understand how to tackle this thing. 

Regards, 

HK

[Humza Khan]

Dear Carlo,

Output log file attached, kindly review.

I am dialing 6587 extension but call going on 6655. That's the issue i m facing.

As you said i have created dial-peer for this extension as well, but issue remains same.

dial-peer voice 7055 voip
 destination-pattern 6587$
 session target ipv4:10.101.100.1
 voice-class codec 1  
 dtmf-relay h245-alphanumeric
 no vad

Regards,

HK

[Carlo Poggiarelli]

Hi Humza.

On your dial-peer 7050 please modify dtmf-relay in h245-alphanumeric only.

Try it and activate a debug voip application script and a debug voip ccapi inout

Thanks

Regards

Carlo

[Humza Khan]

Dear Carlo,

Please find attached file. Logs taken after changing Dial-peer.

DGK-Voice#
DGK-Voice#sh run | sec dial-peer voice 7050

dial-peer voice 7050 voip
 service ivr
 incoming called-number 900
 voice-class codec 1  
 dtmf-relay h245-alphanumeric
 no vad
 

Regards,

HK

[Humza Khan]

Issue has been resolved by changing script.

Thanks for your help.

Regards, 

HK

[Humza Khan]

Now in this tcl everything is working fine, but fxo call issue observed phone constantly ringing after a call hang. So i have taken pcm capture but having trouble in open pcm log file. File attached.

Calling Number:4235762403    OR    4235717568
Called Number Extension: 6630

Regards,

HK 

[Carlo Poggiarelli]

Hi Humza.

Glad that it's working now.

Did you modify the script or you used the One from Cisco?

Thanks

Regards

Carlo