Solved: Cisco 3550 6513 and Avaya4620

balla-zoltan · ‎02-18-2005

I have Cisco 3550 and 6513 switches on my network. We are testing VoIP with Avaya4620 phones. I configured the 6513s with voice vlan, configured the 3550 for voice as well. Here is one of the ports configuration;

interface FastEthernet0/38

switchport trunk encapsulation dot1q

switchport trunk native vlan 18

switchport mode trunk

switchport voice vlan 818

spanning-tree portfast

spanning-tree bpduguard enable

And here is one of the 6513's configuration;

ip dhcp pool VLAN818-pool

network 10.68.0.0 255.255.255.0

default-router 10.68.0.1

netbios-name-server 161.195.161.117 161.195.161.116

netbios-node-type h-node

dns-server 161.195.161.39 161.195.161.211

domain-name fss.aramark.com

option 176 ip 161.195.160.163

interface Vlan818

ip address 10.68.0.3 255.255.255.0

no ip redirects

ip route-cache flow

standby ip 10.68.0.1

standby preempt

!

Vlan 18 is the data vlan, we need to plug the PC into the phone. My problem is the phone never gets the IP address from the 6513. If I configure the phone with the VLAN ID 818, the voice vlan, then the phone gets the right gateway, and the subnet mask, but not the IP address. On the phone there are options such as CallSRV, FileSrv, some ports, etc. It seems like the phone cannot get to the tftp server since it never gets an IP address. Could anybody tell me if the Cisco switch configurations are right?

Thanks

kleo · ‎03-01-2005

glad it worked. The tftp is used mainly to upgrade the phone software aka firmware but there is a 46xxsettigns file that can be used to tweek the phone.Extention are assigned via avaya call server or as you did via extention mobility.

MUTE LOGOFF# or MUTE LOGON#

so you place the newest phone firmware and the 46xxsettings file in the tftp directory.

Newest phone firmware:

http://support.avaya.com/japple/css/japple?temp.documentID=210073&temp.productID=107755&temp.bucketID=108025&PAGE=Document

settings file:

http://support.avaya.com/japple/css/japple?temp.documentID=142911&temp.productID=107755&temp.bucketID=108025&PAGE=Document

View solution in original post

ebreniz · ‎02-25-2005

Did you check any debug commands that can be given to monitor DHCP request and reply.

debug dhcp details.

or show dhcp server.

balla-zoltan · ‎02-27-2005

The interesting part is that the phone gets an IP address for about two seconds. If I do sh ip dhcp bind I can see the IP address of the phone. At that point it wants to connect to the tftp server, but for some reason I can no longer ping the phone abd the connection to the tftp server fails. Then the phone goes throu the same cycle again and grabs another address and try to connect to the tftp server, etc. If you wait long enough it will consume the class C address range. I can ping the tftp server. The Avaya phone is looking for option 176, the Cisco phone is looking for option 150 in the dhcp assighment.

kleo · ‎02-27-2005

A couple things:

1) You need TWO option 176 settings one in data vlan scope with only "L2Q=1,L2QVLAN=818" and one in the voice vlan scope "MCIPADD=#.#.#.#,MCPORT=1719,TFTPSRVR=#.#.#.#"

The first causes the avaya phone to go to your voice vlan and release it's address from data vlan. Once on voice vlan it grabs address and clan,tftp etc info.

-MCIPADD is the IP address of the C-LAN

-MCPORT is the UDP port that is used for telephone registration

-TFTPSRVR is the TFTP server that the telephone uses to look for firmware and configuration

upgrades

• L2Q is 802.1Q. 1 is on, 0 is off

• L2QVLAN is the VLAN that the telephone uses. Vlan ID 0 is a special vlan ID that tells the next

Layer 2 switch to replace the 0 tag with the native vlan ID on that ingress port.

In dhcp data scope option 176 only with this:

L2Q=1,L2QVLAN=818

In dhcp voice scope option 176 with this:

MCIPADD=#.#.#.#,MCPORT=1719,TFTPSRVR=#.#.#.#

2) Disable option 150, I've seen is cause issues with avaya phones.

3) read these documents:(will clarify everything)

http://support.avaya.com/japple/css/japple?temp.documentID=198095&temp.productID=107755&temp.bucketID=159898&PAGE=Document

http://www.avaya.com/gcm/master-usa/en-us/resource/assets/applicationnotes/av-iptel-imp-gd-cm21-0804.pdf

4) you might want to consider using a windows or linux box for dhcp.

kleo · ‎02-27-2005

Oh i forget one other thing, 176 is a ascii option and needs to be configured like this :

Data Vlan

option 176 ascii"L2Q=1,L2QVLAN=818"

Voice vlan

option 176 ascii"MCIPADD=x.x.x.x,MCPORT=1719,TFTPSRVR=x.x.x.x"

**and your tftp script file (46xxsettings) should not include any of the above in it ***

Also, There is a way to use a http/https server instead of tftp with Avaya phone firmware 2.1.3.

HTTPSRVR=x.x.x.x,HTTPPORT=80. Ask your Avaya SE on config notes for this.

balla-zoltan · ‎02-27-2005

I'll try your suggestion first thing Monday morning and let you know the result.

balla-zoltan · ‎03-01-2005

It worked! The phone gets an IP address, now I can ping the phone. I just found out that we do not have a tftp server. Since we do not have a tftp server I neede to assing an extention to the phone manually. After that the phone set itself up fine. If I set a tftp up do you know what needs to be in the file that comes from the tftp server? The issue now is that the phone does not have a dial tone and it does not ring, but I think that is the Avaya Callmanager's configuration issue.

Thank you for your help.

kleo · ‎03-01-2005