CUBE Media Proxy - Cisco · media-recording proxy [dial-peer-tag1 dial-peer-tag2 dial-peer-tag3 dial-peer-tag4 dial-peer-tag5] Example: Step4 Note Youcanspecifymaximumoffivedial-peertags

CUBE Media Proxy

CUBE Media Proxy is a solution that provides multiple forking function, and is built on CUBE architecture.Multiple forks are required for recorder redundancy and advanced media processing needs. The CUBEMediaProxy solution supports mandatory and optional recorders.

CUBEMedia Proxy supports Unified CMNetwork-Based Recording (NBR) and SIP-BasedMedia Recording(SIPREC), to enable forking and recording of Real-Time Transport Protocol (RTP) streams.

• Feature Information for CUBE Media Proxy, on page 1• Supported Platforms, on page 2• Restrictions for CUBE Media Proxy, on page 2• CUBE Media Proxy Using Unified CM Network-Based Recording, on page 3• SIPREC-Based CUBE Media Proxy, on page 3• About Multiple Media Forking Using CUBE Media Proxy, on page 3• How to Configure CUBE Media Proxy, on page 12• Verify CUBE Media Proxy Configuration, on page 17• Supported Features, on page 27

Feature Information for CUBE Media ProxyThe following table provides release information about the feature or features that are described in this module.This table lists only the software release that introduced support for a given feature in a given software releasetrain. Unless noted otherwise, subsequent releases of that software release train also support that feature.

Use Cisco Feature Navigator to find information about platform support and software image support. CiscoFeature Navigator enables you to determine which software images support a specific software release, featureset, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. You do not requirean account on Cisco.com.

Table 1: Feature Information for Recording Proxy

Feature InformationReleasesFeature Name

The SIPREC-based CUBEMedia Proxy solutionsupports forking to multiple recorders.

Cisco IOS XE Amsterdam17.3.1a

SIPREC-Based CUBEMedia Proxy

CUBE Media Proxy1

http://www.cisco.com/go/cfn

Feature InformationReleasesFeature Name

The CUBE Media Proxy solution providesmultiple forking functions for redundancy andadvanced media processing.

IOS XE Gibraltar Release16.10.1a

CUBE Media Proxy

Supported PlatformsCUBEMedia Proxy is supported on the following Cisco router platforms running on Cisco IOS XE SoftwareReleases:

• Cisco 4000 Series-Integrated Services Routers (ISR G3 - 4331, 4351, 4431, 4451, 4461)

• Cisco Aggregated Services Routers (ASR - ASR1001-X, ASR1002-X, ASR1004 with RP2, ASR1006with RP2, Cisco ASR1006-X Aggregated Services Routers with RP2 and ESP40, ASR 1006-X withRP3 and ESP40/ESP100)

• Cisco Cloud Services Routers (CSR1000V series)

• Cisco Catalyst 8000V Edge Software (Catalyst 8000V) series

• Cisco 8300 Catalyst Edge Series Platforms (C8300-1N1S-6T, C8300-1N1S-4T2X, C8300-2N2S-6T,C8300-2N2S-4T2X)

When upgrading to C8000V software from a CSR1000V release, an existing throughput configuration willbe reset to a maximum of 250Mbps. Install an HSEC authorization code, which you can obtain from yourSmart License account, before reconfiguring your required throughput level.

Note

Restrictions for CUBE Media ProxyCUBE Media Proxy using Unified CM NBR, and SIPREC-Based CUBE Media Proxy do not support thefollowing:

• Video recording

• Recording of calls from the endpoints that are registered with the Cloud. For example, Cisco WebexHybrid calls.

• Secure media (SRTP) forking of non secure calls

• SRTP fall back

• Midcall block

• Collocation with CUBE

• Server Groups in outbound dial-peers towards recorders is not supported.

CUBE Media Proxy2

CUBE Media ProxySupported Platforms

• Midcall updates from the recorders such as pause or resume recording, RE-INVITE with SDP changes,INVITE that replaces header that is sent by recorders when they switch from active to standby CUBEMedia Proxy.

Midcall update "BYE" from the recorders is supported.Note

• Unified CM NBR and SIPREC can be used only on separate call flows.

CUBE Media Proxy using Unified CM NBR does not support the following:

• If the primary recorder sends a=inactive in the response SDP, the same is forwarded to Unified CM.Forking is not triggered to any of the recorders.

SIPREC-based CUBE Media Proxy does not support the following:

• Secure recording of secure calls (SRTP passthrough).

CUBEMediaProxyUsingUnifiedCMNetwork-BasedRecordingCUBE Media Proxy using Unified CM Network-Based Recording (NBR), is Unified CM dependent andrequires you to configure inbound dial-peers from Unified CM. After receiving a media forking request fromUnified CM, the CUBE Media Proxy sets up a recording session with the recorders.

SIPREC-Based CUBE Media ProxyThe SIPREC (SIPMedia Recording) feature supports media recording for Real-time Transport Protocol (RTP)streams in compliance with section 3.1.1. of RFC 7245, with CUBE Media Proxy acting as the SessionRecording Client (SRC). SIP protocol is used to establish a Recording Session (RS) between the CUBEMediaProxy and recorders, or any Speech Analytics endpoints.

SIPREC-Based CUBE Media Proxy is independent of Unified CM, and there is a direct SIP trunk to CUBEMedia Proxy via Cisco UBE. SIPREC-basedmedia forking happens at the ingress traffic. CUBEMedia Proxyreceives the SIPREC call from the ingress CUBE, and sends the SIPREC call to the recorders.

About Multiple Media Forking Using CUBE Media ProxyUnified CMNetwork-BasedCUBEMedia Proxy and SIPREC-BasedCUBEMedia Proxy support the followingfunctions:

• Recording forking to multiple recorders—support for maximum of five recorders

• Recorder redundancy by hunting algorithm

• Recording session policy control

• Load balancing during the initial call setup

• High Availability

CUBE Media Proxy3

CUBE Media ProxyCUBE Media Proxy Using Unified CM Network-Based Recording

• Transport protocols such as TLS, TCP and, UDP

• Secure forking of secure calls

Deployment Scenarios for CUBE Media Proxy

CUBE Media Proxy Using Unified CM Network-Based Recording (NBR)Following are the deployment scenarios for CUBEMedia Proxy using Unified CMNetwork-Based Recording:

Figure 1: Deployment Scenario for CUBE Media Proxy Using Unified CM NBR for External Call

Figure 2: Deployment Scenario for CUBE Media Proxy Using Unified CM NBR for Internal Call

The information flow is as follows:

1. External or internal call is set up between the endpoints.

2. CUBE Media Proxy receives the media forking request.

3. CUBE Media Proxy sets up sessions with the recorders based on the proxy policy.

CUBE Media Proxy4

CUBE Media ProxyDeployment Scenarios for CUBE Media Proxy

• Mandatory recorder: Proxy policy is configured to set a recorder as mandatory. CUBEMedia Proxytries to establish connection with the mandatory recorder. Forking to the remaining recorders happenonly if the connection with the mandatory recorder is successful.

• Optional recorders: When the proxy policy is not configured, all the recorders are set as optional.CUBE Media Proxy tries to establish a connection with the remaining recorders even if any of therecorders fail.

• If the CUBE Media Proxy receives '486' response from the initial recorder,CUBEMedia Proxy does not fork the INVITE to other recorders. To performalternate routing, configure the voice hunt user-busy command in globalconfiguration mode.

Example: Router(config)# voice hunt user-busy

Note

•

4. CUBE Media Proxy sends the invite to the recorders using Cisco Unified SIP Proxy.

5. Cisco Unified SIP Proxy performs load balancing and redundancy among recorders.

The CUBE Media Proxy solution supports Unified CM Release 12.5.1 and Cisco Unified SIP Proxy Release9.1.8.

Note

SIPREC-Based CUBE Media ProxyFollowing is the deployment scenario for SIPREC-Based CUBE Media Proxy:

Figure 3: Deployment Scenario for SIPREC-Based CUBE Media Proxy

The information flow during the recording session is as follows:

1. CUBE receives the call directly from the SIP trunk.

2. CUBE performs SIPREC-based media forking at ingress traffic.

CUBE Media Proxy5

CUBE Media ProxySIPREC-Based CUBE Media Proxy

3. CUBEMedia Proxy receives the SIPREC call fromCUBE, and sends the SIPREC call to all the recorders.

