Protocol41

CMC/FAC in Cisco CUCME I got asked at work today to look in to CMC and FAC capabilities in Cisco UCME. Configuring these is fairly simple in CUCM (tick the boxes on the respective route patterns, create the required CMC/FAC codes) but I didn’t know how to do it in CUCME. So I went to find out. Client Matter Codes – Configuration Client Matter Codes (CMC) are codes that are used to represent a particular department/function/client and appear in call detail records to allow billing for calls to be done by department etc, or to log calls to clients in companies like law firms etc. In a CME setup we first need to ensure that the phones we need to have this feature are assigned a softkey template that includes the Acct (Accounting) softkey in the alerting and/or connected call states. ephone-template 1 softkeys alerting Acct Endcall softkeys connected Acct Hold Endcall Confrn Trnsfer Then, we must apply the particular template to the ephone(s) in question ephone 1 ephone-template 1 Once we reset the phones, they will display the Acct softkey in the alerting/connected states. Client Matter Codes – Usage To use the CMC feature in CUCME, the Acct softkey is pressed. After this, the user must enter the CMC in question and end it with a # symbol. Once this is entered it will show up in the show call active and show call history output and in CDRs if CDR logging is enabled on the CUCME. Forced Authorisation Codes – Configuration In CME, there isn’t an explicit FAC setup – instead we can use the after-hours configuration in telephony-service. In short, we’ll define every moment of every day as after-hours and configure specific patterns as after-hours blocked patterns. Then, we’ll configure each phone with a PIN that they can use to ‘log in’ and get around those after-hours restrictions. First however, we need to ensure that the phones have the login key available at the phone’s idle state. Let’s update the ephone-template we configured earlier ephone-template 1 softkeys idle Login Cfwdall Hlog Newcall softkeys alerting Acct Endcall softkeys connected Acct Hold Endcall Confrn Trnsfer Now that we’ve done that, we’ve got to define our after-hours time periods, and the patterns we’ll block (i.e. those that will require a login to dial) and (optionally) a non-default login timeout – i.e. how long they can get around the block pattern before having to log in again. In the example below, we are always blocking the 900T pattern (i.e. UK international calls using a PSTN access code of 9), and the login timeout is set to 5 minutes. telephony-service after-hours day Sun 00:00 23:59 after-hours day Mon 00:00 23:59 after-hours day Tue 00:00 23:59 after-hours day Wed 00:00 23:59 after-hours day Thu 00:00 23:59 after-hours day Fri 00:00 23:59 after-hours day Sat 00:00 23:59 after-hours block pattern 1 900T login timeout 5 We also have a few other options we can configure with this setup. Permanently blocked patterns (not really relevant if every time is after-hours, but useful otherwise) Special after-hours dates (e.g. 25th December, 1st January) After-hours exempt phones (e.g. super-important manager people!) An example of those features is given below telephony-service after-hours block pattern 1 90845T 7-24 after-hours date Jan 1 00:00 23:59 ! ephone 10 description :: IMPORTANT MANAGER PHONE :: button 1:10 type 7942 mac-address aaaa.bbbb.cccc after-hour exempt Now, let’s give some phones a PIN so they can dial the blocked patterns. ephone 11 description :: LESS IMPORTANT PHONE :: button 1:11 type 7942 mac-address aaaa.bbbb.dddd pin 1234 ! ephone 12 description :: LESS IMPORTANT PHONE :: button 1:12 type 7942 mac-address aaaa.bbbb.eeee pin 2234 Forces Authorisation Codes – Usage If you try and dial a blocked pattern during the after-hours time settings (which are, I believe, based on the time-zone configured in CME – so make sure that is set right!) you will get a reorder tone. If you press Login and enter your PIN and then try to dial it, the call will succeed. I think that’s about it… Update: It looks like CUCME 8.5 and above supports a propoer FAC setup, but I haven’t read this in any great detail yet: http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/admin/configuration/guide/cmefac.html