[cisco-voip] Best practices for a 7936?
Jim McBurnett
jim at tgasolutions.com
Wed Aug 16 19:56:11 EDT 2006
if you have a spare system laying around, add a second NIC to it plug
that system into the switch in the closet where the 7936 exists..
span the 36 port to the second card on the switch to the second NIC on
the monitor box.
then using Ethereal you can almost play back the packets..
I had a similiar issue on another vendor's IPT and we found that the
packets were leaving with the wrong QOS and getting dropped....
make sure it is not a layer 2 issue also....
Later,
J
________________________________
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Jonathan
Charles
Sent: Wednesday, August 16, 2006 2:55 PM
To: Ryan LaTorre
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Best practices for a 7936?
Yeah, since the 7935/36 are not made by Cisco, they tend to not do CDP
very well.
I have found that they have a great tendency to pickup an IP on the data
VLAN if the switchport is not configured explicitly as an access port on
the voice vlan.
It just simplifies everything.
Jonathan
On 8/16/06, Ryan LaTorre <rlatorre at unislumin.com > wrote:
Going back a little while to firmware 3.3(5) or so, I also
experienced
one-way audio in some cases. What worked for me was to remove
the
access vlan/voice vlan configuration on the switchport and
configure
just a standard access port on the voice vlan.
-Ryan
-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Robert
Kulagowski
Sent: Wednesday, August 16, 2006 1:48 PM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] Best practices for a 7936?
I've got a site where 7936's seem to have one-way audio issues;
after a
call is made, the other side can hear outbound audio, but we
can't hear
them.
The 7936's are running 3.3(11), which is the latest firmware.
Looking at the forums on Cisco, some solutions were 1) Hardcode
the IP
address on the phone, since there appear to be issues when the
DHCP
server reboots 2) Hardcode the speed and duplex on the phone
and the
switchport to 100/FDX.
Of course it only fails when there's a critical call that needs
to
happen, and our solution is to reboot the phone, but that's not
viable
long term. And once we get to this point, where the phone is
only
working one-way, calling TAC so they can troubleshoot why it's
happening
is a non-starter, because the conference call _has_ to happen.
Anyone else experiencing these issues with 7936's?
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
Attention:
Privileged/Confidential Information may be contained in this
message. Disclosure to any person other than the named recipient is
unauthorized. If you are not the intended recipient, please delete all
copies of this information and kindly notify the sender by reply email.
Opinions, conclusions and other information in this message that do not
relate to the official business of UNIS LUMIN Inc. shall be understood
as neither given nor endorsed by it. UNIS LUMIN Inc. and any of its
subsidiaries reserve the right to monitor all e-mail communications
through its networks. Thank you.
_______________________________________________
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/20060816/ada134aa/attachment-0001.html
More information about the cisco-voip
mailing list