Recording MetadataMetadata is the information that a Recording Server (RS) receives from a Recording Client (RC) in a SIPsession. Metadata has the following functions:

• Carries the communication session data that describes the call to the recording server.

• Identifies the participants list.

• Identifies the session and media association time.

Recording Metadata in CUBE Media Proxy Using Unified CM NBR

The SIP header in the recording request that the CUBE Media Proxy receives from Unified CM, containsmetadata that provides information on the communication session. The CUBE Media Proxy sends this SIPINVITE header with metadata to all the configured recorders.

A SIP header of size up to 583 bytes is supported. Following is a sample SIP header of a recording request:

From: "abcd" <sip:[email protected];x-nearend;x-refci=27298698;x-nearendclusterid=NY-NJ-Labcluster;x-nearenddevice=SEP2834A28318CE;x-nearendaddr=198101;x-farendrefci=27298699;x-farendclusterid=NY-NJ-Labcluster;x-farenddevice=AFIFIM-VI1;x-farendaddr=172001;x-sessionid=696dd5d3f7755c6abdc438e93d01febf>;tag=14087~b35a5915-3167-4d6a-871d-c121221602bf-27298703

A maximum of 16 parameters are supported in the metadata of a SIP header. The following metadata fromthe SIP header is sent in all the requests and responses of a recording session:

;x-nearend;x-refci=27298698;x-nearendclusterid=NY-NJ-Labcluster;x-nearenddevice=SEP2834A28318CE;x-nearendaddr=198101;x-farendrefci=27298699;x-farendclusterid=NY-NJ-Labcluster;x-farenddevice=AFIFIM-VI1;x-farendaddr=172001;x-sessionid=696dd5d3f7755c6abdc438e93d01febf

Recording Metadata in SIPREC-Based CUBE Media Proxy

The initial SIPREC call from CUBE to CUBE Media Proxy, and the SIPREC call from CUBE Media Proxyto the recorders, will have the recording metadata in the SIPREC XML body.

Following is a sample SIPREC INVITE:INVITE sip:[email protected]:5060 SIP/2.0Via: SIP/2.0/UDP 8.43.33.209:5060;branch=z9hG4bK20959BFrom: <sip:8.43.33.209>;tag=678813-6ACTo: <sip:[email protected]>Date: Thu, 13 Feb 2020 03:35:19 GMTCall-ID: [email protected]: 100rel,timer,resource-priority,replaces,sdp-anat

CUBE Media Proxy6

CUBE Media ProxyRecording Metadata

Require: siprecMin-SE: 1800Cisco-Guid: 2967454021-1296568810-2195116643-3918495780User-Agent: Cisco-SIPGateway/IOS-17.3.20200207.160928Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO,REGISTERCSeq: 101 INVITEMax-Forwards: 70Timestamp: 1581564919Contact: <sip:8.43.33.209:5060>;+sip.srcExpires: 180Allow-Events: telephone-eventSession-ID: 812eae44f57c50b38e897d75d8e12809;remote=00000000000000000000000000000000Content-Type: multipart/mixed;boundary=uniqueBoundaryMime-Version: 1.0Content-Length: 2250

--uniqueBoundaryContent-Type: application/sdpContent-Disposition: session;handling=required

v=0o=CiscoSystemsSIP-GW-UserAgent 5146 1045 IN IP4 8.43.33.209s=SIP Callc=IN IP4 8.43.33.209t=0 0m=audio 8278 RTP/AVP 0c=IN IP4 8.43.33.209a=rtpmap:0 PCMU/8000a=ptime:20a=sendonlya=label:1m=audio 8280 RTP/AVP 0c=IN IP4 8.43.33.209a=rtpmap:0 PCMU/8000a=ptime:20a=sendonlya=label:2

--uniqueBoundaryContent-Type: application/rs-metadata+xmlContent-Disposition: recording-session

<?xml version="1.0" encoding="UTF-8"?><recording xmlns="urn:ietf:params:xml:ns:recording:1">

<datamode>complete</datamode><session session_id="sPVtz01IEeqC3dJj6Y+AJA==">

<sipSessionID>0e0960d88013509f86e7ad2d78da208a;remote=4d0de1325c205fa08f77d8d31c1b3a6f</sipSessionID>

<start-time>2020-02-13T03:35:19.008Z</start-time></session><participant participant_id="sPVtz01IEeqC3tJj6Y+AJA==">

<nameID aor="sip:[email protected]"></nameID>

</participant><participantsessionassoc participant_id="sPVtz01IEeqC3tJj6Y+AJA=="

session_id="sPVtz01IEeqC3dJj6Y+AJA=="><associate-time>2020-02-13T03:35:19.008Z</associate-time>

</participantsessionassoc><stream stream_id="sPgFxk1IEeqC49Jj6Y+AJA==" session_id="sPVtz01IEeqC3dJj6Y+AJA==">

<label>1</label></stream><participant participant_id="sPVtz01IEeqC39Jj6Y+AJA==">

CUBE Media Proxy7

CUBE Media ProxyRecording Metadata

<nameID aor="sip:[email protected]"></nameID>

</participant><participantsessionassoc participant_id="sPVtz01IEeqC39Jj6Y+AJA=="

session_id="sPVtz01IEeqC3dJj6Y+AJA=="><associate-time>2020-02-13T03:35:19.008Z</associate-time>

</participantsessionassoc><stream stream_id="sPgFxk1IEeqC5NJj6Y+AJA==" session_id="sPVtz01IEeqC3dJj6Y+AJA==">

<label>2</label></stream><participantstreamassoc participant_id="sPVtz01IEeqC3tJj6Y+AJA==">

<send>sPgFxk1IEeqC49Jj6Y+AJA==</send><recv>sPgFxk1IEeqC5NJj6Y+AJA==</recv>

</participantstreamassoc><participantstreamassoc participant_id="sPVtz01IEeqC39Jj6Y+AJA==">

<send>sPgFxk1IEeqC5NJj6Y+AJA==</send><recv>sPgFxk1IEeqC49Jj6Y+AJA==</recv>

</participantstreamassoc></recording>

--uniqueBoundary--

For a SIPREC call, the Require header in the SIP Invite (from Cisco UBE to CUBE Media Proxy, and fromCUBE Media Proxy to the recorders) must have a "siprec" extension, and also metadata in the XML body,else, the call is dropped. The Contact header in a SIP invite has a "+sip.src" extension.

Session IdentifierCUBE Media Proxy supports Session Identifier for tracking a recording session. The "Session-ID" header inthe SIP request, and response message, provides the details of the identifier. The Session Identifier refers tothe value of the identifier.

The Session-ID comprises of the following two Universally Unique Identifiers (UUIDs) corresponding to theinitiator and recipient of the recording request respectively:

• Local UUID corresponds to UUID of the User Agent that sends a recording request to the participantsof a recording session.

• Remote UUID corresponds to UUID of the User Agent that recieves the recording request in a recordingsession.

Session-ID HandlingBy default, CUBE Media Proxy (both Unified CM NBR and SIPREC-based) supports Session Identifier.

CUBE Media Proxy generates a unique UUID locally, and this UUID is passed as local UUID value in theSession-ID header of the following SIP request and response:

• Request to primary and optional recorders from CUBE Media Proxy.

• Response to Unified CM (Network-Based Recording) or CUBE (SIPREC-Based) from CUBE MediaProxy.

The following events are involved in the Session-ID handling by CUBE Media Proxy:

1. Depending on the type of CUBE Media Proxy—Unified CM NBR or SIPREC-based, the Session-IDheader in the recording request to CUBE Media Proxy contains UUID of Unified CM or CUBE as localUUID and a "NULL" for remote UUID as shown in the following example.

CUBE Media Proxy8

CUBE Media ProxySession Identifier

Session-ID: db248b6cbdc547bbc6c6fdfb6916eeb;remote=00000000000000000000000000000000

2. CUBE Media Proxy locally generates a local UUID. The Session-ID header with this local UUID valueand the remote UUID with a "NULL" is sent in the request to the primary recorder.

Session-ID: 8dfb2f2e1d4c518db6122080fb8b1d83;remote=00000000000000000000000000000000

3. CUBEMedia Proxy receives a 200OK response from the primary recorder. The Session-ID header of theresponse message contains UUID of the primary recorder as local UUID, and the locally generated UUIDby CUBE Media Proxy as the remote UUID.

Session-ID: 4fd24d9121935531a7f8d750ad16e19;remote=8dfb2f2e1d4c518db6122080fb8b1d83

