Showing results for 
Search instead for 
Did you mean: 
Walkthrough Wednesdays

Multiple RTP packets recording

This document was generated from CDN thread

Created by: Ahmad Yaseen on 16-01-2012 09:40:59 AM
Dear All,
My name is Wissam and I work at a company that develop a software called Speechlog that records calls from CUCM. One of the techniques we use is using SIP trunk to capture the voice RTP packets from either the the extention or from the CM (if MTP is set).  Is there a way to secure redundancy from the CM that insures sending multiple instances of the RTP packet one for each server. or should we provide a proxy or redundancy handling on our side (like nice or witness do).
referencing the flooing from Cisco's Help:
<h2 class="pHeading2">
Create Recorder Redundancy

<a name="wp1067350"> </a>

Many recorders have built-in proxy and redundancy functionalities, for example, Nice/Witness recorders.

You can also use the following mechanism to achieve recorder redundancy:

<li>Use the SRV record for the recorder destination address in SIP trunk configuration.</li>

<a name="wp1067366"> </a>

<li>Use multiple
recorders for redundancy and load balance. Create a SIP trunk for each
recorder; create a route list to include the route groups that have
individual SIP trunks as a member.</li>

Subject: RE: Multiple RTP packets recording
Replied by: David Staudt on 20-01-2012 05:03:36 PM
Not aware of any feature that provides multiple simultaneous streams for the same call.  The redundancy approaches mentioned involve ensuring that if one SIP trunk connection is down/unavailable, that another will be tried:
- DNS SRV - provision the SIP trunk with DNS name instead of IP, which has multiple SRV records (each pointing to a backup recorder instance) for redundancy:
- UCM route list - provision separate SIP trunks to primary/backup recorder instance, and configure UCM dial plan so that the recording target DN accesses a Route List which will route the call to the first available recorder
Content for Community-Ad

This widget could not be displayed.