Recording Calls Study

Deploying and
troubleshooting call
recording infrastructure
Vladimir Savostin, Technical Leader, CX
BRKCOL-3672
Cisco Webex Teams
Questions?
Use Cisco Webex Teams to chat
with the speaker after the session
How
1 Find this session in the Cisco Events Mobile App
2 Click “Join the Discussion”
3 Install Webex Teams or go directly to the team space
4 Enter messages/questions in the team space
BRKCOL-3672 © 2020 Cisco and/or its affiliates. All rights reserved. Cisco Public 3
Agenda
• Introduction
• Phone-based Call Recording with BiB
• GW-based Call Recording via XMF
• Call Recording redundancy with Media-Proxy
• Conclusion
Introduction
Call recording infrastructure
What’s in scope for this session
• CUCM-based, UC centric
• Voice-only recording (compliance, analytics, review)
• Secure and non-secure calls
• Recording software agnostic
• Design, deployment, troubleshooting
Existing solutions
• Server-based recording solutions

• SPAN
• Agent Desktop
• CUCM-controlled recording solutions

• Built-In Bridge (BiB) in IP Phones
• eXtended Media Forking (XMF) on Gateway
• Media forking with CUBE

• Open Recording Architecture
• SIPREC compliance
• Media-Proxy
Call recording terminology
Network-based recording solutions
• Calling Party
• Person initiating the call - customer
• Called Party
• Person answering the call - agent
• Recorder
• Software capturing and storing conversation media
• Built-in Bridge (BiB)

• Media forking element within IP Phone
• XMF-enabled Gateway
• Voice GW or CUBE with XMF-based media forking enabled
• Media-Proxy (MPS)
• CUBE with MPS feature configured
• Recording Media Source / Anchoring point

• IP Phone, Gateway or Media-Proxy used to copy and forward (fork) media
Features timeline XE16.10.1
15.6(1)T CUCM 12.5
XE3.17 CUBE Media-
CUCM 10.0 SIPREC Proxy
GW-Based Compliance Recording of
15.3(3)M Recording Authenticated
Calls
15.3(1)T XE3.10
XE3.8 UC GW
CUCM 9.0 Services, XMF
CUBE Media
Softkey and Forking, ORA
CUCM 8.5 PLK support
SIP Header
CUCM 8.0
Enhancements
Secure
CUCM 6.0
Recording
Basic Call
Recording
Jun 07 Feb 10 Feb 11 Jul 12 Oct 12 Jul 13 Dec 13 Jul 17 Dec 18
Supported devices
https://developer.cisco.com/site/uc-manager-sip/documents/supported/
Supported devices
• Navigate to Cisco Unified Reporting ->
• Open System Reports ->
• Run ‘Unified CM Phone Feature List’
• Select Feature ‘Record’
• Click ‘Submit’ to get report
Phone-based Call
Recording with BiB
Phone-based call recording
Built-in Bridge fundamentals
Remote User
Spkr Decoder
Encoder
Call Recording
Mixer Encoder
Mic
Call Monitoring
Built-in Bridge fundamentals
When Endpoint is registered CUCM creates BiB Device with Unique Name/DN
00607872.013 |14:37:40.642 |Created | SIPBuiltInBridgeControl(1,100,86,4) |SIPStationD(1,100,76,7) |

|NumOfCurrentInstances: 2
[…]
00607909.000 |14:37:40.644 |SdlSig |DaRegisterDn |wait |Da(1,100,216,1) |SIPBuiltInBridgeControl(1,100,86,4)
|1,100,14,599.6^10.229.68.143^SEPC40ACB4C5A48 |[R:N-H:0,N:30,L:2,V:0,Z:0,D:0] Partition=
Number=b0018604001 DialPlan= PropagatePattern PatternType=0 SsType=0 SsKey=0 SsNotifyType=0
DigitDiscardingInstructions=0 CallableEndPointName=b0018604001:
[…]
00607909.001 |14:37:40.644 |AppInfo |Digit analysis: add to the localRegistrations /b0018604001 , PID: 1,86,4;
patternUsage = [0]
00607909.004 |14:37:40.644 |AppInfo |Digit analysis: Add local pattern /b0018604001 , PID: 1,86,4
[…]
00607911.000 |14:37:40.644 |SdlSig |DeviceStart |initialized
|DeviceManager(1,100,210,1) |SIPBuiltInBridgeControl(1,100,86,4)
|1,100,14,599.6^10.229.68.143^SEPC40ACB4C5A48 |[T:N-H:0,N:0,L:0,V:0,Z:0,D:0] Name=b0018604001
Cepn=b0018604001: Type=537 ccmType=1 ProtocolName=BIB
Device support for Built-in Bridge
• Cisco Unified Reporting ->
• Open System Reports ->
• Run ‘Unified CM Phone Feature List’
• Select Feature ‘Built In Bridge’
• Click ‘Submit’ to get report
Architecture
Calling Party Voice