4. CUBE Media Proxy sends a 200OK response to Unified CM or CUBE. The Session-ID header of theresponse message contains locally generated UUID by CUBEMedia Proxy as local UUID, and UUID ofUnified CM or CUBE as remote UUID.

Session-ID: 8dfb2f2e1d4c518db6122080fb8b1d83;remote=db248b6cbdc547bbc6c6fdfb6916eeb

5. CUBE Media Proxy sends a forking request to the remaining four recorders with Session-ID headercontaining locally generated UUID as the local UUID and a "NULL" value for the remote UUID.

Session-ID: 8dfb2f2e1d4c518db6122080fb8b1d83;remote=00000000000000000000000000000000

6. CUBEMedia Proxy receives 200OK response from the remaining four recorders. The Session-ID headerof the response message from each recorder contains UUID of the recorder as the local UUID and thelocally generated UUID by the CUBE Media Proxy as the remote UUID.

Session-ID: 4fd24d9121935531a7f8d750ad17f20;remote=8dfb2f2e1d4c518db6122080fb8b1d83

7. CUBEMedia Proxy sends a SIP InfoMessage to Unified CM. For more information on SIP InfoMessage,see SIP Info Messages from CUBE Media Proxy to Unified CM, on page 10. The Session-ID header ofthe SIP Info Message contains locally generated UUID by CUBE Media Proxy as local UUID and theUUID of Unified CM as the remote UUID.

Session-ID: 8dfb2f2e1d4c518db6122080fb8b1d83;remote=db248b6cbdc547bbc6c6fdfb6916eeb

There is no support for SIP Info Message in SIPREC-Based CUBE Media Proxy.Note

CUBE Media Proxy9

CUBE Media ProxySession-ID Handling

Recording State Notification

SIP Info Messages from CUBE Media Proxy to Unified CMAfter trying or establishing a recording session with the recorders, the CUBE Media Proxy sends SIP Infomessage to Unified CM to provide the consolidated status of all the recorders.

A SIP Info message is sent during the following stages of a recording session:

1. Initial Call: After receiving response from all the configured recorders during the initial call, a SIP Infomessage with status of each recorder is sent to the initiator of the recording session.

2. Mid-Call: When status of any of the recorders changes during the midcall, another SIP Info message withstatus of each recorder is sent to the initiator of the recording session. The scenario corresponds to any ofthe recorders sending a "BYE" or rejecting a midcall RE-INIVITE.

All the scenarios in the upcoming sections explain CUBE Media Proxy supporting two recorders. However,CUBE Media Proxy supports five recorders.

Note

XML Format of a SIP Info Message

The Content-Type header present in the SIP Info message is:Content-Type:application/x-cisco-proxy-recording-status+xml

The following is the XML format of a SIP info message.<recorderList>

<recorder>

<uri>recorder1</uri>

<recordertype>Mandatory</recordertype>

<status>Success</status>

<errormessage>null</errormessage>

</recoder>

<recorder>

<uri>recorder2</uri>

<recordertype>Mandatory</recordertype>

<status>Failed</status>

<errormessage>SIP error code received from Recorder</errormessage>

</recoder>

</recorderList>

Table 2: Details of XML Tag and Data Type

Data TypeXML Tag

Stringuri (Mandatory)

CUBE Media Proxy10

CUBE Media ProxyRecording State Notification

Data TypeXML Tag

Enum (Mandatory, Optional)recordertype (Mandatory)

Enum (Success, Failed)status (Mandatory)

Stringerrormessage (Optional)

SIP Info Message Sent During the Initial Call

SIP Info Message Sent During the Initial Call (All the Recorders as Optional)

For information on how to configure the recorders as Optional, see Step 3 and Step 4 of Configure CUBEMedia Proxy, on page 14.

The SIP Info Message sent during a recording session depends on the scenarios that are given in the followingtable:

Table 3: Call scenarios and recorder status during the initial call with all recorders as optional

<status> of recorder-2 in a SIP InfoMessage


Scenario

<success><success>Call to the primary recorderrecorder-1 is established andforking to recorder-2 is triggeredsuccessfully.

<failure><success>Call to the primary recorderrecorder-1 is established andforking to recorder-2 is rejectedwith 503 ServiceUnavailable.

<failure><success>Call to the primary recorderrecorder-1 is established and thereis no response from recorder-2 tothe forking request.

<failure><failure>Call to the recorder recorder-1 andrecorder-2 is rejected with 503Service Unavailable.

<failure><failure>recorder-1 and recorder-2 aredown.

<failure><failure>recorder-1 and recorder-2 respondsto the call with a 488 NotAcceptable Here response.

<failure><failure>recorder-1 and recorder-2 repondsto the call with a 600 BusyEverywhere response.

CUBE Media Proxy11

CUBE Media ProxySIP Info Message Sent During the Initial Call

After a SIP Info Message is sent, a 200 OK response is received from the initiator of the recording session.Note

SIP Info Message Sent During the Initial Call (One Recorder as Mandatory and Remaining as Optional)

For information on how to configure the recorders as Mandatory, see Step 3, Step 4 and, Step 5 of ConfigureCUBE Media Proxy, on page 14.

The SIP Info Message that is sent during a recording session depends on the scenarios that are given in thefollowing table.

Table 4: Call Scenarios and Recorder Status During the Initial Call with a Mandatory Recorder

<status> Of recorder-2 in a SIP InfoMessage


Scenario

<success><success>Call to the mandatory recorderrecorder-1 is established andforking to the optional recorderrecorder-2 is triggeredsuccessfully.

<failure><failure>

Error code is sent in the<errormessage>.

Note

Call to the mandatory recorderrecorder-1 is rejected with a failuremessage and hence the optionalrecorder recorder-2 is not tried.

<cancelled>

The connection to theoptional recorder iscancelled as the primaryrecorder disconnects.

Note

<failure>

BYE is sent in the<errormessage>.

Note

Call to the mandatory recorderrecorder-1 is established and whenthe optional recorder recorder-2 istried, the mandatory recorderdisconnects with a BYE.

<disconnected>

The optional recorder isdisconnected.

Note

<failure>

BYE is sent in the<errormessage>.

Note

After the call is established with amandatory recorder recorder-1 andthe optional recorder recorder-2,themandatory recorder disconnectswith a BYE.

• After a SIP Info Message is sent, a 200 OK response is received from the initiator of the recordingsession. Unified CM sends a 415 Unsupported Media Type message if the INFO sent fromCUBE Media Proxy has a malformed XML body.

Note

How to Configure CUBE Media Proxy• How to Configure Unified CM Network-Based Recording CUBE Media Proxy, on page 13

CUBE Media Proxy12

CUBE Media ProxySIP Info Message Sent During the Initial Call (One Recorder as Mandatory and Remaining as Optional)

• How to Configure SIPREC-Based CUBE Media Proxy, on page 17

How to Configure Unified CM Network-Based Recording CUBE Media ProxyFollowing are the steps to configure Unified CM Network-Based Recording CUBE Media Proxy:

1. Configure Outbound Dial-Peers to the Recorders, on page 13.

2. Configure CUBE Media Proxy, on page 14.

3. Configure Inbound Dial-Peer from Unified CM, on page 16.

Configure Outbound Dial-Peers to the Recorders

SUMMARY STEPS

1. enable2. configure terminal3. dial-peer voice dummy-recorder-dial-peer-tag voip4. destination-pattern [+] string

5. session protocol sipv26. session target ipv4:[recording-server-destination-address | recording-server-dns]7. session transport [udp| tcp | tls]8. end

DETAILED STEPS

PurposeCommand or Action

Enables privileged EXEC mode.enableStep 1

Example: • Enter your password if prompted.

Device> enable

Enters global configuration mode.configure terminal

Example:

Step 2

Device# configure terminal

Configures a recorder dial peer and enters dial peer voiceconfiguration mode.

dial-peer voice dummy-recorder-dial-peer-tag voip

Example:

Step 3

Device(config)# dial-peer voice 8000 voip

Specifies either the prefix or the full E.164 phone number(depending on your dial plan) to be used for a dial peer.

destination-pattern [+] string

Example:

Step 4

CUBE Media Proxy13

CUBE Media ProxyHow to Configure Unified CM Network-Based Recording CUBE Media Proxy


Device(config-dial-peer)# destination-pattern595959

The recorder dial-peers support thedestination-pattern which is a valid number orSIP URI. Regular expression in thedestination-pattern is not supported.

