CCM Security – MGCP

crypto isakmp policy 1
encr 3des
authentication pre-share
group 2
lifetime 10800
crypto isakmp key cisco address 10.1.1.1
crypto isakmp key cisco address 10.1.1.2

!
!
crypto ipsec transform-set CM esp-3des esp-sha-hmac
mode transport
!
crypto map CM 1 ipsec-isakmp
set peer 10.1.1.1
set transform-set CM
match address 101
crypto map CM 2 ipsec-isakmp
set peer 10.1.1.2
set transform-set CM
match address 102

!
access-list 101 permit ip host 10.2.2.2 host 10.1.1.1

access-list 102 permit ip host 10.2.2.2 host 10.1.1.2
interface Serial0/0.101 point-to-point
ip address 10.2.2.2 255.255.255.0
frame-relay interface-dlci 101
crypto map CM

Time of Day routing

Rule of thumb.

a. First analyze and group the time-period for which you want the partition to be active. This could be business hours (M-F, 8-5 for say).

b. If the time slots cannot be grouped into one time period, define multiple time periods.

c. Group all timeperiods into one time schedule.

d. apply time schedule to partitions and partitions to CSS.

e. calling devices should use this CSS (Gateways/ phones etc)

f. Note that when you want differential call treatment based on ToD, you need to create a tie on the dialed number. To create the tie, you have to define the same number (say 1005) twice  one in each partition P1 and P2. P1 may be a TOD enabled partition, while P2 may be a normal partition. P1 will be listed above P2 in the calling device CSS.

Callforward behaviour in 4.1

Callforward All

If the Call Forward all CSS is set to none, it will concatenate the line and device CSS. This applies to settings done via the phone as well as via the CCM user page.

Callforward Busy/No-answer 

If the Callforward CSS is set to none, it does not concatenate the line and device CSS.

Line Device CSS contatenation

In CCM 4.1, Callmanager concatenates the CSS of the device and lines and places the CSS of the lines in front of the CSS of the device.

As per SRND, For CTI ports and CTI Route points, it does the other way. ie, CSS of the device comes first followed by the CSS of the lines. This used to be the behaviour in CCM  3.1. This was not the case during testing. Even the CTI ports and CTI route points were using line CSS First

CMC and FAC

When you have a CMC and FAC enabled on a route pattern, you have to enter FAC first, before entering CMC code.

CMC codes do show up on CDR records (unlike FAC)

FAC and CDR

When you define FAC code names and auth codes, only FAC code names appear on CDR. (For added security). The auth codes themselves never show up.

Call Display restrictions

For internal calls, use translation patterns

Calling Line ID/Name Presentation: This is the Caller ID /Name that shows up at the destination phone while the phone is ringing and connected
Connected Line ID/Name Presentation: This is the Caller ID /Name that is displayed at the source phone while the destination phone is ringing and connected

To override the settings at the translation pattern, check the “Ignore Presentation Indicators (internal calls only)” at the phone. When this is enabled, it will override the Connected Line ID/Name at the source phone and Calling line ID/Name at the destination phone.

Interaction with Callpark

To enable restrictions on Call park numbers, you would need to define a transation pattern for each of the call park numbers. Say, if your Callpark is 400X, then you would need to add 10 translation patterns starting 4001, 4002.

Barge, CBarge and Privacy

Barge, CBarge and Privacy works only on shared lines.

Barge – Extension 2000 is shared across two phones A and B. B Calls C (2001) and is in connected state. Phone A will see the status of the line as “Remote in Use” and can use the Barge softkey to barge into B’s call. B and C hears a short beep and A,B,C are now in a conference. Barge uses the built-in bridge in the target (barged) device. (phone B in this case). There are two places where you can enable Barge and Privacy.

a. Under each phone configuration page, you can enable Built-in-Bridge (Barge) and Privacy. Default value is “Default” which means use Service parameter values.

b. Under Callmanager service parameter you can set Built-in-Bridge and Privacy. Default “Built-in-Bridge Enable” is set to Off and
“Privacy” is set to True.

To enable Barge softkey, you need to set one of the above settings (either under phone or service parameter). Built-in-Bridge should be set to On and Privacy should be set to Off for Barge to work.

Privacy turns off Barge capability on shared lines. This is default setting. Privacy also removes the call information from showing up on other shared lines.

When the Barge key is pressed two set of text show up on the Barger and Barged device. “To 2001″ and “To Barge”

CBarge works a little different from Barge. CBarge uses an actual Conference bridge specified in the device pool (MRGL, MRG etc), instead os using Built in Bridge. Once the CBarge key is pressed, the phone (Barger and Barged device) show as “To Conference”.

If Phone A and B are two in diff locations, and when A barges into B’s call, location bandwidth is deducted from A and B’s locations.

idivert vs ImmDiv

Using idivert function you can immediately send a call to voicemail. Please note that idivert will overwrite the original dialed number and forwarding number to the line that triggered idivert.

1022 calls 1024

1024 CFA to 5003

5003 hits idivert

Call gets to voicemails and user hears the greeting for 5003. In normal case, user would have heard the greeting for 1024.

Please don’t confuse this with the ImmDiv feature of IPMA. ImmDiv is used only to send calls back and forth between manager and assistant.

  

Video call

"Retry video call as Audio". If this is unchecked on the destination device and there is not enough video bandwidth for that location, then the call will not be retried as an audio and will also trigger AAR as a regular audio call.

Callback feature

Uses Cisco Extended functions service

To enable callback, all you need to do is to create a new softkey template and add the Callback softkey for Onhook and Ring Out states. Callback softkey on On hook state is used to check the status of the Callback and Callback softkey on Ring Out state is used to enable callback.  

Attendant Console – Extended functions

acconfig.bat settings

1. JTAPI password – use the clear text password here

2. Hunting algorithim – will show broadcast and circular. Depending on what is set on the Pliot point, it will either show Longest Idle or First Available agent. 

Attendant console Multiple login

Attendant console does not allow two users to login at the same time. When the second user tries to login, a pop-up message shows up asking if you want to logoff the currently logged in user. You can login only if you hit "Yes" to logoff the current user.

Also you cannot have two different users login to the same phone line. 

Attendant console Broadcast hunting

Can be enabled from the "acconfig.bat" tool. Broadcast hunting will place calls on the queue and will show up in the Broadcast calls pane in the Attendant console. The attendant can chose which call to answer on which line.

This works only when the members of the hunt group are user/line. This does not work when the hunt group uses directory numbers as members.

Global Directory > Auto Attendant

IPCC Express Auto Attendant application uses the name specified here for name dialing.

Significance of Primary Extension in Global Directory

This is used by the Auto attendant feature of IPCC express. When Auto attendant tries to transfer a call, it uses the Primary Extension and not the Telephone number.

How to enable blind transfer in IP Phones connected to Callmanager?

By default, blind transfer is not enabled for IP Phones. When you try to transfer a call, it would place the first line on hold and grab the second line and perform a consult transfer. To enable blind transfer, change the service parameter

Transfer On-hook Enabled to True.

This will allow users to hit the transfer softkey and dial the number and either go on-hook or hit the transfer softkey again to complete the call.

Hunt

Timers

1. Line Group > RNA Reversion timeout – this determines the number of seconds to ring at each line in the line group.

2. Hunt Pilot > Maximum Hunt Timer – this determines the total number of seconds a call will be tried within the hunt group before using the Forward Hunt No Answer setting.

Forward settings

1. Forward Hunt No Answer: Is used if a call that was presented to the hunt group was not answered by any member in the group or it reached the specified Maximum Hunt Timer.

2. Forward Hunt Busy: This is used when all members in the line group are busy.

Use Personal Preference: This flag uses the Call Forward No Coverage setting of the original dialed number. This is not used if the hunt pilot number was called directly. Usually used when you have a CTI RP or CTI port that is forwarded to the hunt pilot number.

MLPP on gateways

** MLPP settings does not work on FXO gateways.

** MLPP does work on gateways with T1 PRI and CAS (MGCP).

** No support for MLPP in H323 gateways. But on a ICT you will see a setting for Premption Indication. A trunk itself cannot be Prempted, so there is no way to enable Premption on an ICT. The premption indication on a ICT, helps in passing MLPP indication when a precedence calls is placed from one CM Cluster to another CM cluster.

Sample lab for MLPP testing on gateways: 

1. Set the gateway with MLPP Indication enabled and MLPP Premption enabled. Setup 1026 and 1027 with capability to call Exec override and Flash override respectively.

2. Set up a route pattern 9.@ in Exec partition with Exec override settings

3. Set up a route pattern 9.@ in Flash partition with Flash override settings

4. Point both 9.@ patterns to the MGCP T1 gateway. Busy out all channels except 1 channel. MLPP works only when the trunk is busy. Use B channel maintenance to do this.

5. Place a flash override call from 1027 and then place a exec override call from 1026. The call to 1027 is disconnected and the call from 1026 is connected to the dialed.

6. Place a exec override call from 1026 and then place a flash override call from 1027. The call to 1027 will not succeed and a Block Premption  Announcement is heard. "A equal or higher precedence call has prevented the completion of the call. Please hangup and try again later. This is a recording"

MLPP

How to setup basic MLPP ?

a. Take three phones 1025, 1026 and 1027. Let 1025 be the destination phone. 1026 be able to make Exec Override calls. 1027 be able to make Flash Override calls.

b. Set them all up in same MLPP domain 000011 (for ex:)

c. Set 1025 with MLPP indication enabled, Premption – Forceful

d. Set 1026 and 1027 with MLPP indication enabled, Premption – Can be disabled. No need to set them to forceful.

e. Create translation pattern 90.1025 in partition Exec and set the MLPP setting to Executive Override. This TP can be accessed only by 1026. Translate 90.1025 to 1025.

f. Create translation pattern 90.1025 in partition Flash and set the MLPP setting to Flash Override. This TP can be accessed only by 1027. Translate 90.1025 to 1025.

g. Place a flash override call from 1027 to 1025. (Dial 90.1025 from 1027.). You should note a different ring tone on 1025 and also a precedence ringer display.

h. Place a exec override call from 1026 to 1025 (Dial 90.1025 from 1026). You should immediately hear a precedence tone on 1025 and 1027. (Continous tone). Both parties 1025 and 1027 have to independently hangup. The Exec override call from 1026 is offered to 1025. Phone 1025 starts ringing.

i. If 1025 doesnt answer the exec override call from 1026, after 30 seconds, the call between 1025 and 1027 is dropped and the exec override call from 1026 is offered to 1025.

j. A flash override call cannot preempt a exec override call. If 1026 and 1025 are in a exec override call, a flash override call from 1027 cannot preempt the call between 1026 and 1025, as the flash override call has lower precedence. The flash override call will appear as call waiting on 1025. (No call waiting beep is heard).

k. An exec override call cannot preempt another exec override call (same domain), unless the service parameter Exec Override Call Preemptable is set to true. With the default setting (false), if 1026 places an exec override call to 1025, and 1027 places an exec override call to 1025, this call will appear as call waiting on 1025. (No call waiting beep is heard).

l. Do not set Preemption enabled to Forceful and Premption indication to Off of Default (If device pool is also off). This will prevent preemption on the destination device.

m. Only calls originating from devices in same domain can be prempted. If 1026 is set to domain 000011 and 1027 is set to domain 000022, 1026 cannot override 1027's call and vice versa.

n. If both 1026 and 1027 are set to flash override, One flash override call cannot preempt another flash override call. The call appears as call waiting (no beep is heard)