Ditto VR Resources


Ditto VR | Cisco CUBE SIPREC Configuration


This page outlines the basic operations to enable SIPREC recording with Cisco CUBE and the Ditto VR SIPREC cloud platform. Review the Ditto VR Admin Handbook for provisioning on the Ditto VR Cloud Platform.

Ditto VR Cisco CUBE SIPREC Diagram
Above: As calls pass through the Cisco CUBE a forked copy of the call is directed to Ditto for Recording using the SIPREC protocol..

This configuration example assumes that all calls are to be recorded passing through the CUBE. If you wish to use selective calling please consult your Cisco technical personnel.

Step 1. Enter the configuration mode.

Router> enable

Router# configure terminal


Step 2. Assign a spare dial-peer as the SIPREC recorder profile.

Router # show dial-peer voice

The above command will display all the dial-peers on the CUBE. You will need to assign a dial-peer number that is spare. We recommend something in the range of 7800-8000. We will use 7900 for this tutorial and is assigned as dummy dial-peer for the Ditto VR recorder. 200 is the recorder profile tag.

Router (config)# media profile recorder 200

Router (cfg-mediaprofile)# media-type audio

Router (cfg-mediaprofile)# media-recording 7900

Router (cfg-mediaprofile)# exit


Step 3. Create a Media Class that is assigned to the SIPREC recorder.

Router (config)# media class 100

Router (cfg-mediaclass)# recorder profile 200 siprec

Router (cfg-mediaclass)# exit


Step 4. Create a dial-peer that points to the Ditto VR Cloud Platform.

Router (config)# dial-peer voice 7900 voip

Router (config-dial-peer)# description Ditto VR SIPREC Recording

Router (config-dial-peer)# media class 10

Router (config-dial-peer)# destination-pattern 88888

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

Router (config-dial-peer)# session target ipv:1.2.3.4:5060

Router (config-dial-peer)# session transport tcp

Router (config-dial-peer)# exit

The IP 1.2.3.4 session target above refers to the Ditto VR SIPREC Gateways. These IP addresses can be resolved by pinging of either:

• blanc.ditto-vr.com

• dinara.ditto-vr.com

Note: There is no affinity to which Ditto VR Gateway you choose.


Step 5.Assign the recorder profile to an existing dial-peer.

Verify which dial-peers are in operation and evaluate which peers you wish to assign for SIPREC recording:

Router# show dial-peer voice

dial-peer voice 220 voip

description ITSP Carrier Peer

session protocol sipv2

incoming called-number .

media-class 100



Compatibility. Cisco Restrictions For CUBE SIPREC Recording.

• Any media service parameter change via Re-INVITE or UPDATE from recording server is not supported. For example, hold-resume or any codec changes

• IPv6-to-IPv6 call recording

• IPv6-to-IPv4 call recording if the recording server is configured on the IPv6 call leg

• Calls that do not use Session Initiation Protocol (SIP). Must be a SIP-to-SIP call flow

• Flow-around calls

• Session Description Protocol (SDP) pass-through calls

• Real-time Transport Protocol (RTP) loopback calls

• High-density transcoder calls

• Secure Real-time Transport Protocol (SRTP) passthrough calls

• SRTP-RTP calls with forking for SRTP leg (forking is supported for the RTP leg)

• Multicast music on hold (MOH)

• Mid-call renegotiation and supplementary services like Hold/Resume, control pause, and so on are not supported on the recorder call leg

• Recording is not supported if CUBE is running a TCL IVR application with the exception of survivability.tcl, which is supported with SIPREC based recording

• Digital Signal Processing (DSP) resources are not supported on forked legs



Download PDF Version