Note

Configures the VoIP dial peer to use Session InitiationProtocol (SIP).

session protocol sipv2

Example:

Step 5

Device(config-dial-peer)# session protocol sipv2

Specifies a destination address for a dial peer. Keyword andargument are as follows:

session target ipv4:[recording-server-destination-address| recording-server-dns]

Step 6

Example: • ipv4: destination address --IP address of the mediatarget.

Device(config-dial-peer)# session targetipv4:198.51.100.1 You can configure Unified SIP Proxy to support

recorder redundancy and load balancing, byspecifying the IPv4 Address of Unified SIPProxy in the session target command. TheCUBE Media Proxy sends the INVITEs to therecorders using Unified SIP Proxy.

Note

Configures a VoIP dial peer to use TCP. Using the sessiontransport command, you can also configure UDP and TLSprotocols.

session transport [udp| tcp | tls]

Example:Device(config-dial-peer)# session transport tcp

Step 7

Returns to privileged EXEC mode.end

Example:

Step 8

Device(config-dial-peer)# end

Configure CUBE Media Proxy

SUMMARY STEPS

1. enable2. configure terminal3. media profile recorder profile-tag

4. media-recording proxy [dial-peer-tag1 dial-peer-tag2 dial-peer-tag3 dial-peer-tag4 dial-peer-tag5]5. proxy policy mandatory dial-peer-tag

6. exit7. media class tag

8. recorder profile tag

9. exit

CUBE Media Proxy14

CUBE Media ProxyConfigure CUBE Media Proxy

DETAILED STEPS




Device> enable


Example:

Step 2


Configures the media profile recorder and enters mediaprofile configuration mode.

media profile recorder profile-tag

Example:

Step 3

Device(config)# media profile recorder 100

Configures the dial-peers for forking. The proxy configuresthe first dial-peer of the sequence for establishing a

media-recording proxy [dial-peer-tag1 dial-peer-tag2dial-peer-tag3 dial-peer-tag4 dial-peer-tag5]

Step 4

back-to-back (B2B) call, and the remaining dial-peers formedia forking.Example:

Device(cfg-mediaprofile)# media-recording proxy8000 8001 8002

You can specify maximum of five dial-peer tags.Note

Configures the specified dial-peer for establishing a B2Bcall.

proxy policy mandatory dial-peer-tag

Example:

Step 5

• You can specify only one dial-peer tag forestablishing a B2B call. The dial-peer tagmust be one of the dial-peers tagsconfigured using media-recording proxycommand. Each recorder group receivesone fork. When the forking session policycontrol is set to mandatory, if the forkingsession for Recorder Group 1 fails, then theremaining forking sessions also fail. Thecommand proxy policy mandatoryinitiates forking only when it is configuredalong with the commandmedia recordingproxy as in Step 4.

• For secure forking, the policy mandatorycommand must not be configured.

NoteDevice(cfg-mediaprofile)# proxy policy mandatory8001

Exits media profile configuration mode.exit

Example:

Step 6

Device(cfg-mediaprofile)# exit

CUBE Media Proxy15

CUBE Media ProxyConfigure CUBE Media Proxy


Configures a media class and enters media classconfiguration mode.

media class tag

Example:

Step 7

Device(config)# media class 100

Configures the media profile recorder.recorder profile tag

Example:

Step 8

Device(cfg-mediaclass)# recorder profile 100

Exits media class configuration mode.exit

Example:

Step 9

Device(cfg-mediaclass)# exit

Configure Inbound Dial-Peer from Unified CM

SUMMARY STEPS

1. enable2. configure terminal3. dial-peer voice call-manager-dial-peer-tag voip4. incoming uri {from | request |to | via } tag

5. media-class tag

6. exit

DETAILED STEPS




Device> enable


Example:

Step 2


Configures an inbound dial peer and enters dial peer voiceconfiguration mode.

dial-peer voice call-manager-dial-peer-tag voip

Example:

Step 3

Device(config)# dial-peer voice 1000 voip

CUBE Media Proxy16

CUBE Media ProxyConfigure Inbound Dial-Peer from Unified CM


Configures the voice class that is used to match the VoIPdial-peer to the URI of an incoming call from Unified CMvia the header in an incoming SIP Invite message.

incoming uri {from | request |to | via } tag

Example:

Device(config-dial-peer)# incoming uri via 101

Step 4

For more information on incoming uricommand, see incoming uri.

Note

Configures media class on the inbound dial peer fromUnified CM.

media-class tag

Example:

Step 5

Device(config-dial-peer)# media-class 100

Exits media class configuration mode.exit

Example:

Step 6

Device(cfg-mediaclass)# exit

How to Configure SIPREC-Based CUBE Media ProxyFollowing are the steps to configure SIPREC-based CUBE Media Proxy:

1. Configure Outbound Dial-Peers to the Recorders, on page 13.

2. Configure CUBE Media Proxy, on page 14.

3. Configure SIPREC on CUBE. For more information, see SIPREC (SIP Recording).

Verify CUBE Media Proxy ConfigurationYou can verify the configuration of CUBE Media Proxy using Unified CM NBR and SIPREC-Based CUBEMedia Proxy using the following show and debug commands. These commands can be entered in any order.

SUMMARY STEPS

1. enable2. show voip rtp connections3. show voip recmsp session4. show voip recmsp session detail call-id call-id

5. show voip rtp forking6. show call active voice compact7. show sip-ua calls8. show voip fpi calls9. show media-proxy sessions10. show media-proxy sessions summary11. show media-proxy sessions summary history12. show media-proxy sessions call-id call-id

CUBE Media Proxy17

CUBE Media ProxyHow to Configure SIPREC-Based CUBE Media Proxy

https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/voice/vcr2/vcr2-cr-book/vcr-i1.html#wp7490919080

cube-book_chapter39.pdf#nameddest=unique_457

13. show media-proxy sessions session-id WORD

14. show media-proxy sessions metadata-session-id x-session-id

15. debug ccsip messages(for audio calls)16. Enter one of the following:

• debug ccsip all• debug voip recmsp all• debug voip ccapi all• debug voip fpi all (for ASR devices only)

DETAILED STEPS

Step 1 enable

Enables privileged EXEC mode.

Example:

Device> enable

Step 2 show voip rtp connections

Displays Real-Time Transport Protocol (RTP) connections.

Example:

In CUBE Media Proxy using Unified CM NBR, every recording session has one rtp connection each towards therecorders and one rtp connection towards the recording source that is on the inbound side. Following is the sampleoutput for CUBE Media Proxy using Unified CM NBR with three recorders:Device# show voip rtp connectionsVoIP RTP Port Usage Information:Max Ports Available: 19999, Ports Reserved: 101, Ports in Use:4Port range not configuredMin Max Ports Ports Ports

Media-Address Range Port Port Available Reserved In-useGlobal Media Pool 8000 48198 19999 101 4VoIP RTP active connections :No. CallId dstCallId LocalRTP RmtRTP LocalIP RemoteIP MPSS VRF1 248 249 8218 8372 198.51.100.1 192.0.2.1 NO NA2 249 248 8220 9000 198.51.100.1 192.0.2.1 NO NA3 252 251 8222 9238 198.51.100.1 192.0.2.1 NO NA4 255 254 8224 9240 198.51.100.1 192.0.2.1 NO NA

Found 4 active RTP connections

In SIPREC-Based CUBE Media Proxy, there are 2-m lines each for inbound call leg and the call leg towards fiverecorders. Therefore, we see 12 active RTP connections. Following is the sample output:Device# show voip rtp connectionsVoIP RTP Port Usage Information:Max Ports Available: 19999, Ports Reserved: 101, Ports in Use: 12Port range not configuredMin Max Ports Ports Ports

Media-Address Range Port Port Available Reserved In-useGlobal Media Pool 8000 48198 19999 101 12VoIP RTP active connections :

CUBE Media Proxy18

CUBE Media ProxyVerify CUBE Media Proxy Configuration