Called Party Voice
TAPI/JTAPI
Call Signaling SIP/SCCP
CTI/JTAPI
Call Recording
Control App
SIP/SCCP
BiB
PSTN
Voice GW IP Phone
Recorder
Call recording metadata
x-nearend: call with outgoing
IP Phone media
From: <sip:30107@10.62.150.183; x-farend: call with incoming
x-nearend/x-farend; IP Phone media
x-refci=75831761;
x-nearendclusterid=hulk; Call IDs for incoming and
x-nearenddevice=SEPC40ACB4C5A48; outgoing call legs
x-nearendaddr=30107;
x-farendrefci=75831760; Cluster IDs for incoming and
x-farendclusterid=hulk; outgoing call legs
x-farenddevice=DE-SME-1Z;
x-farendaddr=231110; Calling and Called numbers
tag=6698668~5f282315-ee6f
Calling and Called Device
names
Recording modes
• Automatic recording
• Selective recording
PLK Softkey Service URL
Call modification behavior
• Media for recording calls is torn down during call modifications
MOH Hold Disconnect
BiB
IP Phone A IP Phone B
Recorder
• After resume or transfer media is re-stablished with same codec
Resume Connect
with same codec
BiB
Recorder
Known issues – Unidirectional streams on the Recorder
CUCM load balancing calls in RG with Circular (default) distribution algorithm
CallRec Route List CallRec Route List

CallRec Route Group (Circular) CallRec Route Group (Top Down)
Recorder 1 Recorder 1
Redundancy without load balancing
Sub 1 Rec 1
Recording RL
DC 1 Recording RG1
DC 2 Rec1
Sub 2 Rec 2
Recording RG2
Rec 2
Redundancy with load balancing
CallRec Route List 1 CallRec Route List 2

CallRec Route Group 1 CallRec Route Group 2
CallRec Route Group 2 CallRec Route Group 1

Known issues - Call Recording via Service URL in EMCC scenario
Visiting Cluster Home Cluster
HTTP POST /CGI/Execute

SEP2C31246A03C5
IP Phone Recorder
http://10.2.4.1/ccmcip/authenticate.jsp?UserID=rec&Password=xxx&devicename=SEP2C31246A03C5
Known issues - Call Recording via Service URL in EMCC scenario
Visiting Cluster Home Cluster
Proxy Server
Recorder
IP Phone Enhancement request

SEP2C31246A03C5 CSCvo61550 Feature for Phone Authentication Service in EMCC scenario
Known issues - Built-in Bridge slow memory leak
When IP Phone is registered CUCM creates BiB Device with Unique Name/Pattern
[…]
After IP Phone reset BiB

[…]
Known issues - Built-in Bridge slow memory leak
Modify CallManager Service Parameter "Dialing Forest Dump Enabled" under the
Clusterwide Parameters (System - General) section, and set it to True.
**##*02 - terse/verbose toggle
**##*04 - dump patterns
|Pattern=c00112101001 |Pattern=b00105701008 |Pattern=b00105701021

|Pattern=b0017201001 |Pattern=b00105701012 |Pattern=b00105701025
|Pattern=b00105701006 |Pattern=b00105701019
|Pattern=b00105701007 |Pattern=b00105701020
Known issues – Calls InProgress spiking
• Always keep recorded devices in sync b/w CUCM and Recorder
Calls InProgress
11:20:17 > INVITE
400
11:20:17 < 100 Trying 350
11:24:43 < 200 OK 300
250
11:24:43 > CANCEL
200
150
100
50
0
11:20 11:21 11:22 11:23 11:24 11:25 11:26 11:27 11:28 11:29 11:30 11:31 11:32 11:33 11:34 11:35 11:36 11:37
Known issues - Transcoder engagement
G.722 G.722
BiB
Recorder
MOH Disconnect
Transfer G.711
BiB
Recorder
Known issues - Transcoder engagement
Connect
with same codec
G.729
BiB
IP Phone C G.729 G.722

IP Phone B
Recorder
Region A Region B
Transcoder
Known issues – TRP + Transcoder = TRP Port leak
XCoder OpenLogicalChannel/StartMediaTransmission
Calling Party Voice
Called Party Voice
Secure Zone
TRP
G.711
G.722
G.711, G.729
BiB
PSTN
CUBE
IP Phone
Recorder
MTP-TRP# show sccp connections | include inac
sess_id conn_id type state local_ip local_port remote_port remote_ip
43927109 33604999 mtp inactive UNKNOWN 25330 0 UNKNOWN
Recorder SIP Trunk best practices
• Enable OPTIONS Ping in SIP Profile
• Use Transport TCP in SIP Trunk Security Profile
• Consider Early/Delayed Offer mode
GW-based Call
Recording via XMF
Gateway-based call recording via XMF
Use cases
• Unsupported BiB devices (Jabber for iPhone/Android)

• Unsupported BiB call flows (SNR, E&C, Mobile Agent)
• Centralized SIP trunks
• Remote site bandwidth considerations
Architecture
Calling Party Voice

Called Party Voice
TAPI/JTAPI
CTI/JTAPI
Call Recording
HTTP/XMF Control App
SIP/SCCP
PSTN
Voice GW IP Phone
Recorder
UC WSAPI – Unified Communications Web Services API
UC WSAPI
XCC XSVC XMF XCDR
eXtended eXtended eXtended eXtended

Call Control Serviceability Media Forking CDR
eXtended Media Forking Interface
XMF Provider http://<CUCM>:8090/ucm_xmf XMF Application
XMF connection
SOAP over HTTP

Voice GW CUCM
http://<gateway>:8090/cisco_xmf
XMF Provider
act as a server, monitor calls and deliver notifications of call states,
triggers media forking
XMF Application
acts as client, registers with provider, subscribes for notifications,
requests for media forking
eXtended Media Forking Interface
XMF Provider XMF Application
XMF connection
SOAP over HTTP

Voice GW CUCM
XMF Connection abstracts states of the call at the endpoint or trunk:

