From: Tony H. (aamercado31@yahoo.com)
Date: Sat Nov 02 2002 - 18:43:45 GMT-3
From ip phone to 3com switch, there may be several
issues:
1. The CDP Mac address 0100.0ccc.cccc may causes
problems..my guess is spanning tree??
2. Auto-negotiation issue but I would suspect it
should be ok
3. Will 3com tagged ethernet frame thereby preserving
preserve the CoS field? this may be dependent on the
3com sw???
4. 3com Inline power issue which cisco has at -48?
The main issue is the 802.1Q. Setting trunk port,
you maybe be able to get away with the different
802.1Q tags or otherwise, you can have a default vlan
(no tag) and one tagged VLAN (say VlanID=200
for phones) which means everybody in the same VLAN or
use different ports on the switch (you need twice as
many switch ports then).
With the remote site question, I am assuming you have
the central site doing dhcp but you can also have the
remote router do dhcp with it pointing to the
tftp/callmanager server at the central site. If it is
a small site, then a dhcp router should be fine. If it
is a larger remote site, you can put in another
callmanager cluster but that would be getting away
from your central design to distributed design or,
like you said, you can manually program the phones
--- Nigel Taylor <nigel_taylor@hotmail.com> wrote:
> Yigit,
> Another consideration would be dependant
> on the size of the remote
> site. This would be a consideration in that if the
> remote site consist of
> let's say 50-100 users then it's possible that
> specific services like DNS,
> DHCP and login servers(a BDC) would be located at
> the remote site. This
> would also be in lieu of the bandwisth/SLAs on the
> WAN conection that exist
> between your remote and central site.
>
> Nigel
>
> ----- Original Message -----
> From: "Yigit Zorlu" <yzorlu@tepum.com.tr>
> To: "Armand D" <ciscoworks2001@yahoo.com>; "Tony H."
> <aamercado31@yahoo.com>; "Bob Usa"
> <boby2kusa@hotmail.com>;
> <tlarus@cox.net>; <ccielab@groupstudy.com>
> Sent: Saturday, November 02, 2002 1:57 AM
> Subject: RE: OT Probl relating to Interoperability
> of Cisco IP phones with
> non-Cisco switc
>
>
> > I think Tom's question was "How can we configure
> Cisco IP Phone in
> non-cisco switch ?" e.g. with 3Com switch. It has to
> be done in 3Com switch
> as well. I believe that's one of the main reasons
> Cisco started to
> push/promote 802.1q instead of ISL. I believe in
> that type of situation, it
> is better to configure static IP address of and the
> TFTP server address over
> the IP Phone manually. I will give a try this week.
> >
> > And another question comes into my mind. What
> happens do I have a
> Multi-site Centralized IPTEL topology in remote
> locations? How can remote
> site IP Phones reach DHCP server ? I think in that
> case also we need to
> manually configure the phones.
> >
> > Am I missing something?
> >
> > Yigit
> >
> >
> > -----Original Message-----
> > From: nobody@groupstudy.com
> [mailto:nobody@groupstudy.com]On Behalf Of
> > Armand D
> > Sent: Friday, November 01, 2002 11:07 PM
> > To: Tony H.; Bob Usa; tlarus@cox.net;
> ccielab@groupstudy.com
> > Subject: Re: OT Probl relating to Interoperability
> of Cisco IP phones
> > with non-Cisco switc
> >
> >
> > Ok. Let me see if I understand.
> >
> > Does this solutoin as you have described, allow
> for
> > the Class of Service bit field to be set ? which
> the
> > switch will treat the phone and the data endpoint
> > differentially ?
> >
> > Thanks,
> >
> > Armand
> >
> > --- "Tony H." <aamercado31@yahoo.com> wrote: > hi
> > >
> > > I have the opposite explanation (non ip phone to
> > > cisco
> > > switch)...maybe it will give you some insight.
> > >
> > > If the ip phone does not send CDP, then you will
> > > have
> > > problems in recognizing the voice VLAN:
> > >
> > > The workaround is to use DOT1Q trunking with the
> PC
> > > data frames as Untagged, while the Voice frames
> are
> > > Tagged with VLAN Headers.
> > >
> > > However you may (or may not need to configure
> the
> > > non-cisco ip phone) For instance in the Avaya,
> you
> > > probably need to configure the following:
> > > 802.1Q = on (default is probably off)
> > > Vlan ID = your voice vlan #
> > >
> > > On the Cat:
> > > set trunk to dot1Q
> > > set your vlans
> > > clear all unneeded vlans off the trunk
> > >
> > > For example on a CATIOS (ie 35xx/29xx)
> > >
> > > interface FastEthernetx/x
> > > switchport trunk encapsulation dot1q
> > > switchport trunk native vlan 200
> > > switchport mode trunk
> > > switchport voice vlan 100
> > > spanning-tree portfast
> > > no cdp enable
> > >
> > > This is what will happen:
> > >
> > > The PC traffic be treated as native (data)
> untagged
> > > while the ip phone (in this case Avaya) would
> tag
> > > voice traffic with the voice VLAN header info
> and
> > > send
> > > it (802.1Q) out the port to the Cat. It should
> pass
> > > on both tagged and untagged frames. The Cat will
> see
> > > both and do what it is suppose to do as a trunk
> port
> > > and segregate voice from data
> > >
> > > Hope it helps.
> > >
> > >
> > > --- Bob Usa <boby2kusa@hotmail.com> wrote:
> > > > It depends on what kind of platform. For
> > > > 3500XL/2900XL devices you will have
> > > > to set up the port/interface fro dot1q
> trunking
> > > and
> > > > set the native vlan for
> > > > the data vlan. Non-Cisco IP phone such as
> Avaya
> > > are
> > > > configure-able to send
> > > > vlan ID in their packet. For set command
> switches
> > > > such as Cat4K, Cat6Ks all
> > > > you have to do is set the regular vlan for
> data
> > > and
> > > > set the auxiliary vlan for
> > > > the voice vlan. This is done so you can
> plug-in a
> > > > PC to the IP Phones data
> > > > jack. I have been told that Avaya advice not
> to
> > > use
> > > > auxiliary vlan for now
> > > > since they have not tested but I find it to
> work
> > > > just fine. But you can also
> > > > trunk the port using dot1q and making the data
> > > vlan
> > > > the Native vlan. This
> > > > helps?
> > > >
> > > >
> > > > ----- Original Message -----
> > > > From: tlarus@cox.net
> > > > Sent: Thursday, October 31, 2002 9:17 AM
> > > > To: ccielab@groupstudy.com
> > > > Subject: Problem relating to Interoperability
> of
> > > > Cisco IP phones with
> > > > non-Cisco switches
> > > >
> > > > How do you set the operational VLAN and admin
> VLAN
> > > > on a Cisco IP Phone if the
> > > > switch you are connecting to network with does
> not
> > > > support CDP? Normally a
> > > > Cisco IP phone learns about what VLANs it is
> using
> > > > through CDP communication
> > > > with a Cisco switch.
> > > >
> > > > I wonder if you can have the CallManager tell
> the
> > > IP
> > > > Phone what VLANs it is
> > > > using. I have not found anything indiacting
> that
> > > > this can be done. Even better
> > > > would be being able to set the VLANs on the
> phone
> > > > itself.
> > > >
>
=== message truncated ===
This archive was generated by hypermail 2.1.4 : Tue Dec 03 2002 - 07:22:51 GMT-3