No. CallId dstCallId LocalRTP RmtRTP LocalIP RemoteIP MPSS VRF1 99 101 8108 6012 8.43.21.69 8.41.17.71 NO NA2 100 102 8110 6014 8.43.21.69 8.41.17.71 NO NA3 101 99 8112 6005 8.43.21.69 8.41.17.71 NO NA4 102 100 8114 8883 8.43.21.69 8.41.17.71 NO NA5 107 103 8116 6000 8.43.21.69 8.41.17.71 NO NA6 108 103 8118 8887 8.43.21.69 8.41.17.71 NO NA7 111 104 8120 6008 8.43.21.69 8.41.17.71 NO NA8 112 104 8122 9990 8.43.21.69 8.41.17.71 NO NA9 115 105 8124 6024 8.43.21.69 8.41.17.71 NO NA10 116 105 8126 9979 8.43.21.69 8.41.17.71 NO NA11 119 106 8128 6016 8.43.21.69 8.41.17.71 NO NA12 120 106 8130 9968 8.43.21.69 8.41.17.71 NO NAFound 12 active RTP connections

Step 3 show voip recmsp session

Displays active recording Media Service Provider (MSP) session information internal to CUBE Media Proxy.

Example:

Following is the sample output for CUBE Media Proxy using Unified CM NBR and SIPREC-Based CUBE MediaProxy:

Device# show voip recmsp session

RECMSP active sessions:MSP Call-ID AnchorLeg Call-ID ForkedLeg Call-ID103 99 107104 99 111105 99 115106 99 119Found 4 active sessions

Step 4 show voip recmsp session detail call-id call-id

Displays detailed information about the recording MSP Call ID.

Example:

Following is the sample output for CUBE Media Proxy using Unified CM NBR:

Device# show voip recmsp session detail call-id 145RECMSP active sessions:Detailed Information=========================Recording MSP Leg Details:Call ID: 143GUID : 7C5946D38ECD

AnchorLeg Details:Call ID: 141Forking Stream type: voice-nearendParticipant: 708090

Non-anchor Leg Details:Call ID: 140Forking Stream type: voice-farendParticipant: 10000

Forked Leg Details:Call ID: 145Voice Near End Stream CallID 145

CUBE Media Proxy19


Stream State ACTIVEFound 1 active sessions

In SIPREC-Based CUBE Media Proxy, there are two voice near end streams for the forked call leg. Following is thesample output:

Device# show voip recmsp session detail call-id 103RECMSP active sessions:Detailed Information=========================Recording MSP Leg Details:Call ID: 103GUID : C710812A808A

AnchorLeg Details:Call ID: 99Forking Stream type: voice-nearendParticipant: sipp

Non-anchor Leg Details:Call ID: 101Forking Stream type: voice-farendParticipant: 9876

Forked Leg Details:Call ID: 107Voice Near End Stream CallID 107Stream State ACTIVEVoice Near End Stream CallID 108Stream State ACTIVEFound 1 active sessions

Step 5 show voip rtp forking

Displays RTP media-forking connections.

Example:


Device# show voip rtp forkingVoIP RTP active forks :Fork 1stream type voice-only (0): count 0stream type voice+dtmf (1): count 0stream type dtmf-only (2): count 0stream type voice-nearend (3): count 1remote ip 192.0.2.1, remote port 38526, local port 18648codec g711ulaw, logical ssrc 0x53packets sent 29687, packets received 0

stream type voice+dtmf-nearend (4): count 0stream type voice+dtmf-farend (6): count 0stream type video (7): count 0stream type video-nearend (8): count 0stream type video-farend (9): count 0stream type application (10): count 0

Following is the sample output for SIPREC-Based CUBE Media Proxy:

Device# show voip rtp forkingVoIP RTP active forks :Fork 1

CUBE Media Proxy20


stream type voice-only (0): count 0stream type voice+dtmf (1): count 0stream type dtmf-only (2): count 0stream type voice-nearend (3): count 2remote ip 8.41.17.71, remote port 6000, local port 8116codec g711ulaw, logical ssrc 0x53packets sent 29687, packets received 0

remote ip 8.41.17.71, remote port 8887, local port 8118codec g711ulaw, logical ssrc 0x53packets sent 1296, packets received 0

stream type voice+dtmf-nearend (4): count 0stream type voice+dtmf-farend (6): count 0stream type video (7): count 0stream type video-nearend (8): count 0stream type video-farend (9): count 0stream type application (10): count 0

Step 6 show call active voice compact

Displays a compact version of voice calls in progress. An additional call leg is displayed for media forking.

Example:

Device# show call active voice compact<callID> A/O FAX T<sec> Codec type Peer Address IP R<ip>:<udp>Total call-legs: 3

140 ANS T644 g711ulaw VOIP P10000 192.0.2.1:18638141 ORG T644 g711ulaw VOIP P708090 198.51.100.1:26184145 ORG T643 g711ulaw VOIP P595959 192.0.2.2:38526

Step 7 show sip-ua calls

Displays active user agent client (UAC) and user agent server (UAS) information on SIP calls.

Example:


Device# show sip-ua callsTotal SIP call legs:3, User Agent Client:2, User Agent Server:1SIP UAC CALL INFOCall 1SIP Call ID : [email protected] of the call : STATE_ACTIVE (7)Substate of the call : SUBSTATE_NONE (0)Calling Number : 808808Called Number : 8453Called URI :Bit Flags : 0xC04018 0x80000100 0x80CC Call ID : 2Local UUID : c7351800dd135daba19758eac6b1dd70Remote UUID : ab9f4823802156aaaa8d62e04aaa2b96Source IP Address (Sig ): 192.0.2.1Destn SIP Req Addr:Port : [192.0.2.2]:9312Destn SIP Resp Addr:Port: [192.0.2.2]:9312Destination Name :Number of Media Streams : 1Number of Active Streams: 1RTP Fork Object : 0x0Media Mode : flow-throughMedia Stream 1State of the stream : STREAM_ACTIVE

CUBE Media Proxy21


Stream Call ID : 2Stream Type : voice-only (0)Stream Media Addr Type : 1Negotiated Codec : g711ulaw (160 bytes)Codec Payload Type : 0Negotiated Dtmf-relay : inband-voiceDtmf-relay Payload Type : 0QoS ID : -1Local QoS Strength : BestEffortNegotiated QoS Strength : BestEffortNegotiated QoS Direction : NoneLocal QoS Status : NoneMedia Source IP Addr:Port: [192.0.2.1]:8002Media Dest IP Addr:Port : [192.0.2.2]:9000Mid-Call Re-Assocation Count: 0SRTP-RTP Re-Assocation DSP Query Count: 0

Options-Ping ENABLED:NO ACTIVE:NO

Following is the sample output for SIPREC-Based CUBE Media Proxy:

Device# show sip-ua callsTotal SIP call legs:6, User Agent Client:5, User Agent Server:1SIP UAC CALL INFOCall 1SIP Call ID : [email protected]

State of the call : STATE_ACTIVE (7)Substate of the call : SUBSTATE_NONE (0)Calling Number : sippCalled Number : 9876Called URI : sip:[email protected]:8881Bit Flags : 0xC04018 0x90000100 0x80CC Call ID : 101Local UUID : eeabf35db3d25ca4b8276616cdcf5d15Remote UUID : 8afa5ed7b8a052e29235bade4affcf9eSource IP Address (Sig ): 8.43.21.69Destn SIP Req Addr:Port : [8.41.17.71]:8881Destn SIP Resp Addr:Port: [8.41.17.71]:8881Destination Name : 8.41.17.71Number of Media Streams : 2Number of Active Streams: 2RTP Fork Object : 0x0Media Mode : flow-throughMedia Stream 1State of the stream : STREAM_ACTIVEStream Call ID : 101Stream Type : voice+dtmf (1)Stream Media Addr Type : 1Negotiated Codec : g711ulaw (160 bytes)Codec Payload Type : 0Negotiated Dtmf-relay : rtp-nteDtmf-relay Payload Type : 101QoS ID : -1Local QoS Strength : BestEffortNegotiated QoS Strength : BestEffortNegotiated QoS Direction : NoneLocal QoS Status : NoneMedia Source IP Addr:Port: [8.43.21.69]:8112Media Dest IP Addr:Port : [8.41.17.71]:6005

Media Stream 2State of the stream : STREAM_ACTIVEStream Call ID : 102Stream Type : voice+dtmf (1)Stream Media Addr Type : 1

CUBE Media Proxy22


Negotiated Codec : g711ulaw (160 bytes)Codec Payload Type : 0Negotiated Dtmf-relay : rtp-nteDtmf-relay Payload Type : 101QoS ID : -1Local QoS Strength : BestEffortNegotiated QoS Strength : BestEffortNegotiated QoS Direction : NoneLocal QoS Status : NoneMedia Source IP Addr:Port: [8.43.21.69]:8114Media Dest IP Addr:Port : [8.41.17.71]:8883

