Outbound Calls

Version 1
    This document was generated from CDN thread

    Created by: Anupam Jain on 22-06-2012 02:14:43 AM
    We are using Cisco IOS Software, 2800 Software (C2800NM-ADVENTERPRISEK9_IVS-M), Version 15.1(4)M3.

    We wanted to know if there is a way to make outbound calls by making an HTTP call to the router (we are referring to the case when the platform itself makes an outbound call by receiving an HTTP request (not call transfers))

    This can be done on other voice platforms that we have used. Wanted to check if it's possible on Cisco IOS too? 
    Thanks in advance,

    Subject: RE: Outbound Calls
    Replied by: Raghavendra Gutty Veeranagappa on 22-06-2012 02:57:17 AM
    Hi Anupam,

    i don't think it is possible with tcl script, you can contact cisco TAC you might get an answer.


    Subject: RE: Outbound Calls
    Replied by: Anupam Jain on 22-06-2012 03:00:29 AM
    Hi Raghavendra,

    Thanks for your answer.

    Actually, I did contact TAC before writing on the forum but they told me that TAC is only a break-and-fix organization, so they cannot answer any feature support questions.

    Can you please help.


    Subject: RE: Outbound Calls
    Replied by: Travis May on 22-06-2012 04:32:36 AM

    You can do this by starting a persistent TCL "service" that polls an HTTP server every few seconds.  (use ::httpios )

    Loop over any records contained in the GET result, foreach start a a new TCL instance and pass the variables from the record.

    Good luck!


    Subject: RE: Outbound Calls
    Replied by: Grant Bagdasarian on 24-06-2013 07:43:14 AM
    Like Travis mentioned, you can use the polling method. We've also been doing this for quite a while now and it works good. 

    We built a TCL service which polls for calls from a web server every x seconds. But in order to place multiple calls at once, we need to start multiple instances of the TCL service. I couldn't get a single instance to place multiple calls. The polling method has a huge disadvantage when it comes to debugging. Once you enable logging and you have multiple instances polling every x seconds, the logging output becomes almost unreadable. 

    I don't know why Cisco doesn't have a HTTP interface for pushing instead of polling.