04-21-2011 08:25 AM - edited 03-16-2019 04:38 AM
Hi,
I am working on a TCL script and would like to test it. I have a 2811 and CUCM with two cisco phones and one analog phone. This is in a lab environment. I am attempting to trigger the TCL script by calling the dial peer with the script attached to it, but it doesn't seem to work. I need to trigger it from inside the network.
This is the dial peer I am calling extension 2002 to from attempting to trigger the script.
Router#sh run | s dial-peer
dial-peer voice 2000 voip
destination-pattern 2...
session target ipv4:10.10.25.254
dtmf-relay h245-alphanumeric
codec g711ulaw
This is the dial peer that has the script in it. I have tried both incoming called number and destination pattern with no luck.
dial-peer voice 2002 voip
service disa
session target ipv4:10.10.25.254
incoming called-number 2002
dtmf-relay h245-alphanumeric
Any help would be greatly appreciated.
04-25-2011 02:01 PM
Post a show tech from the GW.
Show flash
Debug voip ccapi inout with calling and called number
04-25-2011 02:19 PM
the debug voice ccapi doesn't show anything different, I can only get output when I use tha analog phone hooked up to an fxs port, the two ip phones in the lab are registered to CM and don't show any output when i dail to the disa line from them.
Router#sh flash
-#- --length-- -----date/time------ path
1 66483320 Oct 25 2009 03:45:24 +00:00 c2800nm-adventerprisek9-mz.151-3.T.bin
2 39540 Feb 28 2011 22:22:38 +00:00 auth_fail_final.AU
3 24476 Feb 28 2011 22:23:40 +00:00 en_enter_pin.AU
4 11020 Feb 28 2011 22:24:44 +00:00 out_of_time.AU
5 5778 Feb 28 2011 22:25:20 +00:00 DISA.tcl
04-25-2011 03:14 PM
dial-peer voice 222 voip
service disa
destination-pattern 2010
session target ipv4:
incoming called-number 2010
codec g711ulaw
no vad
session target is missing that dial-peer.
Can you please verify whether the CUCM Route-patterns are setup correctly? Can you call the FXS Analog phone on the GW from the CUCM?
04-25-2011 03:57 PM
Hm, I can't call from the gw to the analog phone, let me get that sorted out.
04-25-2011 03:16 PM
*Apr 25 21:19:41.572: //37/91862E598055/CCAPI/cc_process_call_setup_ind:
Event=0x4AD47728
*Apr 25 21:19:41.572: //37/91862E598055/CCAPI/ccCallSetContext:
Context=0x48E43404
*Apr 25 21:19:41.572: //37/91862E598055/CCAPI/cc_process_call_setup_ind:
>>>>CCAPI handed cid 37 with tag 2003 to app "_ManagedAppProcess_Default"
If everything is working correctly we should see DISA app instead of "_ManagedAppProcess_Default"
04-26-2011 08:53 AM
Ok, I resolved the rout list issue. I can now call the voip phones from the ananlog phone hooked up to the VG via fxs. The VG is set up as both h323 and mgcp, the fxs ports are being handled by h323.
When I call the DISA number now 2010 I can see that the right dial peer is being triggered by doing a sh voice call status. I here two ring tones and then it seems as if the call is answered but after a few seconds I here another ring. When that happens, the call is no longer triggering the correct dial peer, it instead is triggering dial peer 200, which is weired because I have not created a dial peer 200.
When I loaded the script i did this.
application
service new-call flash:DISA.tcl
paramspace english language en
paramspace english index 0
paramspace english location flash
paramspace english prefix en
That loaded the script. I then uploaded the audio files to flash. I think I used a command audio load.
Do you think I made a mistake in loading the script or files? Thanks in advanced.
04-26-2011 10:08 AM
04-26-2011 11:21 AM
I haven't tried the DISA myself!
But try this
voice translation-rule 2009
rule 1 /2009/ //
voice translation-profile 2009
translate called 2009
dial-peer voice 222 voip
translation-profile incoming 2009
I can see a
*Apr 26 17:06:56.823: vsacount in free is 2
*Apr 26 17:06:56.827: //116/65978F9A808F/CCAPI/cc_api_call_disconnected:
Cause Value=28, Interface=0x4A3C9228, Call Id=116
*Apr 26 17:06:56.827: //116/65978F9A808F/CCAPI/cc_api_call_disconnected:
Call Entry(Responsed=TRUE, Cause Value=28, Retry Count=0)
Cause No. 28 - invalid number format (address incomplete).
This cause indicates that the called party cannot be reached because the called party number is not in a valid format or is not complete.
Even the doc https://supportforums.cisco.com/docs/DOC-9795#Does_the_UC500_support_Dial_Inward_System_Access_DISA suggests removing the called number.
/divin
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide