[cisco-voip] Weird call in VM..... Explain that?

[Scott Voll]

The call was from OUTSIDE our org.

it came in via a POTS line on our H323 GW and went to VM.  I really thing
that someone conferenced our number in by accident.

Scott

On Tue, Dec 6, 2011 at 10:54 AM, Chris Ward (chrward) <chrward at cisco.com>wrote:

> Assuming the CDR doesn’t show a conference call made to voicemail, can you
> go back into your CDRs and figure out which phone placed or received that
> call that was recorded in voicemail and then search for as many records as
> possible for that user and see if there were any abnormal call clearings or
> anything out of the ordinary. Doing the same for the GW might not be a
> terrible idea. Although, I am pretty sure CUC has that RTP stream
> protection so that it doesn’t accept streams from unknown sources.****
>
> ** **
>
> Any MTPs or anything like that in the call flows? Also, what is the
> firmware version on the 7961?****
>
> ** **
>
> +Chris****
>
> Hosted Collaboration Solution TME****
>
> ** **
>
> *From:* Scott Voll [mailto:svoll.voip at gmail.com]
> *Sent:* Tuesday, December 06, 2011 1:31 PM
> *To:* Chris Ward (chrward)
> *Cc:* cisco-voip at puck.nether.net
> *Subject:* Re: [cisco-voip] Weird call in VM..... Explain that?****
>
> ** **
>
> 2811 H323(15.1T) -- CM 7.1.5 -- (sccp) 7961 -- (non-sip) UC 8.5****
>
> ** **
>
> Scott****
>
> On Tue, Dec 6, 2011 at 9:32 AM, Chris Ward (chrward) <chrward at cisco.com>
> wrote:****
>
> I saw a case like this a long time ago when I was in TAC. Basically, a
> customer was reporting that they received VMs of entire conversations, in
> my case it was the conversation of a VP within the company, which was
> less-than-optimal for the customer.****
>
>  ****
>
> It turned out that when certain devices encounter a TCP connection failure
> (unregister) while streaming audio, they would forever stream an additional
> audio stream to that IP and port until the device was cold-rebooted. In
> this case it was a legacy VM device that DPA that wasn’t filtering out
> audio streams that were not from the current audio session and the 7970 the
> defect that when unregistered, would continue to send an additional audio
> stream (CSCsj99361).****
>
>  ****
>
> We were able to finally track down the bug by using CDR records and the
> voicemail to determine who’s phone we were hearing and then looking for
> that phone’s calls before the cross-talk was heard.****
>
>  ****
>
> So, let me ask, what are the details of this deployment? Voicemail system,
> phones in use, integration type, and versions for all.****
>
>  ****
>
> At any rate, this totally changed my perception that cross-talk is not
> possible in an IP environment. J****
>
>  ****
>
> +Chris****
>
> Hosted Collaboration Solution TME****
>
>  ****
>
> *From:* cisco-voip-bounces at puck.nether.net [mailto:
> cisco-voip-bounces at puck.nether.net] *On Behalf Of *Scott Voll
> *Sent:* Tuesday, December 06, 2011 12:20 PM
> *To:* cisco-voip at puck.nether.net
> *Subject:* [cisco-voip] Weird call in VM..... Explain that?****
>
>  ****
>
> We received a VM this morning when checking a branch VM box.****
>
>  ****
>
> Basically the VM sounded like a full conversation between two people
> (possible a bank being one side) and the whole conversation is there
> including MoH that is not ours either.  we are on the west coast and the
> call came in from Kansas.  we see the call in CDR's on CM.****
>
>  ****
>
> What the hey happened?  ideas?****
>
>  ****
>
> Only thing I can guess is that we got conferenced in, incorrectly, or the
> telco has some major issues.****
>
>  ****
>
> TIA****
>
>  ****
>
> Scott****
>
> ** **
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20111206/257a0f20/attachment.html>