Mid-Call Re-Assocation Count: 0SRTP-RTP Re-Assocation DSP Query Count: 0

Options-Ping ENABLED:NO ACTIVE:NO

Step 8 show voip fpi calls

Displays the call (both inbound and outbound leg) information at the application level.

Example:

Following is the sample output for CUBE Media Proxy using Unified CM NBR:Device#show voip fpi callsNumber of Calls : 1---------- ---------- ---------- ----------- --------------- ------------confID correlator AcallID BcallID state event---------- ---------- ---------- ----------- --------------- ------------1005 1 1019 1020 ALLOCATED DETAIL_STAT_RSP

As there are 2-m lines in the incoming invite to SIPREC-Based CUBE Media Poxy, two FPI sessions are created.Following is the sample output:Device#show voip fpi callsNumber of Calls : 2---------- ---------- ---------- ----------- --------------- ------------confID correlator AcallID BcallID state event---------- ---------- ---------- ----------- --------------- ------------42 13 102 100 ALLOCATED DETAIL_STAT_RSP41 14 99 101 ALLOCATED DETAIL_STAT_RSP

Step 9 show media-proxy sessions

Displays the inbound and forked Call-ID, Session-ID, and dial peer tag details of the active recording sessions. The"Secure" field in the command output is tagged Y if the recording session is secure and N if the recording session isnon-secure. The "SIPREC" field in the command output is tagged Y for SIPREC-based recording session and N forUnified CM-based recording session.

Example:Device# show media-proxy sessions

No. Call-ID Session-ID Dialpeer Secure SIPRECInbound/Forked LocalUuid;RemoteUuid Tag (Y/N) (Y/N)

================================================================================================1 36770/- a234a20672ce596d969c59ee9767f127; 3 N Y

aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

Step 10 show media-proxy sessions summary

Displays the active recording session details such as the dial peer tag, IP address, port number, number of failed recordingsessions, and total number of recording sessions.

CUBE Media Proxy23


Example:Device# show media-proxy sessions summary

No Inbound/Forked Dialpeer-Tag IP:Port Total/Failed Sessions---------------------------------------------------------------------------------------------1 Forked 100 ipv4:192.0.2.2:6680 2/02 Forked 200 ipv4:192.0.2.2:6220 2/03 Inbound 5678 2/0

Step 11 show media-proxy sessions summary history

Displays the details of all the completed recording sessions. Once the recording session is completed, the session detailsmoves to the call history table. Total Sessions refers to the cumulative value of all the completed recording sessions.

Example:Device# show media-proxy sessions summary history

No. Inbound/Forked Dialpeer Tag IP:Port Total/Failed Sessions---------------------------------------------------------------------------------------------1 Inbound 5678 2/02 Forked 100 ipv4:192.0.2.2:6680 2/03 Forked 200 ipv4:192.0.2.2:6220 2/0

To clear the history data for the CUBE Media Proxy recording sessions, use the command clear media-proxysessions summary history, in privileged EXEC mode.Device# clear media-proxy sessions summary history

Following is the sample output of the command show media-proxy sessions summary history after clearingthe CUBE Media Proxy recording session history data.Device# show media-proxy sessions summary history

No. Inbound/Forked Dialpeer Tag IP:Port Total/Failed Sessions---------------------------------------------------------------------------------------------

Note

Step 12 show media-proxy sessions call-id call-id

Displays the details of the inbound leg and all the forked legs that are associated with the specified SIP leg call-ID.MSP call-ID is not a valid call-ID for this command. Specify the CCAPI call identifier of the SIP leg.

Example:Device# show media-proxy sessions call-id 2CC Call-ID: 1 Inbound-legDur: 00:00:15 tx: 0/0 rx: 1484/296800 lost: 0/0/0 delay: 0/0/0msRemote-Addr: 198.51.100.1:6009 Local-Addr: 192.0.2.1:8000 rtt:0ms pl:0/0msDialpeer-Tag: 100 Negotiated-Codec: g711ulawSRTP-Status: off SRTP-Cipher: NALocalUUID: 6bde661e9767590b930f3427ad6e94e9 RemoteUUID: aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

CC Call-ID: 2 Forked-leg (Primary)Dur: 00:00:15 tx: 1484/296800 rx: 0/0 lost: 0/0/0 delay: 0/0/0msRemote-Addr: 198.51.100.1:6000 Local-Addr: 192.0.2.1:8002 rtt:0ms pl:0/0msDialpeer-Tag: 200 Negotiated-Codec: g711ulawSRTP-Status: off SRTP-Cipher: NALocalUUID: bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb RemoteUUID: 6bde661e9767590b930f3427ad6e94e9

CUBE Media Proxy24


CC Call-ID: 7 Forked-legDur: 00:00:15 tx: 1480/296000 rx: 0/0 lost: 0/0/0 delay: 0/0/0msRemote-Addr: 198.51.100.1:6001 Local-Addr: 192.0.2.1:8004 rtt:0ms pl:0/0msDialpeer-Tag: 300 Negotiated-Codec: g711ulawSRTP-Status: off SRTP-Cipher: NALocalUUID: cccccccccccccccccccccccccccccccc RemoteUUID: 6bde661e9767590b930f3427ad6e94e9




Step 13 show media-proxy sessions session-id WORD

Displays the details of the Media Proxy recording sessions that are associated with the specified session-ID. To displaythe details of a specific call-leg, specify the complete session ID string as, local-uuid;remote=remote-uuid. Tokensthat are allowed for WORD are '*', [0-9], [a-f], and [A-F].

Example:Device# show media-proxy sessions session-id 6bde661e9767590b930f3427ad6e94e9CC Call-ID: 1 Inbound-legDur: 00:00:15 tx: 0/0 rx: 1484/296800 lost: 0/0/0 delay: 0/0/0msRemote-Addr: 198.51.100.1:6009 Local-Addr: 192.0.2.1:8000 rtt: 0ms pl: 0/0msDialpeer-Tag: 100 Negotiated-Codec: g711ulawSRTP-Status: off SRTP-Cipher: NALocalUUID: 6bde661e9767590b930f3427ad6e94e9 RemoteUUID: aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

CC Call-ID: 2 Forked-leg (Primary)Dur: 00:00:15 tx: 1484/296800 rx: 0/0 lost: 0/0/0 delay: 0/0/0msRemote-Addr: 198.51.100.1:6000 Local-Addr: 192.0.2.1:8002 rtt: 0ms pl: 0/0msDialpeer-Tag: 200 Negotiated-Codec: g711ulawSRTP-Status: off SRTP-Cipher: NALocalUUID: bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb RemoteUUID: 6bde661e9767590b930f3427ad6e94e9

CC Call-ID: 7 Forked-legDur: 00:00:15 tx: 1480/296000 rx: 0/0 lost: 0/0/0 delay: 0/0/0msRemote-Addr: 198.51.100.1:6001 Local-Addr: 192.0.2.1:8004 rtt: 0ms pl: 0/0msDialpeer-Tag: 300 Negotiated-Codec: g711ulawSRTP-Status: off SRTP-Cipher: NALocalUUID: cccccccccccccccccccccccccccccccc RemoteUUID: 6bde661e9767590b930f3427ad6e94e9

CC Call-ID: 9 Forked-legDur: 00:00:15 tx: 1479/295800 rx: 0/0 lost: 0/0/0 delay: 0/0/0msRemote-Addr: 198.51.100.1:6004 Local-Addr: 192.0.2.1:8006 rtt: 0ms pl: 0/0msDialpeer-Tag: 400 Negotiated-Codec: g711ulaw

CUBE Media Proxy25


SRTP-Status: off SRTP-Cipher: NALocalUUID: cccccccccccccccccccccccccccccccc RemoteUUID: 6bde661e9767590b930f3427ad6e94e9



Step 14 show media-proxy sessions metadata-session-id x-session-id

Displays the details of the Media Proxy recording sessions based on the x-session-id present in the "From" header ofthe INVITE from CUCM.

Example:Device# show media-proxy sessions metadata-session-id 696dd5d3f7755c6abdc438e93d01febfCC Call-ID: 77 Inbound-legDur: 00:00:46 tx: 0/0 rx: 3105/578880 lost: 0/0/0 delay: 0/0/0msRemote-Addr: 198.51.100.1:8010 Local-Addr: 198.51.100.1:8048 rtt: 0ms pl: 0/0msDialpeer-Tag: 1 Negotiated-Codec: g711ulawSRTP-Status: off SRTP-Cipher: NALocalUUID: 528b282b804c5fd098eaba3696c00de2 RemoteUUID: aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