IDLE - This state is the initial state for all new connections
ADDRESS_COLLECT - gateway collects digits from the endpoint
CALL_DELIVERY – selecting route for call
ALERTING – remote side notified of the call
CONNECTED – call is established
DISCONNECTED – call is terminated
Basic XMF Provider Configuration
XMF Provider
1. Enable HTTP on IOS
ip http server
ip http max-connections 100
2. Enable the API on IOS

uc wsapi
source-address [Gateway_IP_Address]
probing interval negative 10
probing interval keepalive 180
3. Enable XMF service within the API

provider xmf
remote-url 1 http://<CUCM IP/FQDN>:8090/ucm_xmf ! Sub1
remote-url 2 http://<CUCM IP/FQDN>:8090/ucm_xmf ! Sub2
XMF Provider
MS-P1-3900#sh control-plane host open-ports | i 8090

MS-P1-3900#
MS-P1-3900(config)# uc wsapi
MS-P1-3900(config-uc-wsapi)# source-address 10.48.52.170
MS-P1-3900(config-wsapi-xmf)# provider xmf
MS-P1-3900#sh control-plane host open-ports | i 8090

tcp *:8090 *:0 HTTP CORE LISTEN
tcp *:8090 *:0 HTTP CORE LISTEN
XMF Provider
HTTP Server settings Enables HTTP Server
ip http server Set maximum number

of connections
ip http max-connection 100
ip http timeout-policy idle 600 life 86400 requests 86400
HTTP Client settings Define timeouts:

- Idle
http client connection persistent - absolute time
- max number of requests
http client connection idle timeout 600
Allow multiple requests
to be multiplexed over
Number of seconds until the same connection
client will close the
connection if it’s idle
Set maximum number of failed XMF Provider
UC WSAPI settings message delivery before
unregistering Application
uc wsapi
message-exchange max-failures 1
probing max-failures 3 Set maximum number of
failed probes before
probing interval keepalive 120 unregistering Application
probing interval negative 10
Set interval between

How often we are probing messages
sending probes if
there is no reply
XMF Provider
CUCM Gateway
In 18,5 seconds CUCM will terminate the connection
XMF Provider
Gateway CUCM
In 18,5 seconds CUCM will terminate the connection
Basic XMF Application Configuration
XMF Application
XMF Registration process
RequestXmfRegister
CREATED/DISCONNECTED XMF Application
XMF Application
Registration
ResponseXmfRegister
CUCM
XMF Provider
SolicitXmfProbing
XMF Provider
Voice GW ResponseXmfProbing Keepalives
XMF Registration process – GW debugs
Jan 12 05:40:16.166: //WSAPI/XMF/INCOMING_MSG:: msg_type[6] RequestXmfRegister

Jan 12 05:40:16.166: transactionID Cisco:UCM:CayugaIf:3:1
connectionEventsFilter: CREATED|DISCONNECTED
mediaEventsFilter:
Jan 12 05:40:16.166: app url http://10.62.150.183:8090/ucm_xmf
Jan 12 05:40:16.166: app name Unified CM 11.5.1.14900-11
Jan 12 05:40:16.166: prov url http://10.62.150.156:8090/xmf
Jan 12 05:40:16.166: //WSAPI//OUTGOING_RESPONSE:: type 8 ResponseXmfRegister:

Jan 12 05:40:16.166: registrationID CCDEDF16:XMF:Unified CM 11.5.1.14900-11:1
Jan 12 05:40:16.166: providerStatus 1ws
XMF Registration process – CUCM traces
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
<soapenv:Body>
<RequestXmfRegister xmlns="http://www.cisco.com/schema/cisco_xmf/v1_0">
<applicationData>
<name>Unified CM 11.5.1.14900-11</name>
<url>http://10.62.150.183:8090/ucm_xmf</url>
</applicationData>
<connectionEventsFilter>CREATED DISCONNECTED </connectionEventsFilter>
<mediaEventsFilter/>
<msgHeader>
<transactionID>Cisco:UCM:CayugaIf:2:2</transactionID>
</msgHeader>
<providerData>
<url>http://10.62.150.156:8090/xmf</url>
</providerData>
</RequestXmfRegister>
</soapenv:Body>
</soapenv:Envelope>
XMF Registration process – CUCM traces

