[cisco-voip] Question about using Forced Activation Codes or Client Matter codes on internal calls

[Lelio Fulgenzi]

FACs and CMCs can only be used on route patterns so getting them to work on internal calls will be a bit more work and it's something I've wanted to do for a while for things like paging systems that do not have security built in. 

I think I've read on list a few times that you can create a SIP trunk loopback of sorts, which should work. Other than that, I can only think of a T1 to T1 crossover, but that limits you to 23 calls and is an expensive hardware solution. 

--- 
Lelio Fulgenzi, B.A. 
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN) 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
Cooking with unix is easy. You just sed it and forget it. 
- LFJ (with apologies to Mr. Popeil) 



From: "Paul Bottone" <paulb at uwo.ca> 
To: cisco-voip at puck.nether.net 
Sent: Thursday, November 18, 2010 12:12:37 PM 
Subject: [cisco-voip] Question about using Forced Activation Codes or Client Matter codes on internal calls 

I have been asked to control calls going to a specific phone number by using either FAC or CMC codes to know who called the number and / or connect the call to the number. 

Has anyone used either FAC or CMC codes to control internal calls? Is there another way to prevent the call connecting and know who made the call? 
The phone in question is in its own Calling Search Space and its own Partition, but by giving them these codes we can tell who called the number and when. 

If you have, how did you configure CUCM to use the codes? 

Thanks 
Paul 

-- 
Paul Bottone <paulb at uwo 



Paul Bottone; paulb at uwo.ca 
Telecom Network Analyst 
The University of Western Ontario 
ITS NOC 
Phone: (519) 661-2014 
_______________________________________________ 
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/20101118/02ecbdfd/attachment.html>