CC Call-ID: 78 Forked-leg (Primary)Dur: 00:00:46 tx: 3105/578880 rx: 0/0 lost: 0/0/0 delay: 0/0/0msRemote-Addr: 198.51.100.1:8014 Local-Addr: 198.51.100.1:8050 rtt: 0ms pl: 0/0msDialpeer-Tag: 2 Negotiated-Codec: g711ulawSRTP-Status: off SRTP-Cipher: NALocalUUID: bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb RemoteUUID: 528b282b804c5fd098eaba3696c00de2

CC Call-ID: 84 Forked-legDur: 00:00:46 tx: 3100/577880 rx: 0/0 lost: 0/0/0 delay: 0/0/0msRemote-Addr: 198.51.100.1:8018 Local-Addr: 198.51.100.1:8052 rtt: 0ms pl: 0/0msDialpeer-Tag: 3 Negotiated-Codec: g711ulawSRTP-Status: off SRTP-Cipher: NALocalUUID: bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb RemoteUUID: 528b282b804c5fd098eaba3696c00de2



CC Call-ID: 91 Forked-legDur: 00:00:46 tx: 3101/578080 rx: 0/0 lost: 0/0/0 delay: 0/0/0msRemote-Addr: 198.51.100.1:8030 Local-Addr: 198.51.100.1:8058 rtt: 0ms pl: 0/0msDialpeer-Tag: 6 Negotiated-Codec: g711ulaw

CUBE Media Proxy26


SRTP-Status: off SRTP-Cipher: NALocalUUID: bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb RemoteUUID: 528b282b804c5fd098eaba3696c00de2

Step 15 debug ccsip messages(for audio calls)

The CUBE Media Proxy sends INVITEs to the recorders with a single stream, which successfully forks the primarycall to the recorders. INVITEs to recorders have a single m-line with a send-only attribute.

Step 16 Enter one of the following:

• debug ccsip all• debug voip recmsp all• debug voip ccapi all• debug voip fpi all (for ASR devices only)

Displays detailed debug messages.

Supported Features

Support for Mid-Call FeaturesCUBE Media Proxy using Unified CM NBR and SIPREC-Based CUBE Media Proxy support mid-callsignalling events that involve RE-INVITEs from the initiator of the recording session (Unified CM or CiscoUBE) to the recorders. CUBE Media Proxy handles the RE-INVITEs that request for an SDP change, codecchange, session refresh, and direction change in SDP.

In CUBE Media Proxy using Unified CM NBR, based on the change in the status of the recorders during themid-call, SIP Info messages are sent from the recorders to the Unified CM.

CUBE Media Proxy using Unified CM NBR supports mid-call RE-INVITE with no SDP change. However,SIPREC-Based CUBEMedia Proxy does not support mid-call RE-INVITE that does not involve any changein the SDP.

Note

When all the recorders are configured as optional, CUBE Media Proxy using Unified CM NBR supports themid-call features given in the following table:

CUBE Media Proxy27

CUBE Media ProxySupported Features

Table 5: Details of Mid-Call Scenarios and the events (optional recorders)

Events in the Mid-Call ScenarioMid-Call Scenario(optional recorders)

1. Unified CM sends amid-call RE-INVITEwith any of the following changes:

• Media change

• XML change without any change in media

• Change in media and XML

• No SDP change

• Refresh invite

2. CUBE Media Proxy sends the RE-INVITE to the primary recorder only.

Mid-call session refresh

1. Unified CM sends a mid-call RE-INVITE with direction change in SDP.

2. CUBE Media Proxy sends the RE-INVITE to the primary recorder.

3. The primary recorder sends a200OK response to CUBEMedia Proxy, whichsends this response to Unified CM.

4. CUBE Media Proxy sends the RE-INVITE to the remaining recorders.

Mid-call direction change

1. Unified CM sends a mid-call RE-INVITE with a codec change in SDP.


3. The primary recorder sends a 200OK response for the codec change to CUBEMedia Proxy, which sends this response to Unified CM.

4. CUBE Media Proxy sends the RE-INVITE containing new codec to theremaining recorders.

5. The remaining recorders send a 200OK response to CUBE Media Proxy.

Mid-call codec changewith a 200OK from theprimary recorder



3. The primary recorder sends a 488 error response for the codec change toCUBE Media Proxy, which sends this response to Unified CM.

4. REINVITE is not sent to the remaining recorders.

Mid-call codec changewith failure status of theprimary recorder

CUBE Media Proxy28

CUBE Media ProxySupport for Mid-Call Features






5. Two of the recorders send a 488 error response for the codec change toCUBE Media Proxy and the remaining recorders respond with a 200OK.

6. CUBE Media Proxy sends a BYE to the failed recorders and disconnectsthem.

Mid-call codec changewith failure status of therecorders

1. Unified CM sends a mid-call RE-INVITE with an SRTP key change.



4. CUBEMedia Proxy sends the RE-INVITE containing new SRTP key to theremaining recorders.


Mid-call SRTP suite orSRTP key change with a200OK from the primaryrecorder

1. Unified CM sends a mid-call RE-INVITE with an SRTP key change.


3. The primary recorder sends a 488 error response for the SRTP key changeto CUBE Media Proxy, which sends this response to Unified CM.


Mid-call SRTP suite orSRTP key change withfailure status of theprimary recorder

1. Unified CM sends a mid-call RE-INVITE with an SRTP change.


3. The primary recorder sends a 200OK response for the SRTP key change toCUBE Media Proxy, which sends this response to Unified CM.

4. CUBEMedia Proxy sends the RE-INVITE containing new SRTP key to theremaining recorders.

5. Two of the recorders send a 488 error response for the SRTP key change toCUBE Media Proxy and the remaining recorders respond with a 200OK.


Mid-call SRTP suite orSRTP key change withfailure status of therecorders

CUBE Media Proxy29


When a mandatory recorder is configured, CUBEMedia Proxy using Unified CMNBR supports the mid-callfeatures given in the following table:

Table 6: Details of Mid-Call Scenarios and the events (mandatory recorder)

Events in the Mid-Call ScenarioMid-Call Scenario(mandatory recorder)

1. Unified CM sends a mid-call RE-INVITE with any of the SDP changes.


3. The primary recorder sends a 488 error response or 503 error response forthe SDP change to CUBEMedia Proxy, which sends this response to UnifiedCM.


Mid-call SDP changewithfailure status of themandatory recorder

1. Unified CM sends a mid-call RE-INVITE with any of the SDP changes.


3. The primary recorder sends a 200OK response for the SDP change to CUBEMedia Proxy, which sends this response to Unified CM.


5. One of the recorders responds with a 488 error response for the SDP changeto CUBE Media Proxy and the remaining recorders respond with a 200OK.

6. CUBE Media Proxy sends a BYE to the failed recorder and disconnects thesame.

Mid-call SDP changewithfailure status of therecorders

A mid-call SIP Info message containing status of the recorders is sent to the Unified CM when the mid-callRE-INVITEs to the recorders fail.

During the mid-call, the following events happen when the primary recorder sends a BYE to the CUBEMediaProxy:

• Primary recorder as Optional: CUBEMedia Proxy sends a 200OK response to the primary recorder. TheCUBEMedia Proxy does not send BYE to Unified CM. The call-leg between Unified CM and the CUBEMedia Proxy enters midcall-signaling blockmode to reduce interoperability issues that arise to consumingmid-call RE-INVITES. The call-leg between the CUBE Media Proxy and the primary recorder remainsin a dormant state. Hence the primary recorder stops recording. However, the remaining recorders continuewith the recording.

• Primary recorder as Mandatory: CUBEMedia Proxy sends BYE from the mandatory recorder to UnifiedCM. All the recorders disconnect and the recording stops.

Note

When all the recorders are configured as optional, SIPREC-Based CUBE Media Proxy supports the mid-callfeatures given in the following table:

CUBE Media Proxy30


Table 7: Details of Mid-Call Scenarios and the events (optional recorders)


1. CUBE sends a mid-call RE-INVITE with any of the following changes:

• Media change

• XML change without any change in media

• Change in media and XML

• Refresh invite

2. CUBE Media Proxy sends the RE-INVITE to the primary recorder only.

When there is no change in the SDP, invite is not triggered toSPREC-Based CUBE Media Proxy.

Note

Mid-call session refresh