<SOAP:Envelope xmlns:SOAP="http://www.w3.org/2003/05/soap-envelope">
<SOAP:Body>
<ResponseXmfRegister xmlns="http://www.cisco.com/schema/cisco_xmf/v1_0">
<msgHeader>
<transactionID>Cisco:UCM:CayugaIf:3:1</transactionID>
<registrationID>CCDEDF16:XMF:Unified CM 11.5.1.14900-11:1</registrationID>
</msgHeader>
<providerStatus>IN_SERVICE</providerStatus>
</ResponseXmfRegister>
</SOAP:Body>
</SOAP:Envelope>
XMF Registration process – verify registrations
csr1000v#sh wsapi registration xmf
Provider XMF
=====================================================
registration index: 1
id: CCDEDF16:XMF:Unified CM 11.5.1.14900-11:1
appUrl:http://10.62.150.183:8090/ucm_xmf
appName: Unified CM 11.5.1.14900-11
provUrl: http://10.62.150.156:8090/xmf
prober state: STEADY
connEventsFilter: CREATED|DISCONNECTED
mediaEventsFilter:
registration index: 2
id: CCDEDF55:XMF:Unified CM 11.5.1.14900-11:2
appUrl:http://10.62.150.184:8090/ucm_xmf
appName: Unified CM 11.5.1.14900-11
provUrl: http://10.62.150.156:8090/xmf
prober state: STEADY
connEventsFilter: CREATED|DISCONNECTED
mediaEventsFilter:
Recording call walk-through
GW is sending XMF message for the First leg (Near End):
Jan 12 14:52:39.252: //WSAPI/XMF/OUTGOING_MESSAGE:: msg_type[21] NotifyXmfConnectionData
Jan 12 14:52:39.252: registrationID 22DCCD6C:XMF:Unified CM 11.5.1.14900-11:2
Jan 12 14:52:39.252: callID: 13
Jan 12 14:52:39.252: connID: 15762
Jan 12 14:52:39.252: guid: 0x56B44800-0x00010000-0x00000037-0x832E300A
Jan 12 14:52:39.252: callingAddrData:
Jan 12 14:52:39.252: addr 30120
Jan 12 14:52:39.252: calledAddrData:
Jan 12 14:52:39.252: addr 30107
SIP INVITE
200OK
Call Setup
PSTN Call Estab
Voice GW IP Phone
Recorder
GW is sending XMF message for the Second leg (Far End):
Jan 12 14:52:39.252: //WSAPI/XMF/OUTGOING_MESSAGE:: msg_type[21] NotifyXmfConnectionData
Jan 12 14:52:39.252: callID: 13
Jan 12 14:52:39.252: connID: 15763
Jan 12 14:52:39.252: guid: 0x56B44800-0x00010000-0x00000037-0x832E300A
Jan 12 14:52:39.252: callingAddrData:
Jan 12 14:52:39.252: addr 30120
Jan 12 14:52:39.252: calledAddrData:
Jan 12 14:52:39.252: addr 30107
SIP INVITE
200OK
Call Setup
PSTN Call Estab
Voice GW IP Phone
Recorder
CUCM is sending Media Forking request for connection:
Jan 12 14:52:41.728: //WSAPI/XMF/INCOMING_MSG:: msg_type[13] RequestXmfConnectionMediaForking
Jan 12 14:52:41.728: callID: 13
Jan 12 14:52:41.728: connID: 17464
Jan 12 14:52:41.728: nearEndAddr:
Jan 12 14:52:41.728: ipv4 10.48.46.129
Jan 12 14:52:41.728: port 50752
Jan 12 14:52:41.728: tone 0
Jan 12 14:52:41.728: farEndAddr:
Jan 12 14:52:41.728: ipv4 10.48.46.129
SIP INVITE
Jan 12 14:52:41.728: port 50754
200OK
Jan 12 14:52:41.728: tone 0
Jan 12 14:52:41.728: preserve: 1
Call Setup
PSTN Call Estab
Voice GW
IP Phone
Recorder
RequestXmfConnectionMediaForking message attributes:
Jan 12 14:52:41.728: nearEndAddr:
Jan 12 14:52:41.728: tone 0
Jan 12 14:52:41.728: farEndAddr:
Jan 12 14:52:41.728: tone 0
SIP INVITE
200OK
Call Setup
PSTN Call Estab
Voice GW
IP Phone
Recorder
XMF Call correlation
22:09:23.327 |AppInfo |CayugaInterface - processInd - Parsed
Msg{MessageType=MSG_NOTIFY_XMF_CONNECTION_DATA RegId=467428:XMF:Unified CM 11.5.1.14900-11 :19
TransId=6E4590:293 ProbeRegStatus=false CallId=18 ConnId=291 NotificationEventType = CREATED guid =
3393161472-0000065536-0000000117-2710978058 IntfType = CONN_SIP CallDirection= INCOMING}
22:09:23.416 |AppInfo |CayugaInterface - processInd - Parsed

Msg{MessageType=MSG_NOTIFY_XMF_CONNECTION_DATA RegId=467428:XMF:Unified CM 11.5.1.14900-11:19
TransId=6E4598:295 ProbeRegStatus=false CallId=18 ConnId=292 NotificationEventType = CREATED guid =
3393161472-0000065536-0000000117-2710978058 IntfType = CONN_SIP CallDirection= OUTGOING}
22:09:24.787 |AppInfo |SIPTcp - wait_SdlReadRsp: Incoming SIP TCP message from 10.48.52.170 on port 30658
index 292:
INVITE sip:730120@10.62.150.183:5061 SIP/2.0
Via: SIP/2.0/TLS 10.48.52.170:5061;branch=z9hG4bK291DB
From: <sip:1001@10.48.52.170>;tag=6E4594-1B89
To: <sip:730120@10.62.150.183>
Date: Fri, 24 Jan 2020 20:32:48 GMT
Call-ID: 84CC5B16-3E1F11EA-8181C2E2-B6CA21F4@10.48.52.170
Cisco-Guid: 3393161472-0000065536-0000000117-2710978058
Supported: 100rel,timer,resource-priority,replaces,sdp-anat,X-cisco-srtp-fallback
Inter-cluster recording information pass-through - configuration
SME Cluster
Cisco recording
QSIG
Inter-cluster recording information pass-through – QSIG APDU
07787405.004 |16:32:48.010 |AppInfo |Recording::- (0000009) 07787405.012 |16:32:48.010 |AppInfo |CCQSIGASN -
-encodeRecordingAPDU- apduType=[1]. RawByteOutput:AA068001 00820100
07787405.005 |16:32:48.010 |AppInfo |RCD_Qsig 07787405.013 |16:32:48.013 |AppInfo |RECORDQSIGASN -
-- RecordingQsigInfo -- StructuredInput:value RecordingStart ::= invoke :
mApdutype = 1 {
mInvokeID = 6 invokeID 6,
mRecordingRequestor = 7 operationValue localValue : 60,
mPlayToneDirection = 3 argument
mReqDeviceType = 0 {
mReqRefCI = 29601406 pilotNumber '3735303031'H,
mfrkRefCI =0 requesterDN '32393031'H,
mCtiEventType = 0 requestorType 7,
mCause = 0 toneDirection 3,
mRecorderDn = 75001 requestorDevType 0,
mReqDeviceName =SEPD824BDBA7134 requestorDevName '534550443832344244424137313334'H,
mReqClusterName = cucm193 requestorClusterID '6375636D313933'H,
mRecorderDevName = requestorRefCI 29601406,
mRecorderPartition = frkDevPosition 2,
mfrkDeviceName = restartRecording FALSE,
mfrkClusterID = locale 64,
[…] transactionID 0
mLocale = 64 }
-- End -- }
Inter-cluster recording information pass-through – missing Recording Info
07783828.000 |16:08:29.673 |SdlSig |SsCallInfoRes |await_callInfo_res |Recording(1,100,162,8)

