Live Record (Cisco Unity Express) Configuration, Debugging and Verification
Live-record is a great little feature available when integrating CUE and CME; a feature that does not exist natively with CUCM. As long as the "Live Record" softkey button is assigned to a users' ephone, and the user is a valid CUE user with a mailbox, they will be able to interactively record voice conversations. The recorded conversations are stored as a message in the users mailbox. CUE periodically beeps to alert participants that the call is still being recording - this is required under certain national legislations (such as Australia).
For live-record to work correctly, conferencing must be configured and working correclty. Verify that ad hoc conferences work before proceeding with live-record. The process to enable and use Live Record is:
- Ensure ad hoc conferencing is configured and works correctly (check here for instructions on configuring conferencing)
- Permit any ephones that require live-record to use the feature by creating an ephone-template with the live record button configured, and assign the template to ephones
- Configure a live-record pilot number under the CME telephony-service, and on the CUE module itself
- Create an ephone-dn with the live record pilot number, with call forwarded all set to the voicemail pilot
Users initiating conferences by simply pressing the "Live Record" button during a conversation. Its as simple as that!
First, let's review the configuration requirements; we'll ignore the conferencing configuration. Configuration for conferencing is covered here. The following configuration uses a Live-Record number of 8889 in a CUE voicemail system setup on pilot 8888.
======== CME ========
ephone-template 1
 softkeys connected LiveRcd Confrn Hold Park Trnsfer TrnsfVM
!
ephone 1
 ephone-template 1
!
ephone 2
 ephone-template 1
!
dial-peer voice 8888 voip
 destination-pattern 8888
 session protocol sipv2
 session target ipv4:192.168.255.98
 dtmf-relay sip-notify
 codec g711ulaw
 no vad
!
telephony-service
 live-record 8889
 voicemail 8888
!
ephone-dn 100
 number 8889
 call-forward all 8888
======== CUE ========
voicemail live-record beep duration 1000
voicemail live-record pilot-number 8889
Verify on CUE that Live Record is correctly configured:
se-192-168-255-98# show voicemail live-record
Status: enabled
Pilot number: 8889
Conversation beep settings
   Beep Duration: 1000 milliseconds
   Beep Interval: 15 seconds
Now, verify the output from "debug ephone detail" when live-record is initiated. Observe that, apart from the numbers (which we know from the above configuration), there is nothing to indicate a live-record session. From CME's perspective, this is simply an ad-hoc conference:
Jan 10 09:48:43.819: ephone-2[1/3]:SkinnyTryCall to 8889 instance 1 start at 0 secondary 0
SkinnyTryCall to 8889 instance 1 match DN 100
Jan 10 09:48:43.819: ephone-2[1/3]:SkinnyTryCall to 8889 instance 2 start at 101 secondary 0
Jan 10 09:48:43.831: ephone_update_redirect_number: orig=8889 cfn=8888 cgn=7002
Jan 10 09:48:44.223: ephone-2[3]:OpenReceive DN 2 chan 2 codec 4:G711Ulaw64k duration 20 ms bytes 160
Jan 10 09:48:44.223: ephone-2[1/3][SEP001B53B8AFB9]:SkinnyDisplayCallInfo callingNumber=7002
Jan 10 09:48:44.223: ephone-2[1/3][SEP001B53B8AFB9]:SkinnyDisplayCallInfo calledNumber=8888
Jan 10 09:48:44.223: ephone-2[1/3][SEP001B53B8AFB9]:SkinnyDisplayCallInfo called number 8888 name
Jan 10 09:48:44.223: ephone-2[3]::callingNumber 7002
Jan 10 09:48:44.227: ephone-2[3]::callingParty 7002
Jan 10 09:48:44.231: SkinnyGetCallState for DN 2 chan 2 CONNECTED
Jan 10 09:48:46.179: ephone-2[1/3]:SkinnyTryCall to 8888 instance 1 start at 0 secondary 0
Jan 10 09:48:46.183: called DN -1 chan 1, calling DN -1 chan 1 phone 2 s2s:0
Jan 10 09:48:46.183: ephone-2[1/3][SEP001B53B8AFB9]:Adding/Returning DN 2 chan 1 to conference
Jan 10 09:48:46.183: SkinnyGetCallState for DN 2 chan 1 HOLD
Jan 10 09:48:46.183: called DN -1 chan 1, calling DN 3 chan 1 phone -1 incoming s2s:1
Jan 10 09:48:46.183: SkinnyGetCallState for DN 2 chan 1 HOLD
Jan 10 09:48:46.183: called DN -1 chan 1, calling DN 3 chan 1 phone -1 incoming s2s:1
Jan 10 09:48:46.183: SkinnyGetCallState for DN 2 chan 2 CONNECTED
Jan 10 09:48:46.183: called DN -1 chan 1, calling DN -1 chan 1 phone 2 s2s:0
Jan 10 09:48:46.183: ephone-2[1/3]:SkinnyAddDnToConference: (dn=2 chan=1 state=9) (conf_dn=2 conf_chan=2 state=4)
Jan 10 09:48:46.183: SkinnyGetCallState for DN 2 chan 2 CONNECTED
Confirm that a conference bridge is now in use on CME; the voice-mail pilot is one member of the conference (we'll see why a little further down):
CME#sh telephony-service conference hardware detail
Conference Type Active Max Peak Master MasterPhone Last
cur(initial)
=======================================================================================
A101 Ad-hoc 3 8 3 7002 Marketi 2 ( 2) 8888
Conference parties (number:phone)
    8888
    7003 IT:3
    7002 Marketing:2
Now, confirm that a voice call is now active on CUE; you can see both the called number, the last redirected number (i.e. the Live Record number) and the initiating party.
se-192-168-255-98# show ccn call application
Active Call Details for Subsystem : SIP
-----------------------------------------
 **** Details for route ID : 8888 ****
 -------------------------------------
    ** Active Port #1: Call and Media info **
    ------------------------------------------
Port ID : 8
Port Impl ID : 16912
Port State : IN_USE
Call Id : 13
Call Impl Id : 793A154E-DE3111DD-80A9F350-4482156F@192.168.255.99
Call State : CALL_ANSWERED
Call active time(in seconds) : 17
Application Associated : voicemail
Application Task Id : 23000000010
Called Number : 8888
Dialed Number :
Calling Number : 7002
ANI :
DNIS :
CLID : sip:7002@192.168.255.99
Arrival Type : FORWARD_ALL
Last Redirected Number : 8889
Original Called Number : 8889
Original Dialed Number :
Media Id : 2
Media State : IN_USE
Media Destination Address : 192.168.255.99
Media Destination Port : 18092
Destination Size : 30
Destination Payload : G711ULAW64K
Media Source Address : 192.168.255.98
Media Source Port : 16912
Source Size : 30
Source Payload : G711ULAW64K
Finally, confirm that the message has been delivered to the initating party - i.e. Marketing on extension 7002.
se-192-168-255-98# show user detail username Marketing
Nickname: Marketing
Phone: 7002
se-192-168-255-98# show voicemail mailboxes
OWNER MSGS NEW SAVE DEL BCST FUTR FAX MSGTIME MBXSIZE USED
"Sales" 0 0 0 0 0 0 0 0 10285 0 %
"Marketing" 6 6 0 0 0 0 0 72 10285 1 %