1. CUBE sends a mid-call RE-INVITE with direction change in SDP.


3. The primary recorder sends a200OK response to CUBEMedia Proxy, whichsends this response to CUBE.


Mid-call direction change

1. CUBE sends a mid-call RE-INVITE with a codec change in SDP.


3. The primary recorder sends a 200OK response for the codec change to CUBEMedia Proxy, which sends this response to CUBE.



Mid-call codec changewith a 200OK from theprimary recorder



3. The primary recorder sends a 488 error response for the codec change toCUBE Media Proxy, which sends this response to CUBE.


Mid-call codec changewith failure status of theprimary recorder

CUBE Media Proxy31





3. The primary recorder sends a 200OK response for the codec change to CUBEMedia Proxy, which sends this response to CUBE.


5. Two of the recorders send a 488 error response for the codec change toCUBE Media Proxy and the remaining recorders respond with a 200OK.


Mid-call codec changewith failure status of therecorders

When a mandatory recorder is configured, SIPREC-Based CUBEMedia Proxy supports the mid-call featuresgiven in the following table:

Table 8: Details of Mid-Call Scenarios and the events (mandatory recorder)

Events in the Mid-Call ScenarioMid-Call Scenario(mandatory recorder)

1. CUBE sends a mid-call RE-INVITE with any of the SDP changes.


3. The primary recorder sends a 488 error response or 503 error response forthe SDP change to CUBEMedia Proxy, which sends this response to CUBE.


Mid-call SDP changewithfailure status of themandatory recorder

1. CUBE sends a mid-call RE-INVITE with any of the SDP changes.


3. The primary recorder sends a 200OK response for the SDP change to CUBEMedia Proxy, which sends this response to CUBE.


5. One of the recorders responds with a 488 error response for the SDP changeto CUBE Media Proxy and the remaining recorders respond with a 200OK.

6. CUBE Media Proxy sends a BYE to the failed recorder and disconnects thesame.

Mid-call SDP changewithfailure status of therecorders

CUBE Media Proxy32


Secure Recording of Secure CallsCUBE Media Proxy using Unified CM NBR supports secure recording of secure calls. Following are theevents that are involved in forking of a secure recording request:

1. CUBE Media Proxy receives a secure recording request from Unified CM over TLS transport throughSIP INVITE with SDP body containing SRTP crypto attributes.

2. CUBE Media Proxy enters SRTP-SRTP passthrough mode and sends the secure recording request to theprimary recorder through SIP INVITE with SDP containing crypto attributes.

3. It is not required to explicitly configure SRTP on the dial-peers towards the recorders. TLS configurationon the dial-peers from CUBE Media Proxy to the recorders must be done. For information on how toconfigure TLS on dial-peers to the recorders, see Configuring SIP TLS.

TLS trustpoints must be configured. For information on how to configure TLS trustpoints, see ConfiguringTLS Trustpoints.

Note

4. CUBEMedia Proxy offers all the crypto suites that are received fromUnified CM to the primary recorder.The crypto suite that is negotiated with the primary recorder is offered to the remaining recorders.

5. SRTP media packets are successfully forked to all the recorders.

CUBE Media Proxy supports SRTP media pass-through for SRTP. Hence the CUBE Media Proxy neverrejects the SRTP media packets.

TCP TLS is required for signaling.

Note

Support for High AvailabilityHigh availability feature ensures that the active recording sessions are preserved whenever CUBE MediaProxy experiences an outage. Stateful Switchover (SSO) preserves the recording sessions and postswitchoverteardown of recording sessions. When a redundant standby CUBE Media Proxy is present, the recordingsessions continue to be active even after the active CUBEMedia Proxy goes down. The standby CUBEMediaProxy becomes active and services new recording requests.

CUBEMedia Proxy using Unified CMNBR and SIPREC-based CUBEMedia Proxy support high availability.

CUBE Media Proxy does not support ISSU (upgrade) from legacy CUBE versions.Note

In a recording session, the call-leg with a primary recorder and forked call-leg with the remaining recordersare checkpointed at the standby CUBEMedia Proxy. If the active CUBEMedia Proxy goes down, the standbydevice ensures that the forking call is active, and is able to exchange further transactions between the recordersand Unified CM (CUBE Media Proxy using Unified CM NBR) or CUBE (SIPREC-based CUBE MediaProxy). There is no change in the number of call-legs on the active CUBE Media Proxy and standby CUBE

CUBE Media Proxy33

CUBE Media ProxySecure Recording of Secure Calls

https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-border-element/200104-SIP-TLS-and-SRTP-RTP-internetworking-on.html

https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-border-element/200614-Configure-and-Troubleshoot-Enterprise-CA.html

https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-border-element/200614-Configure-and-Troubleshoot-Enterprise-CA.html

Media Proxy. The Active and Standby devices must have the same configurations for checkpointing to happencorrectly.

CUBE Media Proxy using Unified CM NBR and SIPREC-based CUBE Media Proxy support Box-to-Boxhigh availability and Inbox high availability with up to five recorders.

The following conditions and restrictions apply to the current implementation of SSO in CUBEMedia Proxyusing Unified CM NBR and SIPREC-based CUBE Media Proxy:

• Checkpointing is not done on the call-leg that is in the middle of a transaction.

• High availability is supported for all midcall transactions that include REINVITE, UPDATE, or BYEfromUnified CM (CUBEMedia Proxy using Unified CMNBR) or CUBE (SIPREC-based CUBEMediaProxy). Checkpointing is done after the completion of midcall transactions. Checkpointing is not doneif the SSO happens when the midcall transactions are in progress.

• Checkpointing is done only for the recorders that were successfully connected before the SSO.

• BYE received from any of the recorders is checkpointed.

The following conditions and restrictions apply to the current implementation of SSO in CUBEMedia Proxyusing Unified CM NBR:

• When one of the optional recorders sends BYE, CUBE Media Proxy sends an INFO message to UnifiedCMwith the updated status of all the recorders. Checkpointing for the recorder status happens only afterreceiving a 200OK response from Unified CM for the INFO message. Checkpointing is not done if theSSO happens after receiving the BYE from the recorder and before receiving a 200OK response for theINFO message from Unified CM.

• INFOmessages that indicate the status change of the recorders are checkpointed after response is receivedfor the corresponding INFO message.

• Metadata, SRTP context, and common Session ID used across all the five recorders are checkpointed.

The following conditions and restrictions apply to the current implementation of SSO in SIPREC-based CUBEMedia Proxy:

• Common Session ID used across all the five recorders are checkpointed.

• Metadata is not checkpointed.

You can use the following show commands to monitor the recording sessions on the active and the standbyinstances of CUBE Media Proxy:

• show call active voice compact

• show voip rtp connections

• show voip recmsp session

Media LatchBy default, CUBE Media Proxy using Unified CM NBR does source address validation to check if the IPaddress and port details that are received in the UDP header of the RTP or SRTP packets, matches with thedetails in the SDP sent by the SIP User Agent. The packets without matching IP address and port are dropped.

CUBE Media Proxy34

CUBE Media ProxyMedia Latch

In a typical SCCP-based BiB recording using Unified CMNBR CUBEMedia Proxy , Unified CM first sendsan SDP with the IP address and a dummy port to the CUBE Media Proxy to get the capabilities of CUBEMedia Proxy. Unified CM then sends this SDP to the SCCP phone. The CUBE Media Proxy does not knowthe vBiB IP address and port details of the SCCP phone. In these call flows, the IP address and port detailsin the media packets that are sent from vBiB of the SCCP phone to SCCP phone, are different from the IPaddress and port details in the packets that are sent from Unified CM to the CUBE Media Proxy.

Media Latching is enabled on Unified CM NBR CUBE Media Proxy by default so that the CUBE MediaProxy learns the remote IP address and port details from the UDP transport header of the first RTP or SRTPpacket. Media latching is turned on for every call that flows through the CUBE Media Proxy, and works forinitial and mid-call scenarios. Media Latching is enabled on the inbound leg (Unified CM leg), such that themedia packets are accepted even if they are sent from a source IP address and port that is different from theIP address that is advertised in the SDP.

CUBE Media Proxy35


CUBE Media Proxy36


Documents

CUBE Media Proxy - Cisco · media-recording proxy [dial-peer-tag1 dial-peer-tag2 dial-peer-tag3 dial-peer-tag4 dial-peer-tag5] Example: Step4 Note Youcanspecifymaximumoffivedial-peertags