|RecordManager(1,100,161,1) |1,100,255,1.87^10.62.150.183^* |[R:N-H:0,N:0,L:0,V:0,Z:0,D:0] Type=16777246
ssKey=8 sideASsNode=1 sideASs=29601403 AHold=F sideAPSS=a19ec8ca-74d8-71c4-a002-156c3d887214 sideACMDevType=6
sideAEncodingType=0 sideAQsigEncodingType=0 sideAIsPreferAltScript=F sideAVideoCapable=F isSideAPSTN=F isSideBPSTN=F isSideB
IME=F sideBNode=1 sideBSs=29601404 BHold=F sideBPSS= sideBCMDevType=4 sideBEncodingType=1 sideBQsigEncodingType=10
sideBIsPreferAltScript=T sideBVideoCapable=F cgPart= cgPat= cgTags= cgValues= pretransCgp:tn=0npi=0ti=1nd=1001pi=0si3
rnName=locale: 1 Name: UnicodeName: pi: 0 LRNumVMbox= LRNumberVMPN= LRVMPCss= LRRFR=15 LRCause=0 callState=5
[…]
5060>OrigPort=0pi=0si1 param=;+multiple-codecs-in-ans isParamSet=T' sideBCcContactHeaderInfo='
uri=ti=1User=Host=Port=0PassWord=Madder=Transport=4mDisplayName=RawUrl=<sip:aa55d7fb-8c05-f627-5254-
ff7ab5a022c7@10.229.68.145:51364;transport=tcp>OrigPort=0pi=0si1 isParamSet=T' callingDeviceNodeId=1 calledDeviceNodeId=1
sideABib=0 sideBBib=0 sideARecQsigApduSupport=T sideBRecQsigApduSupport=F
sideAMobilePartyNumber:pi=0si1 callingMobileDeviceName: calledMobileDeviceName: sideBMobilePartyNumber:pi=0si1
sideAGuid:E2Epcol=1E2EcallID=DF9F83800001000000000048B7963E0A sideBGuid:E2Epcol=0E2EcallID= isMultiForkingEnabled=F
CAL={v=-1, m=-1, tDev=F, res=F, devType=0} CAL={v=-1, m=-1, tDev=F, res=F, devType=0}sideAnp=FsideBnp=F connBeforeA
NN=F External Presentation Info [ pi=0si1locale: 1 Name: UnicodeName: pi: 0 mIsCallExternal=F ] External Presentation Info [ pi=0si1locale:
1 Name: UnicodeName: pi: 0 mIsCallExternal=F ] Session-
ID:8d972ce127862077450a4f236b3a3ba0;remote=df3bbb91d396525193611d227aa12486
Inter-cluster recording information pass-through – no Rerouting CSS
07787452.007 |16:32:48.146 |AppInfo |RECORDQSIGASN -
StructuredOutput:value RecordingStart ::= retError :
{
invokeID 6,
errorValue localValue : 6160,
argument
{
eventType 27,
recorderDeviceName ''H,
recorderPartition ''H,
frkDeviceName ''H,
frkClusterID '48554C4B'H,
frkRefCI 0,
frkDeviceGUID '3434413841383830303030313030303030 ...'H,
cCcause 1114112,
recordingFailurecause 1,
transactionID 0
}
}
07787452.009 |16:32:48.146 |AppInfo |Recording::- (0000009) -sendCTIErrorWithQsigRes: causeTag=[1]. ssCause[1114112]
07787452.011 |16:32:48.147 |AppInfo |GenAlarm: AlarmName = RecordingCallSetupFail, subFac =
CALLMANAGERKeyParam = , severity = 3, AlarmMsg = RecordedDeviceName : SEPD824BDBA7134
Deployment models – centralized call recording
SME Cluster
Cisco
Voice GW recording IP Phones
QSIG
Central Recorder Branch Recorder
Deployment models – distributed call recording
SME Cluster
Cisco
QSIG
Deployment models – optimized call recording
SME Cluster
Cisco
QSIG
Deployment models – optimized call recording
<Request xmlns="urn:oasis:names:tc:xacml:2.0:context:schema:os">
<Attribute AttributeId="urn:Cisco:uc:1.0:callingnumber">
<AttributeValue>b0018601001</AttributeValue></Attribute>
<Attribute AttributeId="urn:Cisco:uc:1.0:callednumber">
<AttributeValue>75001</AttributeValue></Attribute>
<Attribute AttributeId="urn:Cisco:uc:1.0:transformedcgpn">
IP Phones <AttributeValue>b0018601001</AttributeValue></Attribute>
<Attribute AttributeId="urn:Cisco:uc:1.0:transformedcdpn">
<AttributeValue>75001</AttributeValue></Attribute>
<Attribute AttributeId="urn:Cisco:uc:1.0:callingdevicename">
<AttributeValue>SEPC40ACB4C5A48</AttributeValue></Attribute>
75001 75002
<Response><Result><Decision>Permit</Decision>
<Obligations><Obligation FulfilOn="Permit" obligationId="divert.simple">
<AttributeAssignment AttributeId="Policy:divert.simple">
<AttributeValue>
<cixml version="1.0”>
<divert><destination>75002</destination></divert>
</cixml>
Branch </AttributeValue></AttributeAssignment>
Central </Obligation></Obligations></Result></Response>
Recorder Recorder
Known limitation – no call recording after transfer to conference
SIP INVITE
200OK
Call Setup
PSTN Call Estab
Voice GW IP Phone
Recorder
Conference IP Phone
Known limitation – secure calls are not supported by CUCM
GW Preferred method Encrypted Call is

