[cisco-voip] SIP and tcl applications

Jim McBurnett jim at tgasolutions.com
Tue Mar 22 16:26:36 EDT 2011


I just reproduced the same error on a PRI-
So we'll see what TAC says...


Jim

From: ATIENZA, Gonzalo [mailto:Gonzalo.ATIENZA at LA.LOGICALIS.COM]
Sent: Monday, March 21, 2011 4:43 PM
To: Jim McBurnett; cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] SIP and tcl applications

Hi Jim,

As far as I know those TCL applications provided by Cisco are only supported on pots dial-peers, hence they won't work with either H323 calls or SIP calls.

I´ve seen the same thing with the auto attendant TCL applications from Cisco, if you want to trigger the application with an incoming call to a voip dial-peer it just won't work, you will need to develop a different TCL script.

Regards.

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Jim McBurnett
Sent: lunes, 21 de marzo de 2011 05:10 p.m.
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] SIP and tcl applications

Interesting TAC case I had today.
In doing some testing with onramp and offramp faxing, I could not get it working on a SIP trunk.

The problem I kept seeing in the debugs was

 %CALL_CONTROL-6-APP_NOT_FOUND: Application onramp in dial-peer 400 not found.  Handing callid 39880 to the alternate app



When I got to the TAC engineer we went around the dial peers a few times before it was agreed upon that the dial-peers were correctly configured.

Call comes in as full e.164 from the sip provider and we strip all but the last 3.
Then those last three are forwarded on to the lab cluster.

In the end I was told that SIP trunks do not support TCL applications.

In retrospect I question...
Anyone have a different perspective?

Thanks,
Jim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20110322/9da65c46/attachment.html>


More information about the cisco-voip mailing list