[cisco-voip] Conference Initiator Unable to be Heard - On-Netcalls

Fri Nov 4 12:34:03 EST 2005

I have skinny fixup ON. 

And obviously the pix vpn tunnels were not an ideal solution, or my idea
for that matter. Now that mgt wants to do video conferencing - and our
largest office is having quality problems, the people who decided this
are realizing the limitations and coming around. We're going to MCI's
PIP network v. soon. 

> -----Original Message-----
> From: Wes Sisk [mailto:wsisk at cisco.com]
> Sent: Friday, November 04, 2005 12:01 PM
> To: Jason Evans; Kevin Thorngren
> Cc: cisco-voip at puck.nether.net
> Subject: RE: [cisco-voip] Conference Initiator Unable to be Heard -
On-
> Netcalls
> 
> pix vpn interesting.  do you have sccp fixup on or off?
> 
> -----Original Message-----
> From: cisco-voip-bounces at puck.nether.net
> [mailto:cisco-voip-bounces at puck.nether.net]On Behalf Of Jason Evans
> Sent: Friday, November 04, 2005 11:18 AM
> To: Kevin Thorngren
> Cc: cisco-voip at puck.nether.net
> Subject: RE: [cisco-voip] Conference Initiator Unable to be Heard -
> On-Netcalls
> 
> 
> Thanks Kevin, responses inline ...
> 
> > -----Original Message-----
> > From: Kevin Thorngren [mailto:kthorngr at cisco.com]
> > Sent: Thursday, November 03, 2005 7:19 PM
> > To: Jason Evans
> > Cc: CiscosupportUpuck <cisco-voip at puck.nether.net>
> > Subject: Re: [cisco-voip] Conference Initiator Unable to be Heard -
> On-Net
> > calls
> >
> > It sounds like the audio from the phone is not making it to the CCM
> > Conference Bridge.  Do you have diverse routes between the remote
> sites
> > and the CCM?
> 
> No, it's a pix to pix tunnel from the 2 sites. The routing is fine it
> appears. I verified connectivity from the Voice subnet in DC to the
CM's
> in NY.
> >
> > Can you ping the phone with the problem from the CCM?
> 
> Yes, I can.
> 
> >
> > Once in a problem state try hitting the "?" button twice quickly.
> This
> > will bring up the stats for the call.  Is the phone transmitting?
> 
> I will test this with the DC user as soon as I can. He's not around
now.
> 
> >
> > You can also web into the IP Address of the phone, ie, http://<ip
> > address>.  On the left hand menu select the first audio stream.  You
> > can verify the IP Address and port of the destination.  Does this
look
> > correct?
> 
> When I first looked at this, the remote address of the user was the
> PRI/MGCP Gateway - so I assume he had made an external call. I looked
a
> few minutes later and the Remote address was the Unity VM server. So,
I
> guess, yes the addresses look correct.
> >
> > Do you have any firewalls between the remote phones and the
Conference
> > Bridge?
> 
> Yes, but the ACL's on the Pixes allow for full connectivity between
the
> remote subnets and the NY voice subnets. I also watched both firewalls
> during a problem to confirm that no packets were being dropped or not
> NAT'ed.
> 
> >
> > Kevin
> >
> > On Nov 3, 2005, at 5:46 PM, Jason Evans wrote:
> >
> > > Thanks for the response Wes:
> > >
> > > 1. I'm using the CM Conference Bridge Software - default Device
> Pool,
> > > no
> > > Location configured.
> > > 2. All the routing seems to be fine - I double checked, and
nothing
> is
> > > getting blocked on the firewalls. What bothers me is that another
> user
> > > in DC - same subnet, phone, firmware load - can do it, but this
guy
> > > can't. And now there seems to be a user in Austin with the same
> > > problem.
> > >
> > >
> > > jason
> > >
> > >> -----Original Message-----
> > >> From: Wes Sisk [mailto:wsisk at cisco.com]
> > >> Sent: Thursday, November 03, 2005 5:08 PM
> > >> To: Jason Evans; cisco-voip at puck.nether.net
> > >> Subject: RE: [cisco-voip] Conference Initiator Unable to be Heard
-
> > > On-Net
> > >> calls
> > >>
> > >> Given WAN, I would check a couple of things:
> > >>
> > >> 1. CM builtin conference bridge is g711 only, so you're either
> > > invoking
> > >> transcoder or using hardware conferencing - which?
> > >> 2. check all the IP Routes and default gateway from your hardware
> > >> conference
> > >> device or transcoder.
> > >>
> > >> /Wes
> > >>
> > >> -----Original Message-----
> > >> From: cisco-voip-bounces at puck.nether.net
> > >> [mailto:cisco-voip-bounces at puck.nether.net]On Behalf Of Jason
Evans
> > >> Sent: Thursday, November 03, 2005 2:39 PM
> > >> To: cisco-voip at puck.nether.net
> > >> Subject: [cisco-voip] Conference Initiator Unable to be Heard -
> On-Net
> > >> calls
> > >>
> > >>
> > >> Hi,
> > >>
> > >> Certain users over the WAN are unable to use the Ad-hoc
> conferencing
> > >> feature because when they press the "Confrn" button to join the 3
> > >> parties, none of the parties can hear the initiator.
> > >>
> > >> For instance: User A in DC dials user B at extension 1123 in NYC,
> and
> > >> both parties can converse. User A then presses the "confrn"
button
> and
> > >> gets User C in NYC at extension 4500 - User A and User C can also
> > >> converse normally. However, when User A presses the "confrn"
button
> > >> again to join the parties, User A can hear Users B and C, Users B
> and
> > > C
> > >> can hear and speak normally, BUT Users B and C can NOT hear User
A.
> > >>
> > >> Additionally, I tested this scenario with another user in the DC
> > >> location and things worked fine. So I have 2 phones on the same
WAN
> > >> segment, with the same profile and rules - 1 works and 1 does
not.
> The
> > >> only discrepancy between these 2 instruments is that the one
which
> is
> > >> having the problem is a shared line (with a NYC appearance and a
DC
> > >> appearance in both places) and one has only a single appearance
in
> DC.
> > >>
> > >> I did a run through bugs and didn't see anything pop out, and
most
> > >> previous postings on "one-way" voice have to deal with calls
going
> out
> > >> of a Gateway. Any ideas or suggestions would be great!
> > >>
> > >> Thanks - Jason
> > >>
> > >> _______________________________________________
> > >> cisco-voip mailing list
> > >> cisco-voip at puck.nether.net
> > >> https://puck.nether.net/mailman/listinfo/cisco-voip
> > >>
> > >
> > >
> > > _______________________________________________
> > > cisco-voip mailing list
> > > cisco-voip at puck.nether.net
> > > https://puck.nether.net/mailman/listinfo/cisco-voip
> > >
> >
> 
> 
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
> 