[cisco-voip] Voice recording issue

Tim Smith smithsonianwa at gmail.com
Mon Oct 18 01:19:54 EDT 2010


haha..

Sorry just had CCM 4.1 on my brain!

Minute I sent it, I realised you are on CME.

I am assuming it is actually working off the same principle though.

Cheers,

Tim

On Mon, Oct 18, 2010 at 4:18 PM, Tim Smith <smithsonianwa at gmail.com> wrote:

> I'm not familiar with this particular product.
>
> But my guess is that if it is 4.1 CCM, it is probably based off packet
> capturing the signalling and media off the wire.
>
> So usually they sniff the SCCP and this signalling traffic is used to build
> tables of extension numbers to device IP addresses for instance.
>
> Typically, in your recording software you then select which extensions to
> record. The software typically then applies filters to it's packet capturing
> process to exclude non-interesting traffic.
>
> In terms of recording, it also uses the SCCP sniffing to figure out when a
> call is happening, and who is involved, and therefore which RTP media
> packets to pluck off the wire and put into a recording file.
>
> So recorder placement, and what traffic you have spanning to it, can be
> important. i.e. you probably dont want to capture duplicate packets.
>
> This is how it all used to work before SIP forking etc. Since you are on
> 4.1 think this is off the table anyway.
>
> The key thing from the CM perspective is to make sure the recorders have
> visibility of both the SCCP and RTP packets required, and as you know these
> take different paths sometimes.
>
> These products typically use common components such as WINPCAP (same as
> used in Ethereal and Wireshark).
>
> As Ahmed says, it does sound like a software issue on their side.
>
> The fact that it is crossing calls is strange, because it means their
> system, is taking audio from other conversations that it is not supposed to
> be listening to. i.e. Not correlating the media streams and correct involved
> call parties.
>
> Hope that helps a bit.
>
> Cheers,
>
> Tim
>
> On Sat, Oct 16, 2010 at 5:02 PM, Tahir Uddin <tahir.uddin at riyadbank.com>wrote:
>
>>  Thanks Ahmed,
>> Could this be a version incompatibility issue, we are running CM 4.1 while
>> the Etalk software is one of the latest versions.
>> Also, are there extenion numbers or other info in the wav files that it
>> might not be able to decipher. How does it identify the packets belonging to
>> one conversation?
>>
>> Regards
>>
>>
>> Tahir Uddin
>> Assistant Vice President / Information Technology Officer
>> Information Technology Division - Mgmt.
>> Information Technology Division
>> Phone: +966-1-276-3000 ext. 5305
>> Email: tahir.uddin at riyadbank.com
>>
>> **
>> **
>>
>>
>>
>>  ------------------------------
>> *From:* Ahmed Elnagar [mailto:ahmed_elnagar at rayacorp.com]
>> *Sent:* Wednesday, October 13, 2010 6:50 PM
>> *To:* Tahir Uddin
>> *Cc:* voyp list
>> *Subject:* RE: [cisco-voip] Voice recording issue
>>
>>  It must be a problem in the recording servers in interpreting the
>> sniffed voice streams and reconstructing the wav files, I saw this problem a
>> lot in other product and every time it happen the vendor has to change their
>> code!!!
>>
>>
>>
>>  Best Regards;
>>
>>   Ahmed Elnagar
>>
>>   Senior Network PS Engineer
>>
>>   Mob: +2019-0016211
>>
>>   CCIE#24697 (Voice)
>>
>>  [image: ccie_voice_large.gif]
>>
>>
>>
>> *From:* cisco-voip-bounces at puck.nether.net [mailto:
>> cisco-voip-bounces at puck.nether.net] *On Behalf Of *Tahir Uddin
>> *Sent:* Wednesday, October 13, 2010 4:25 PM
>> *To:* voyp list
>> *Subject:* [cisco-voip] Voice recording issue
>>
>>
>>
>>
>>
>>
>>
>> Hi,
>>
>> We have call manager express and Etalk recorders
>>
>> We have an issue where the recording files for each call is getting mixed
>> up. When agent A talks to customer A and agent B talks to customer B, in the
>> recording files, we hear agent A interlaced with customer B. Has anyone come
>> across this issue.
>>
>> I am probably not providing enough information on this, just wanted to get
>> an initial take to start out.
>>
>>
>>
>> Regards
>>
>> Tahir
>>
>> ************************************************************************************************************************************
>> This email and any files transmitted with it are confidential and intended
>> solely for the use of the individual or entity to whom they are addressed.
>> Please note that any views or opinions presented in this email are solely
>> those of the author and do not necessarily represent those of Riyad Bank.
>> Finally, the recipient should check this email and any attachments for the
>> presence of any viruses. Riyad Bank accepts no liability for any damage
>> caused by any virus / error transmitted by this email.
>> ************************************************************************************************************************************
>>
>>
>> Disclaimer: NOTICE The information contained in this message is
>> confidential and is intended for the addressee(s) only. If you have received
>> this message in error or there are any problems please notify the originator
>> immediately. The unauthorized use, disclosure, copying or alteration of this
>> message is strictly forbidden. Raya will not be liable for direct, special,
>> indirect or consequential damages arising from alteration of the contents of
>> this message by a third party or as a result of any malicious code or virus
>> being passed on. Views expressed in this communication are not necessarily
>> those of Raya.If you have received this message in error, please notify the
>> sender immediately by email, facsimile or telephone and return and/or
>> destroy the original message.
>> ************************************************************************************************************************************
>> This email and any files transmitted with it are confidential and intended
>> solely for the use of the individual or entity to whom they are addressed.
>> Please note that any views or opinions presented in this email are solely
>> those of the author and do not necessarily represent those of Riyad Bank.
>> Finally, the recipient should check this email and any attachments for the
>> presence of any viruses. Riyad Bank accepts no liability for any damage
>> caused by any virus / error transmitted by this email.
>> ************************************************************************************************************************************
>>
>>
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20101018/07c2f7cc/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 1801 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20101018/07c2f7cc/attachment.jpg>


More information about the cisco-voip mailing list