Cisco B-ACD on CME router - Drop-through option

In Cisco CME B-ACD, drop-through option can be configured so that when the AA services receive the incoming call, it will send the call directly to the call queue without provide menu options to callers.  This is useful for some small contact center backup, when the WAN link is downed and the site can't reach the contact center express or enterprise in the main site, it can still provide basic ACD service to the callers.

My Sample Configuration:

application

service aa flash:app-b-acd-aa-3.0.0.2.tcl

  paramspace english index 0

  param number-of-hunt-grps 1

  param drop-through-option 1

  param handoff-string aa

  paramspace english language en

  param max-time-vm-retry 2

  param aa-pilot 5000

  paramspace english location flash:

  param second-greeting-time 60

  param drop-through-prompt _dt_prompt.au

  param call-retry-timer 15

  param voice-mail 5555

  param max-time-call-retry 700

  param service-name callq

!

service callq flash:app-b-acd-3.0.0.2.tcl

  param queue-len 10

  param aa-hunt1 5600

  param queue-manager-debugs 1

  param number-of-hunt-grps 1

dial-peer voice 5000 pots

service aa

incoming called-number 5000

ephone-hunt 1 longest-idle

pilot 5600

list 5111, 5112

When there is incoming call, on both of the phone with ephone-dn 5111 and 5112, the message "1 call in queue" will be shown on the phone screen and you will know how many callers waiting in the call queue.

For more information:
http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/bacd/configuration/guide/40bacd.html

MGCP Signaling QoS marking

According to show mgcp, the default marking for MGCP signaling DSCP marking is AF31 (26):

MGCP media (RTP) dscp: ef, MGCP signaling dscp: af31

It can be override with the command:  mgcp ip qos dscp cs3 signaling

MGCP media (RTP) dscp: ef, MGCP signaling dscp: cs3

As a result the signaling is now marked as CS3 (24) instead of AF31 (26)

Difference between "set dscp" and "set ip dscp" under policy-map

They are more or less the same in the IPv4 world.  The only difference is, set dscp will work for IPv4 and IPv6 and set ip dscp is for IPv4 only.


pandasw02(config-pmap-c)#set ?
  dscp        Set DSCP in IP(v4) and IPv6 packets
  ip          Set IP specific values
  precedence  Set precedence in IP(v4) and IPv6 packets


pandasw02(config-pmap-c)#set ip ?
  dscp        Set IP DSCP (DiffServ CodePoint)
  precedence  Set IP precedence

Off-hook alerting configuration on UCM

This is one of the common compliance clause in RFP (especially hotel, hospital) which requires off-hook alerting, which means after the phone has been off-hook for a time that expires the "Off-hook to First Digit Timer, by default 15s", a call will be placed automatically to a predefined number, usually an operator number.  You can achieve it by creating PLAR on UCM, unchecking the "Urgent Priority" in the empty translation pattern.  Here is the example on how it can be done:

1. Create a partition called PT-FOR-PLAR (for translation pattern), PT-TO-PLAR (for destination phone)

2. Create a CSS called CSS-FOR-PLAR, and include the PT-FOR-PLAR partition.  Or simply include this partition to your existing phone CSS.  

3. Apply CSS-FOR-PLAR to the phone if you haven't done so.

4. Create another CSS called CSS-TO-PLAR, which includes the partition PT-TO-PLAR

5. Create a translation pattern with empty pattern.  The partition is PT-FOR-PLAR, and the CSS is PT-TO-PLAR.  The called party transformation is configured with the number of your destinated called party number.  Say for example my operator number is 1234, the called party transformation prefix is 1234.  Remember to "uncheck" the "Urgent Priority" so that the call will not setup immediately, instead it will wait for the time that is configured in "Off-hook to First Digit Timer".

6. Your operator DN 1234 should have partition PT-TO-PLAR or other partition in CSS-TO-PLAR

The experience is when you put your phone off-hook, after 15 sec, call will be made automatically to operator 1234.

For more information about PLAR configuration, please visit the previous post:

http://pandaeatsbamboo.blogspot.com/2008/03/configuring-plar-on-cucm.html

Comparing N5K and N7K - a very high level key features comparison

5K
- A-FEX
- VM-FEX
- FC
- Unified Ports
- EvPC

7K
- OTV
- LISP
- MPLS
- VDC

Both of them support FabricPath (N7K F1 and F2 cards), vPC, L3, FEX, etc

ASR 1000 OTV supports on IOS XE 3.5

Recently OTV is introduced to the ASR 1000 platform and is supported starting from IOS XE 3.5.  Basically the OTV support on ASR1K and N7K is similar, there are only a few difference that needs to note in this release:

- Support OTV with GETVPN on ASR1K
- No Adjacency server support, multicast WAN is required
- Support fragmentation
- Support of one Joint interface and one access interface per box

Nexus 7000 - M1 modules and F2 modules quick comparison

A fetaure comparison for quick reference:

M1	F2
Max 8 x 10GE line rate ports	Max 48 1/10GE line rate ports
Full L2 and L3 feature	Full L2 and L3 feature
Large FIB, ACL, QoS Tables	Small FIB, ACL, QoS Tables
MPLS	MPLS NOT supported
LISP	LISP NOT supported
FEX Support	FEX Support
FabricPath NOT Supported	FabricPath
FCoE NOT supported	FCoE (will support in future release)

Changing CUE license

In the lab, another common task that you will work on is to changing the CUE license.  For CME and UCM integration, different licensing file is required.

Firstly you can do a "show software license" see what license your CUE is currently using:

CUE# show software license
Installed license files:
 - voicemail_lic.sig : 25 MAILBOX LICENSE
 - ivr_lic.sig : NULL IVR LICENSE
 - port_lic.sig : 8 PORT BASE LICENSE


Core:
 - Application mode: CCM
 - Total usable system ports: 8


Voicemail/Auto Attendant:
 - Max system mailbox capacity time: 18000
 - Default # of general delivery mailboxes: 10
 - Default # of personal mailboxes: 25


 - Max # of configurable mailboxes: 35


Interactive Voice Response:
 - Max # of IVR sessions: Not Available


Languages:
 - Max installed languages: 5
 - Max enabled languages: 5

According to the output, my CUE is using UCM license and I wanna change it to CME.  You can place your license file in your FTP server and install it on CUE:

CUE# software install clean url ftp://192.168.20.16/cue-vm-license_25mbx_cme_7.0.1.pkg username panda password eatsbamboo




WARNING:: This command will install the necessary software to
WARNING:: complete a clean install.  It is recommended that a backup be done
WARNING:: before installing software.


Would you like to continue? [n]y


Downloading ftp cue-vm-license_25mbx_cme_7.0.1.pkg
Bytes downloaded :  5299


Validating package signature ... done
compatibility mode
Validating installed manifests ...............complete.
The system will be brought to offline state for a brief period
and will be brought back to online state automatically
No work order produced.
The system is back in online state
55296+0 records in
108+0 records out
Size of buff is: 65536
65536 bytes written
Parsing...
25 MAILBOX LICENSE
Parsing...
NULL IVR LICENSE
Parsing...
8 PORT BASE LICENSE
Core:
 - Total usable system ports: 8


/tmp/license/voicemail_lic.sig
/tmp/license/ivr_lic.sig
/tmp/license/port_lic.sig


 Important:: A Reload is required in order for the new License to take effect.

It is changed to CME licensing file successfully, reboot the CUE module for the new license to take effect.

CME cBarge - Failed to setup barge

Just labbing on the CME cBarge feature and got the error message "Failed to setup Barge" on the phone display.  The reason in my case is I have forgotten to create the ad-hoc conference ephone-dn.  Let us quickly walkthrough the steps that are needed to config cBarge on CME:

1. Create Conferencing DSP farm profile

dspfarm profile 1 conference
codec g711ulaw
codec g711alaw
codec g729ar8
codec g729abr8
codec g729r8
codec g729br8
maximum sessions 2
associate application SCCP

2. DSP farm profile SCCP configuration

sccp local GigabitEthernet0/0
sccp ccm 192.168.20.254 identifier 1 priority 1 version 7.0
sccp
!
sccp ccm group 1
associate ccm 1 priority 1
associate profile 1 register CFB

3. sdspfarm configuration on CME under telephony-service

telephony-service
sdspfarm units 2
sdspfarm tag 1 CFB
no privacy
conference hardware

4. Create ephone template with cBarge softkey in remote-in-use state

ephone-template  1
softkeys remote-in-use  CBarge Newcall

5. Sample ephone configuration

ephone  1
privacy off
privacy-button
device-security-mode none
mac-address 0021.5555.5555
ephone-template 1
type 7965
button  1:1 2:3
!
!
!
ephone  2
privacy off
privacy-button
device-security-mode none
mac-address 0026.2222.2222
ephone-template 1
type 7975
button  1:2 2:3

6. Create shared line ephone-dn and ad-hoc conference ephone-dn

ephone-dn  3  octo-line
number 5003
!
!
ephone-dn  4  octo-line
number A123
conference ad-hoc

After I've created the ephone-dn 4 for ad-hoc conferencing, cBarge is setup successfully without the error any more!

UCM + CUE integration example step-by-step

1. Create CUE End User on CUE

conf t

username boss create

username sec create

username boss phonenumber 1001

username sec phonenumber 1002

exit

username boss pin 12345

username sec pin 12345

2. Config JTAPI subsystem on CUE

ccn subsystem jtapi

ctiport 1111 1112 1113 1114

ccm-manager address 192.168.20.2 192.168.20.1

ccm-manager username panda password eatsbamboo

end subsystem

3. Config JTAPI number on CUE

ccn trigger jtapi phonenumber 1110

application voicemail

enabled

maxsessions 4

end trigger

3. Create voice mailbox on CUE

voicemail mailbox owner boss

enable

voicemail mailbox owner sec

enable

4. Create UCM End User boss and sec on UCM

5. Create Voicemail Pilot 1110 on UCM

6. Create Voicemail Profile on UCM

7. Assign Voicemail Profile to DN of boss and sec

8. Create CTI Route Point 1110, same DN as voicemail pilot

9. Create CTI ports 1111, 1112, 1113 and 1114

10. Create application users panda and assign CTI route point and ports to it

Note: No MWI number is needed to create on UCM and CUE