[prev in list] [next in list] [prev in thread] [next in thread]
List: cisco-voip
Subject: Re: [cisco-voip] Automating on call schedules?
From: Erick Wellnitz <ewellnitzvoip () gmail ! com>
Date: 2013-04-30 15:51:45
Message-ID: CAK0wOsB4JKaDA3=mug=LbOxSnhrcnz4wjH72K0S3BwQAObRFRg () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/related)]
[Attachment #4 (multipart/alternative)]
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@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@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@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>
[Attachment #7 (text/html)]
<div dir="ltr"><div>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.</div> <div> </div><div> \
</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Apr 30, \
2013 at 10:39 AM, Stephen Welsh <span dir="ltr"><<a \
href="mailto:stephen.welsh@unifiedfx.com" \
target="_blank">stephen.welsh@unifiedfx.com</a>></span> wrote:<br> <blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">
<div style="word-wrap:break-word">
Are you adverse to writing some code, or just the fun of AXL ;)
<div><br>
</div>
<div>How about this approach:</div>
<div><br>
</div>
<div>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.</div> <div><br>
</div>
<div>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.</div> <div><br>
</div>
<div>The CURRI API is documented here:</div>
<div><a href="http://developer.cisco.com/web/curri/home" \
target="_blank">http://developer.cisco.com/web/curri/home</a></div> <div><br>
</div>
<div>Also,</div>
<div>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 \
;)</div> <div><br>
</div>
<div>If you do for a CURRI (pun intended ;) I'd be keen to find out how you get \
on...</div> <div><br>
</div>
<div>Thanks</div>
<div><br>
<div>
<div style>
Stephen Welsh</div>
<div style>
CTO</div>
<a href="http://www.unifiedfx.com" target="_blank">http://www.unifiedfx.com</a></div>
<div><br style>
<span><img src="cid:CBBF0493-235C-43D2-A874-9FB3D95AF598@b2.unifiedfx.com" \
width="100" height="16"></span> </div>
<br>
<div>
<div>On 30 Apr 2013, at 16:15, Erick Wellnitz <<a \
href="mailto:ewellnitzvoip@gmail.com" \
target="_blank">ewellnitzvoip@gmail.com</a>></div> <div> wrote:</div>
<br>
<blockquote type="cite">
<div dir="ltr">
<div>HI all!</div>
<div> </div>
<div>I know on call rotations have been discussed before, mostly with UCCX and either \
a DB dip or XML.</div> <div> </div>
<div>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?</div> <div> </div>
<div>Thanks!</div>
</div>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" \
target="_blank">cisco-voip@puck.nether.net</a><br> <a \
href="https://puck.nether.net/mailman/listinfo/cisco-voip" \
target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br> \
</blockquote> </div>
<br>
</div>
</div>
</blockquote></div><br></div>
--bcaec54859e077e40804db95faad--
["image003.png" (image/png)]
_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic