[cisco-voip] User Inadvertently Reaches Intercom

Norton, Mike mikenorton at pwsd76.ab.ca
Mon Apr 26 13:26:26 EDT 2010


Another thing... did she actually hear the person's voicemail greeting? Or did she just hear the intercom system's pre-announce tone, assume it was a voicemail beep, and start talking? If it was the latter, then you might just accidentally be matching the wrong route pattern somewhere.

--
Mike Norton
I.T. Support
Peace Wapiti School Division No. 76
Helpdesk: 780-831-3080
Direct: 780-831-3076


From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of David Zhars
Sent: April-26-10 11:01 AM
To: Peter Slow
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] User Inadvertently Reaches Intercom

What I meant was we did not hear her dialing the phone, but we heard her leaving a message for this person (since the person dialed did not answer).  All I can think is the cell phone she was calling was forwarded to a *34 speed-dial or something, and somehow we picked it up.

It was so bizarre because when it happened, we called my user and told her what happened.  She figured the call didn't go through, so she placed the call again, and again, we heard her leaving the message over the intercom!  She has since tried calling other cells and POTS and none of those have gone over the intercom.

When I look at recently dialed calls, all I see are the cell # she is calling (which has no 3 or 4 in it!!)  I have never seen anything like this one, but like you said, CDR might be a good place to start.

On Mon, Apr 26, 2010 at 11:24 AM, Peter Slow <peter.slow at gmail.com<mailto:peter.slow at gmail.com>> wrote:
the first thing i would do is go to the phone and look at the placed
calls in the call history. have you done this?

CUCM isnt going to use where teh last call was routed to  as the
destination for the next call or anything like that. assuming your
user didnt do something like hit the conference button to make the new
call, the new call should have been completely independent of the last
call.

When you say  "heard the whole thing over the intercom," do you mean
you heard her try to dial the called party, or do you mean that you
heard both parties talking with each other over the PA?

you would normally troubleshoot something like this with traces from
the callmanager and debugs from the gateway, but depending on what
actually ocurred, you might be able to get useful info from the CDR
records.

-Peter


On Mon, Apr 26, 2010 at 8:51 AM, David Zhars <dzhars at gmail.com<mailto:dzhars at gmail.com>> wrote:
> I setup an intercom attachment to an FXS port.  This morning, one of my
> users placed a phone call and we heard the whole thing over the
> intercomm...Is it my setup?
>
> The 2801 with FXS is in H323 mode, here's the portion for the intercom code
> (we want people to dial *34 for the intercom):
>
> dial-peer voice 55 pots
>  description Paging for Fire
>  destination-pattern *34
>  port 0/2/0
>  forward-digits all
>
> In CCM (4.1(3)) under Route Pattern, there is a box that says "Provide
> Outside Dial tone" and that has a check mark in it.  Is there anyway this
> could be setup that if you dial the overhead, we also let you dial a number
> and keep it going over the intercom?
>
> How would I trace what she did do in CCM?  I think I have to wait until the
> next day because CCM won't finalize the database update until the next day
> (it's been a while since I've had to do one of these!)
>
> Thanks to anyone who can offer some insight.
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net<mailto: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/20100426/c533ff8c/attachment.html>


More information about the cisco-voip mailing list