Callmanager Express Forced Authorization Codes

Unanswered Question
Dec 11th, 2009

Hello,

I am putting in a solution for a customer which includes Call Manager Express (latest version) and several phones that will be "public" phones.  These are for the lobby, lunch room, etc.

The customer has requested that these phones be able to always dial 911 and local numbers, but to require a code to dial long distance.  Does CME include anything that can provide this functionality?

Thanks for any advice,

Bill

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Paolo Bevilacqua Fri, 12/11/2009 - 09:31

Sure, you can use COR, or a translation-profile that discards everythign except 911 and call with code.

There is more than one way actually.

asandborgh Fri, 12/11/2009 - 09:31

Bill,

Might be easy, might be a bit of wrangling...

From:

http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/admin/configuration/guide/cmeblock.html

Prior to Cisco Unified CME 4.2(1), all Call Blocking features are implemented globally and uniformly on each phone in the system. All phones are similarly restricted according to time, date, location, and other call blocking characteristics. Call Blocking is not supported on ephone-dns that are configured to use the trunk feature, and Call Blocking did not apply to second-stage trunk dialing.

In Cisco Unified CME 4.2(1) and later versions, you have the flexibility to set different call block calendars and call block patterns to phones in different departments, to block certain trunk dialing as required, and to configure Call Blocking on a particular SCCP IP phone by creating and applying a template to that phone.

For configuration information, see the "Configuring Call Blocking" section.

Call Blocking Override

The after-hours configuration applies globally to all dial peers in Cisco Unified CME. You can disable the feature on phones using one of three mechanisms:

directory number—To configure an exception for an individual directory number.

phone-level—To configure an exception for all directory numbers associated to a Cisco Unified IP phone regardless of any configuration for an individual directory number.

dial peer—To configure an exception for a particular dial peer.

Individual phone users can be allowed to override call blocking associated with designated time periods by entering personal identification numbers (PINs) that have been assigned to their phones. For IP phones that support soft keys, such as the Cisco Unified IP Phone 7940G and the Cisco Unified IP Phone 7960G, the call-blocking override feature allows individual phone users to override the call blocking that has been defined for designated time p

HTH,

Art

Michelle Jardim Fri, 12/11/2009 - 09:58
Sending some features description:


Introducing Client Matter Codes

To use the Client Matter Codes feature, users must enter a client matter
code to reach certain dialed numbers. You enable or disable CMC through
route patterns, and you can configure multiple client matter codes. When a
user dials a number that is routed through a CMC-enabled route pattern, a
tone prompts the user for the client matter code. When the user enters a
valid CMC, the call occurs; if the user enters an invalid code, reorder
occurs. The CMC writes to the CDR, so you can collect the information by
using CDR Analysis and Reporting (CAR), which generates reports for client
accounting and billing.

The Client Matter Codes feature benefits law offices, accounting firms,
consulting firms, and other businesses or organizations where tracking the
length of the call for each client is required. Before you implement CMC,
obtain a a list of all clients, groups, individuals, parties, and so on that
you plan to track through CMC. Determine whether you can assign the codes
consecutively, arbitrarily, or whether your organization requires a special
code structure; for example, using existing client account numbers for CMC.
For each client (or group, individual, and so on) that you want to track,
you must add a client matter code in the Client Matter Code Configuration
window of Cisco CallManager Administration. Then, in Cisco CallManager
Administration, you must enable CMC for new or existing route patterns.
After you configure CMC, make sure that you update your dial plan documents
to indicate the CMC-enabled route patterns.


Clicking on the link below you can get more details:

http://www.cisco.com/en/US/customer/docs/voice_ip_comm/cucm/admin/4_1_3/ccmf
eat/fsfaccmc.html#wp1052254


Introducing Forced Authorization Codes

When you enable FAC through route patterns in Cisco CallManager
Administration, users must enter an authorization code to reach the intended
recipient of the call. When a user dials a number that is routed through a
FAC-enabled route pattern, the system plays a tone that prompts for the
authorization code.

In Cisco CallManager Administration, you can configure various levels of
authorization. If the user authorization code does not meet or exceed the
level of authorization that is specified to route the dialed number, the
user receives a reorder tone. If the authorization is accepted, the call
occurs. The name of the authorization writes to call detail records (CDRs),
so you can organize the information by using CDR Analysis and Reporting
(CAR), which generates reports for accounting and billing.