is configured identified
22:09:28.015 |AppInfo |Recording::- (0000006) -processGWPreferred ....

22:09:28.015 |AppInfo |Recording::- (0000006) -getRecordingAnchorMode:
PeerBib=[1];peerCMDevType=[8];qSigApduSupported=[0]
22:09:28.015 |AppInfo |Recording::- (0000006) -processGWPreferred: Encrypted
sideB! Only its BIB allowed for Recording. Normal anchorMode=[1] ignored!
22:09:28.015 |AppInfo |Recording::- (0000006) -processGWPreferred: Peer sideA
(28113320) has no GWBib [1];try agent deviceBib [3]
22:09:28.015 |AppInfo |Recording::- (0000006) -getDeviceRecordingAnchorMode:
cmDevType=[4];bibEnabled=[3];qSigApduSupported=[0]
Try to fallback to
Phone BIB
Troubleshooting GW-based recording issues
Recording mode selection in CUCM traces
00040863.007 |12:17:29.680 |AppInfo |SIPStationCdfc::getRecordingMethod recording

Requester= 5, phone Supports GatewayRecording = 1, recording Method= 1
Recording Method maps to Recording Media Source
1: Gateway Preferred
2: Device Preferred
3: Device BIB Only
GatewayRecording corresponds to attribute in REGISTER message of IP Phone
0: Gateway Recording is not supported

