[cisco-voip] Dynamic Client Matter Codes

[Wes Sisk]

Not exactly, FAC and CMC are not that dynamic.  Much better approach to 
route calls over to IP-IVR to do database dip for lookup or validation.

You can change FAC/CMC via BPS or AXL, but even then it becomes limited 
compared to the potential number of tickets.  The database will allow 
adding CMC to your heart's content.  However, CM tends to fail to start 
after many are added.  CM is only tested up to 60,000 CMC.

While technically possible, it's just not particularly sane or 
scalable.  Send it to IP-IVR and database dip to your ticket system backend.

/Wes

On Monday, June 29, 2009 1:01:24 PM, Matthew Loraditch 
<MLoraditch at heliontechnologies.com> wrote:
>
> I don't think this is possible, but wanted to ping the list about it. 
> Would it be possible to setup calls to require a CMC but not need to 
> match it against any list? In this scenario the customer has a 
> ticketing system and would like to possibly associate calls by ticket 
> number. Tickets constantly opening and closing means a constantly 
> changing list of CMCs. The tickets are in a SQL DB so I could imagine 
> some sort of process that does an AXL update to Call Manager but 
> wondered if we could do something simpler.
>
> Thanks much!
>
>  
>
>  
>
> *Matthew Loraditch*
> 1965 Greenspring Drive
>
> Timonium, MD 21093
> support at heliontechnologies.com <mailto:support at heliontechnologies.com>
> (p) (410) 252-8830
> (F) (443) 541-1593
>
> Visit us at www.heliontechnologies.com 
> <http://www.heliontechnologies.com>
> Support Issue? Email support at heliontechnologies.com 
> <mailto:support at heliontechnologies.com> for fast assistance!
>
>  
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> 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/20090629/bd8ca5ef/attachment.html>