[cisco-voip] External Call Control Profile

Florian Kroessbacher florian.kroessbacher at gmail.com
Sat Jan 10 13:26:12 EST 2015


hy


i thnxs


--

Florian Kroessbacher 
florian.kroessbacher at gmail.com

On Sat, Jan 10, 2015 at 6:57 PM, Anthony Holloway
<avholloway+cisco-voip at gmail.com> wrote:

> I haven't read the doc yet, and I will, but this seems correct.
> The whole purpose of CURRI is to enhance the routing decision beyond the
> capabilities of CUCM. Which are basically route or block, or ToD filtering.
> If you want to apply an ECCP to all calls being made by an extension, you
> might be able to place a catch all translation pattern in front of all
> other patterns.
> Example:
> 1. DN 1000 dials 2000
> 2. XLATE XXXX with ECCP attached
> 3. DN 2000
> I'll reply again if I find verbiage to support my thought, but my gut tells
> me I won't find anything. For the same reason you won't find documentation
> stating you can't make a call from a route pattern, but you can from a
> translation pattern. It's sort of implied.
> On Fri, Jan 9, 2015 at 6:11 PM Florian Kroessbacher <
> florian.kroessbacher at gmail.com> wrote:
>> Hy Guys
>>
>> I'm Trying do do something with CURRI.
>> So i'm testing now my Application.
>>
>> The Setting is made on Directory Number BASE (Callmanger 10.5.1.10000-7)
>> when will Callmanger go to the External Call Controll Server
>> * Only on outbound Calls
>> * Only on inbound Calls
>> * For all Call's inbound/outbound
>>
>> In my Test i only see Calls which are going to the Directory Number doing
>> Webrequest to the Routing Server
>>
>> is this per Design or do i have to Contact TAC
>>
>> --
>>
>> Florian Kroessbacher
>> florian.kroessbacher at gmail.com
>>
>> [image: Twitter] <https://twitter.com/flohATinnsbruck> [image: Google
>> Plus] <https://plus.google.com/+FlorianKroessbacher> [image: Linkedin]
>> <https://www.linkedin.com/profile/view?id=115928906>
>>  _______________________________________________
>> 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/20150110/6730545b/attachment.html>


More information about the cisco-voip mailing list