1: Gateway Recording is supported
IP Phone registration with Gateway-based recording supported
00607862.004 |14:37:40.528 |AppInfo |SIPTcp - wait_SdlReadRsp: Incoming SIP TCP message from 10.229.68.143
on port 49474 index 2505 with 2371 bytes:
[129636,NET]
REGISTER sip:10.62.150.183 SIP/2.0
Via: SIP/2.0/TCP 10.229.68.143:49474;branch=z9hG4bK551f1cf1
From: <sip:30120@10.62.150.183>;tag=c40acb4c5a4800047265d8ce-4de61f01
To: <sip:30120@10.62.150.183>
Call-ID: c40acb4c-5a480003-1cb8a40d-44ca6840@10.229.68.143
Max-Forwards: 70
Date: Sun, 12 Jan 2020 13:37:32 GMT
CSeq: 101 REGISTER
User-Agent: Cisco-CP9951/9.4.2
[…]
<x-cisco-remotecc-request>
[...]
<gatewayrecording></gatewayrecording>
<conferenceDisplayInstance></conferenceDisplayInstance>
</optionsind>
</x-cisco-remotecc-request>
CUCM is not able to register with Gateway
Jan 12 11:15:25.411: //WSAPI/XMF/INCOMING_MSG:: msg_type[6] RequestXmfRegister
connectionEventsFilter: CREATED|DISCONNECTED
mediaEventsFilter:
Jan 12 11:15:25.411: app url http://10.62.150.183:8090/ucm_xmf
Jan 12 11:15:25.411: app name Unified CM 11.5.1.14900-11
Jan 12 11:15:25.411: prov url http://10.62.150.156:8090/xmf
Jan 12 11:15:25.412: //WSAPI/XMF/registration_base_add_registration: remote url
(http://10.62.150.183:8090/ucm_xmf) not configured
Jan 13 11:15:25.412: //WSAPI//OUTGOING_EXCEPTION:: registrationID[] transactionID[Cisco:UCM:CayugaIf:4:1]
errorCode[ServiceException011], reason[Authentication fail] text[Application URL is not configured on the router.]
uc wsapi
source-address 10.62.150.156
!
provider xmf
remote-url 1 http://10.62.150.183:8090/ucm-xmf << Wrong URL configured
CUCM SIP Trunk destination should match WSAPI source-address on GW
uc wsapi
source-address 10.62.150.156
!
provider xmf
remote-url 1 http://10.62.150.183:8090/ucm_xmf
Monitoring Gateway status
Troubleshooting GW-based recording issues – trace collection
Information to be collected from the Gateway
Show commands
show wsapi registration xmf ! List of Registered CUCMs
show call media-forking ! Displays the forked stream information
Debug commands
debug voip application ! App framework debug
debug voip application media forking ! RTP forking info
debug ccsip message ! SIP signaling
debug wsapi xmf message ! XMF signaling
debug voip rtp packet ! RTP packet flow
Packet captures
Troubleshooting GW-based recording issues – trace collection
Information to be collected from the CUCM
Traces and logs

Detailed Cisco CallManager traces
Event Viewer – Application Log
Event Viewer – System Log
RisDC PerfMon Logs
Packet captures
utils network capture file xmf-capture size 1500 host ip 10.62.150.156
Call Recording
Redundancy with
Media-Proxy
Call recording redundancy with Media-Proxy
Use cases
• More then one recorder support CUCM 12.5

• In-call recording redundancy IOS XE 16.10
• Application real-time media processing
Architecture with Phone-Based recording
Recorder 1
Media Proxy
CUBE
Recorder 2
Signaling
Media
CUCM
Recorder 3
IP Phone
Architecture with Gateway-Based recording
Recorder 1
Media Proxy
CUBE
Recorder 2
Signaling
Media
CUCM
Recorder 3
IP Phone
Feature highlights
• Platforms ISR4K, ASR1K, CSR1000v

• Maximum of 5 recorders are supported
• Various call flows (internal, external, mobile)
• Supports High Availability (SSO, Box-to-Box with Redundancy Groups)
• Provides secure call forking with Phone-Based call recording
• Load-balancing of recorders with CUSP
Mandatory recorder policy
media profile recorder 1

proxy policy mandatory 1
Recorder 1
Media Proxy
INVITE
Recorder 2
Recorder 3
Media Latching with Gateway
• Media coming from the Gateway is on different IP/Port then advertised in SDP
Media Proxy
INVITE SDP
has a dummy
port 4000
RTP stream coming from GW
has different IP/Port then was
sent by CUCM in SDP
CUCM
SIP Trunk to SP Signaling
Media
Gateway/CUBE
Media Latching with IP Phone
• Media coming from the SCCP Phone is on different IP/Port then advertised in SDP
Media Proxy
INVITE SDP
has Phone IP
but dummy
port 4000
RTP/SRTP coming from Phone
have different port then was
sent by CUCM in SDP
CUCM
Signaling
Internal/External Media
Party
SCCP Phone
Configuring solution elements
CUBE/Gateway Configuration
ip http server
ip http max-connection 100
ip http timeout-policy idle 600 life 86400 requests 86400
uc wsapi
Gateway/CUBE source-address 10.62.150.156
CUBE: 10.62.150.156
provider xmf
Media Proxy configuration: Dial-peer
tagging
media profile recorder 1
media-recording proxy 4 5
proxy policy mandatory 4
Mandatory
Recorder
media class 1
Media Proxy recorder profile 1
Incoming
dial-peer voice 3 voip dial-peer for
MPS: 10.62.154.116 CUCM
incoming called-number 75001
voice-class codec 1
media-class 1
dtmf-relay rtp-nte
Media Proxy configuration:
dial-peer voice 4 voip

destination-pattern 75001
session protocol sipv2
session target ipv4:10.62.150.171
Outgoing dial-peers
session transport tcp
to the Recorders
voice-class codec 1
dtmf-relay rtp-nte
Media Proxy no vad
!
MPS: 10.62.154.116 destination-pattern 75001
voice-class codec 1
dtmf-relay rtp-nte
no vad
Recording Profile with DN:
Trunk to Gateway/CUBE:
CUCM
CUCM: 10.62.150.183
CUCM: 10.62.150.184
Recorded Line Appearance:
Redundancy options – Recorder Hunting dial-peer voice 4 voip
voice-class codec 1
Recorder 1 dtmf-relay rtp-nte
Media Proxy no vad
INVITE !
Recorder 2
voice-class codec 1
dtmf-relay rtp-nte
no vad
Recorder 3
MS-P2-4351(config)# voice hunt user-busy
Redundancy options - Load-balancing with CUSP
Recorder 1
Media Proxy
CUBE
Recorder 2
CUSP
Signaling
Media
CUCM
Recorder 3
IP Phone
Redundancy options- Fully redundant architecture
Recorder 1 Recorder 2 Recorder 3 Recorder 4 Recorder 5
CUSP
Media Proxy
Media Proxy Box-to-Box HA
Box-to-Box HA
Signaling
Media
Restrictions and Limitations
• Co-existence with CUBE

• SRTP <-> RTP forking
• SRTP fallback
• Mid-call signaling updates from Recorders
• Mid-call signaling block
• Video recording (only one audio m-line)
• SIP EO is required from CUCM
Troubleshooting Media-Proxy
INFO sip:Username@10.62.150.47:5060;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 10.62.150.91:5060;branch=z9hG4bK761A9B
From: <sip:123456@10.62.150.91>;tag=F8C3EE1-129F
To: ”Username" <sip:Username@10.62.150.47;x-nearend;x-refci=25579597;x-nearendclusterid=StandAloneCluster
Call-ID: ade62980-b8c1ede8-23e06-2f69410a@10.62.150.47
User-Agent: Cisco-SIPGateway/IOS-16.11.20180827.020621
Content-Type: application/x-cisco-proxy-recording-status+xml
Content-Length: 348
<recorderList>
<recorder>
<uri>sip:75001@10.62.150.71:5060</uri>
<recorderType>Optional</recorderType>
<status>Success</status>
</recorder>
<recorder>
<uri>sip:75001@10.62.150.72:5060</uri>
</recorder>
INFO sip:Username@10.62.150.47:5060;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 10.62.150.91:5060;branch=z9hG4bK761A9B
From: <sip:123456@10.62.150.91>;tag=F8C3EE1-129F
To: ”Username" <sip:Username@10.62.150.47;x-nearend;x-refci=25579597;x-nearendclusterid=StandAloneCluster
Call-ID: ade62980-b8c1ede8-23e06-2f69410a@10.62.150.47
User-Agent: Cisco-SIPGateway/IOS-16.11.20180827.020621
Content-Type: application/x-cisco-proxy-recording-status+xml
Content-Length: 348
<recorderList>
<recorder>
<uri>sip:75001@10.62.150.71:5060</uri>
</recorder>
<recorder>
<uri>sip:75001@10.62.150.72:5060</uri>
<status>Failure</status>
<errormessage>503 Service Unavailable</errormessage>
</recorder>
Show commands Debug commands

show voip rtp connections debug ccsip messages
show voip recmsp session debug ccsip error
show voip recmsp session detail debug ccsip events
show voip rtp forking debug ccsip states
show call active voice compact debug voip recmsp all
show sip-ua calls debug voip ccapi all
show media-proxy sessions debug voip fpi all
Conclusion
Callout for action
• Review your call recording architecture

• Combine all methods where possible
• Start baseline system monitoring
• Join discussion and ask questions
Look ahead
“Look,” whispered Chuck, and George lifted

his eyes to heaven. (There is always a last
time for everything.)
Overhead, without any fuss, the stars were
going out.
Arthur Clarke, 1953
Complete your
online session
survey • Please complete your session survey
after each session. Your feedback
is very important.
• Complete a minimum of 4 session
surveys and the Overall Conference
survey (starting on Thursday) to
receive your Cisco Live t-shirt.
• All surveys can be taken in the Cisco Events
Mobile App or by logging in to the Content
Catalog on ciscolive.com/emea.
Cisco Live sessions will be available for viewing on

demand after the event at ciscolive.com.
Continue your education
Demos in the
Walk-In Labs
Cisco Showcase
Meet the Engineer

Related sessions
1:1 meetings
Thank you

Recording Calls Study

Uploaded by

Document Informationclick to expand document information

Document Informationclick to expand document information

Copyright:

Available Formats

Recording Calls Study

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Recording Calls Study

Uploaded by

Copyright:

Available Formats

Deploying and

Vladimir Savostin, Technical Leader, CX

• Server-based recording solutions

• CUCM-controlled recording solutions

• Media forking with CUBE

• Built-in Bridge (BiB)

• Recording Media Source / Anchoring point

Jun 07 Feb 10 Feb 11 Jul 12 Oct 12 Jul 13 Dec 13 Jul 17 Dec 18

• Navigate to Cisco Unified Reporting ->

• Open System Reports ->

• Run ‘Unified CM Phone Feature List’

• Select Feature ‘Record’

• Click ‘Submit’ to get report

00607872.013 |14:37:40.642 |Created | SIPBuiltInBridgeControl(1,100,86,4) |SIPStationD(1,100,76,7) |

• Cisco Unified Reporting ->

• Open System Reports ->

• Run ‘Unified CM Phone Feature List’

• Select Feature ‘Built In Bridge’

• Click ‘Submit’ to get report

Calling Party Voice

PLK Softkey Service URL

MOH Hold Disconnect

• After resume or transfer media is re-stablished with same codec

CUCM load balancing calls in RG with Circular (default) distribution algorithm

CallRec Route List CallRec Route List

CallRec Route List 1 CallRec Route List 2

CallRec Route Group 2 CallRec Route Group 1

HTTP POST /CGI/Execute

IP Phone Enhancement request

After IP Phone reset BiB

|Pattern=c00112101001 |Pattern=b00105701008 |Pattern=b00105701021

• Always keep recorded devices in sync b/w CUCM and Recorder

11:20:17 < 100 Trying 350

11:24:43 < 200 OK 300

IP Phone C G.729 G.722

• Enable OPTIONS Ping in SIP Profile

• Use Transport TCP in SIP Trunk Security Profile

• Consider Early/Delayed Offer mode

• Unsupported BiB devices (Jabber for iPhone/Android)

Calling Party Voice

XCC XSVC XMF XCDR

eXtended eXtended eXtended eXtended

XMF Provider http://<CUCM>:8090/ucm_xmf XMF Application

SOAP over HTTP

SOAP over HTTP

XMF Connection abstracts states of the call at the endpoint or trunk:

2. Enable the API on IOS

3. Enable XMF service within the API

MS-P1-3900#sh control-plane host open-ports | i 8090

MS-P1-3900#sh control-plane host open-ports | i 8090

ip http server Set maximum number

HTTP Client settings Define timeouts:

Set interval between

In 18,5 seconds CUCM will terminate the connection

In 18,5 seconds CUCM will terminate the connection

Jan 12 05:40:16.166: //WSAPI/XMF/INCOMING_MSG:: msg_type[6] RequestXmfRegister

Jan 12 05:40:16.166: //WSAPI//OUTGOING_RESPONSE:: type 8 ResponseXmfRegister:

<?xml version="1.0" encoding="UTF-8"?>