You can use FAC for colleges, universities, or any business or organization
when limiting access to specific classes of calls proves beneficial.
Likewise, when you assign unique authorization codes, you can determine
which users placed calls. For each user, you specify an authorization code,
then enable FAC for relevant route patterns by selecting the appropriate
check box and specifying the minimum authorization level for calls through
that route pattern. After you update the route patterns in Cisco CallManager
Administration, update your dial plan documents to define the FAC-enabled
route patterns and configured authorization level.

To implement FAC, you must devise a list of authorization levels and
corresponding descriptions to define the levels. You must specify
authorization levels in the range of 0 to 255. Cisco allows authorization
levels to be arbitrary, so you define what the numbers mean for your
organization. Before you define the levels, review the following
considerations, which represent examples or levels that you can configure
for your system:

�Configure an authorization level of 10 for interstate long-distance calls
in North America.

�Because intrastate calls often cost more than interstate calls, configure
an authorization level of 20 for intrastate long-distance calls in North
America.

�Configure an authorization level of 30 for international calls.


Clicking on the link below you can get more details:

http://www.cisco.com/en/US/customer/docs/voice_ip_comm/cucm/admin/4_1_3/ccmf
eat/fsfaccmc.html#wp1052254


Account Code Entry
The Cisco�Unified�IP Phones�7940 and 7940G and the Cisco�Unified�IP Phones
7960 and 7960G allow phone users to enter account codes during call setup or
when connected to an active call using the Acct soft key. Account codes are
inserted into call detail records (CDRs) on the Cisco�Unified�CME router for
later interpretation by billing software.
An account code is visible in the output of the show call active command and
the show call history command for telephony call legs and is supported by
the CISCO-VOICE-DIAL-CONTROL-MIB. The account code also appears in the
"account-code" RADIUS vendor-specific attribute (VSA) for voice
authentication, authorization, and accounting (AAA).
To enter an account code during call setup or when in a connected state,
press the Acct soft key, enter the account code using the phone keypad, then
press the # key to notify Cisco�Unified�CME that the last digit of the code
has been entered. The account code digits are processed upon receipt of the
# and appear in the show output after processing.
No configuration is required for this feature.

Clicking on the link below you can get more details:

http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/admin/configuration/guid
e/cmesoftk.html#wp1015257


Please take a look on these features description and verify which one is
better for you.

There are some observation about those features:

CMC: It is supported only by CCM. It is supported by all IP Phone modules.

FAC: It is supported only by CCM. For CME, there is a XML script. Using the
script, the code doesn�t appear in CDRs. It is supported by all IP Phone
modules.

In attach, you can find the TCL script and an example of configuration (step-by-step)
on Readme file.

Bellow one example:

application
  service acctfixedpin tftp://10.2.2.1/acctfixedpin.tcl
  param uid-len 5
  !
dial-peer voice 696969 voip
service acctfixedpin


Account Code: It is supported by CME. It is supported only by 7940/7940G and
7960/7960G Modules.
Paolo Bevilacqua Fri, 12/11/2009 - 11:02
Sending some features description:

[much outdated and irrelevant to the discussion text follows]

CMC: It is supported only by CCM. It is supported by all IP Phone modules.

Incorrect. CMC are supported by CME also.

FAC: It is supported only by CCM. For CME, there is a XML script. Using the
script, the code doesn�t appear in CDRs. It is supported by all IP Phone
modules.

Incorrect. What CCM calls FAC, is just called and done in another way on CME.
The script is TCL-IVR, not XML.

In attach, you can find the TCL script and an example of configuration (step-by-step)
on Readme file.E.g:


There is no need for external script. This TCL/IVR script, as many others is embedded
in IOS image and directly reference with the "service" command in "application" configuration mode.






euvazhanov Mon, 08/05/2013 - 04:14

Hi All,

Any news about using FAC im CUCME without scripts? Is it possible for this version?

show version

Cisco IOS Software, 2800 Software (C2800NM-ADVENTERPRISEK9-M), Version 12.4(24)T

show telephony-service

CONFIG (Version=7.1)

Thanks for any replies.

Actions

This Discussion