haha..<div><br></div><div>Sorry just had CCM 4.1 on my brain!</div><div><br></div><div>Minute I sent it, I realised you are on CME.</div><div><br></div><div>I am assuming it is actually working off the same principle though.</div>
<div><br></div><div>Cheers,</div><div><br></div><div>Tim</div><div><br><div class="gmail_quote">On Mon, Oct 18, 2010 at 4:18 PM, Tim Smith <span dir="ltr"><<a href="mailto:smithsonianwa@gmail.com">smithsonianwa@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div>I'm not familiar with this particular product.</div><div><br></div><div>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.</div>
<div><br></div><div>
So usually they sniff the SCCP and this signalling traffic is used to build tables of extension numbers to device IP addresses for instance.</div><div><br></div><div>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.</div>
<div><br></div><div>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.</div>
<div><br></div><div>So recorder placement, and what traffic you have spanning to it, can be important. i.e. you probably dont want to capture duplicate packets.</div><div><br></div><div>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.</div>
<div><br></div><div>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.</div><div><br></div>
<div>These products typically use common components such as WINPCAP (same as used in Ethereal and Wireshark).</div><div><br></div><div>As Ahmed says, it does sound like a software issue on their side.</div><div><br></div>
<div>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.</div>
<div><br></div><div>Hope that helps a bit.</div><div><br></div><div>Cheers,</div><div><br></div><div>Tim<br><br><div class="gmail_quote"><div><div></div><div class="h5">On Sat, Oct 16, 2010 at 5:02 PM, Tahir Uddin <span dir="ltr"><<a href="mailto:tahir.uddin@riyadbank.com" target="_blank">tahir.uddin@riyadbank.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div></div><div class="h5">
<div lang="EN-US" style="word-wrap:break-word" vlink="purple" link="blue">
<div><span><font face="Arial" color="#0000ff" size="2">Thanks
Ahmed,</font></span></div>
<div><span><font face="Arial" color="#0000ff" size="2">Could
this be a version incompatibility issue, we are running CM 4.1 while the Etalk
software is one of the latest versions.</font></span></div>
<div><span><font face="Arial" color="#0000ff" size="2">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?</font></span></div>
<div><span><font face="Arial" color="#0000ff" size="2"></font></span> </div>
<div><span><font face="Arial" color="#0000ff" size="2">Regards</font></span></div>
<div> </div><br>
<p><font face="Verdana" color="black" size="2">Tahir Uddin<br>Assistant Vice President
/ Information Technology Officer<br>Information Technology Division -
Mgmt.<br>Information Technology Division<br>Phone: +966-1-276-3000 ext.
5305<br>Email: <a href="mailto:tahir.uddin@riyadbank.com" target="_blank">tahir.uddin@riyadbank.com</a><br><br><b><font face="verdana" color="green" size="2"></font></b><br><b><font face="verdana" color="green" size="2"></font></b></font></p>
<br>
<div> </div><br>
<div lang="en-us" dir="ltr" align="left">
<hr>
<font face="Tahoma" size="2"><b>From:</b> Ahmed Elnagar
[mailto:<a href="mailto:ahmed_elnagar@rayacorp.com" target="_blank">ahmed_elnagar@rayacorp.com</a>] <br><b>Sent:</b> Wednesday, October 13, 2010
6:50 PM<br><b>To:</b> Tahir Uddin<br><b>Cc:</b> voyp list<br><b>Subject:</b> RE:
[cisco-voip] Voice recording issue<br></font><br></div><div><div></div><div>
<div></div>
<div>
<p class="MsoNormal"><span style="font-size:11pt;color:#1f497d">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!!!</span></p>
<p class="MsoNormal"><span style="font-size:11pt;color:#1f497d"> </span></p>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:10pt;color:#1f497d"> </span><span style="font-size:10.5pt;color:#1f497d">Best
Regards;</span></p>
<p class="MsoNormal" style="background:white"><span style="font-size:10.5pt;color:#1f497d">
Ahmed Elnagar</span></p>
<p class="MsoNormal" style="background:white"><span style="font-size:10.5pt;color:#1f497d">
Senior Network PS Engineer</span></p>
<p class="MsoNormal" style="background:white"><span style="font-size:10.5pt;color:#1f497d">
Mob: +2019-0016211</span></p>
<p class="MsoNormal" style="background:white"><span style="font-size:10.5pt;color:#1f497d">
CCIE#24697 (Voice)</span></p>
<p class="MsoNormal" style="background:white"><span style="font-size:10.5pt;color:#1f497d"> <img height="63" alt="ccie_voice_large.gif" src="cid:114185905@16102010-055F" width="63"></span></p></div></div>
<p class="MsoNormal"><span style="font-size:11pt;color:#1f497d"> </span></p>
<div>
<div style="border-right:medium none;padding-right:0in;border-top:#b5c4df 1pt solid;padding-left:0in;padding-bottom:0in;border-left:medium none;padding-top:3pt;border-bottom:medium none">
<p class="MsoNormal"><b><span style="font-size:10pt">From:</span></b><span style="font-size:10pt">
<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>]
<b>On Behalf Of </b>Tahir Uddin<br><b>Sent:</b> Wednesday, October 13, 2010 4:25
PM<br><b>To:</b> voyp list<br><b>Subject:</b> [cisco-voip] Voice recording
issue</span></p></div></div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal"> </p></div>
<div>
<p class="MsoNormal"> </p></div>
<div>
<p class="MsoNormal"><span style="font-size:10pt;color:blue">Hi,
</span></p></div>
<div>
<p class="MsoNormal"><span style="font-size:10pt;color:blue">We have
call manager express and Etalk recorders</span></p></div>
<div>
<p class="MsoNormal"><span style="font-size:10pt;color:blue">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.
</span></p></div>
<div>
<p class="MsoNormal"><span style="font-size:10pt;color:blue">I am
probably not providing enough information on this, just wanted to get an initial
take to start out.</span></p></div>
<div>
<p class="MsoNormal"> </p></div>
<div>
<p class="MsoNormal"><span style="font-size:10pt;color:blue">Regards</span></p></div>
<div>
<p class="MsoNormal"><span style="font-size:10pt;color:blue">Tahir</span></p></div>
<p class="MsoNormal">************************************************************************************************************************************
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.
************************************************************************************************************************************
</p></div>
<div> </div>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. </div></div></div><div><div></div><div>
************************************************************************************************************************************
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.
************************************************************************************************************************************
</div></div><br></div></div>_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br></div>
</blockquote></div><br></div>