[cisco-voip] Automating on call schedules?

[Anthony Holloway]

If you have AXL experience, then it would be trivial to run the following
SQL command via AXL SQL Toolkit:

update remotedestinationdynamic set destination = '<New RD Number>' where
destination = '<Current RD Number>'

Alternatively, the AXL method updateRemoteDestination (
http://developer.cisco.com/axl/Files/AXLSoap_updateRemoteDestination.html)
is where you want to look.

In PHP using the SoapClient class (
http://php.net/manual/en/class.soapclient.php) it would look like this:

$axl_resp = $soap_client->connection->updateRemoteDestination(array(
    'destination' => '<Current RD Number>',
    'newDestination' => '<New RD Number>'
));

And because RD numbers are unique within a system, both of these work this
easily.


On Tue, Apr 30, 2013 at 10:51 AM, Erick Wellnitz <ewellnitzvoip at gmail.com>wrote:

> I have plenty of AXL code laying around in both C# and Perl that I could
> adapt.  I'll take a look at CURRI and hopefully before this becomes too
> time consuming the 'mystery API' will be available.
>
>
>
>
> On Tue, Apr 30, 2013 at 10:39 AM, Stephen Welsh <
> stephen.welsh at unifiedfx.com> wrote:
>
>>  Are you adverse to writing some code, or just the fun of AXL ;)
>>
>>  How about this approach:
>>
>>  Create some translation rules that sit at the start of the in-bound
>> call path and use the "Routing Rules interface" API (aka CURRI) to
>> re-direct based on the time of day, on-call rota etc.
>>
>>  The good thing about CURRI is the behaviour if your application is
>> off-line, the call just follows the translation pattern after a predefined
>> time-out (only delay is the first failed request). It's a lot simpler than
>> AXL and JTAPI to implement, you just need a simple DB/CSV file to hold your
>> call routing rules/schedule and a single web service (i.e. a ASP page if
>> you are old school) to respond with the destination to redirect the call to.
>>
>>  The CURRI API is documented here:
>> http://developer.cisco.com/web/curri/home
>>
>>  Also,
>> There is a new CUCM API (can't say anything as it's not released yet)
>> that's a lot easier than AXL to implement but would allow solve this
>> problem too ;)
>>
>>  If you do for a CURRI (pun intended ;) I'd be keen to find out how you
>> get on...
>>
>>  Thanks
>>
>>  Stephen Welsh
>>  CTO
>> http://www.unifiedfx.com
>>
>>
>>  On 30 Apr 2013, at 16:15, Erick Wellnitz <ewellnitzvoip at gmail.com>
>>  wrote:
>>
>>  HI all!
>>
>> I know on call rotations have been discussed before, mostly with UCCX and
>> either a DB dip or XML.
>>
>> Short of writing my own AXL code and using cron/task scheduler, is there
>> a decent way of automating this process so I don't have to manually change
>> a dozen remote destinations every week?
>>
>> Thanks!
>>  _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>>
>>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20130501/e31c328b/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 1364 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20130501/e31c328b/attachment.png>