Created by: Mark Alliban on 11-06-2012 11:51:25 AM Hi all, We've been using TCL for auite a while to run our LCR application and call billing. But to be honest it's having issues. 1) It uses RADIUS messages to send billing information (call start, carrier selection, call hangup etc). These are sent as UDP hence sometimes go AWOL and billing is not done properly. 2) We are having issues with the code (calls remaining visible on "show call acti voi bri" but not showing up on the termination gateway, and the billing shows a hangup and disconnection... etc). It all works perfectly if I do a test when traffic is low. But when there are 300 simultaneous calls, I find TCL extremely hard to debug. 3) To be honest I just find TCL is a complete PITA. It's hard to figure out where the code is going wrong or even what is gonig on half the time. So unless these can be overcome I would ideally like to convert our applications to make them more manageable. First obvious choice for me was VoiceXML, I understand with that I can make requests to a web server to do the billing, that should be much more reliable than RADIUS/UDP. But we use 7200VXR gateway, VoiceXML is not supported on this... What would anyone recommend I do?!
Subject: Re: New Message from Mark Alliban in Voice Gateway API (VGAPI) - TCL-API: T Replied by: LEON MCCALLA on 11-06-2012 01:33:13 PM Mark, I’d be interested to share my findings with you offline. At 600 calls I rarely miss any records. (rarely is under 1/1000)
On the other hand I have been having trouble with large scale routing.
Leon leonmccalla at hotmail.com
From: Cisco Developer Community Forums Sent: Monday, June 11, 2012 11:51 AM To: cdicuser@developer.cisco.com Subject: New Message from Mark Alliban in Voice Gateway API (VGAPI) - TCL-API: TCL replacement?
Mark Alliban has created a new message in the forum "TCL-API":
-------------------------------------------------------------- Hi all, We've been using TCL for auite a while to run our LCR application and call billing. But to be honest it's having issues. 1) It uses RADIUS messages to send billing information (call start, carrier selection, call hangup etc). These are sent as UDP hence sometimes go AWOL and billing is not done properly. 2) We are having issues with the code (calls remaining visible on "show call acti voi bri" but not showing up on the termination gateway, and the billing shows a hangup and disconnection... etc). It all works perfectly if I do a test when traffic is low. But when there are 300 simultaneous calls, I find TCL extremely hard to debug. 3) To be honest I just find TCL is a complete PITA. It's hard to figure out where the code is going wrong or even what is gonig on half the time. So unless these can be overcome I would ideally like to convert our applications to make them more manageable. First obvious choice for me was VoiceXML, I understand with that I can make requests to a web server to do the billing, that should be much more reliable than RADIUS/UDP. But we use 7200VXR gateway, VoiceXML is not supported on this... What would anyone recommend I do?! -- To respond to this post, please click the following link:
Subject: RE: TCL replacement? Replied by: Mark Alliban on 12-06-2012 08:35:26 AM Leon Thanks for the offer but really I an not looking for a 1/1000 packet loss. It is not good for us to give away 1 in 1000 calls for free! I am looking for a 0 packet loss and that means TCP. I am not aware of any way of moving to TCP for billig messages using TCL. VoiceXML is not compatible with my 7200 series. Plus I believe Cisco no longer supports TCL.
So I am really confused, what do people use to create applications on 7200 series voice gateways?
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:
