PacketFence
Bug Tracking System

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000719PacketFencehardware modulespublic2009-06-08 13:382012-06-14 12:24
Reporterobilodeau 
Assigned Toobilodeau 
PrioritynormalSeverityfeatureReproducibilityhave not tried
StatusclosedResolutionno change required 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Summary0000719: support non Cisco VoIP phones on Cisco switches
Descriptioncurrently, when using Cisco switches and non Cisco VoIP phone, the DHCP query of the phone cannot be used to determine its VLAN (when using port-security). The voice VLAN has to be hardcoded into the phone currently.

There should be a way to make this work ... the main reason why it doesn't currently is that the development of the code on Cisco switches had been done which Cisco phones in mind
=> the code has to be generalized
TagsNo tags attached.
fixed in git revision
fixed in mtn revision
Attached Files

- Relationships

-  Notes
(0001844)
fgaudreault (viewer)
2011-01-31 17:12

This is done using DHCP option 150 with Cisco, option 176 for Avaya, etc. Basically, on the "data" network, you have an option 176 that tells the phone to tag is port using the voice vlan. On the voice VLAN DHCP, you have an option 176 that tell the phone the proper TFTP server IP, etc.

On the registration and data VLAN DHCP scope, we need to add the following :
option 176
value ascii "L2Q=1,L2QVLAN=6"

On the Voice VLAN :
option 176
value ascii "MCIPADD=192.168.6.10,TFTPDIR=/phone/,TFTPSRVR=192.168.6.10"

Now how to deal with port-security? I think we don't have any choice to allow 2 MAC on the data VLAN. The best way of doing things is Mac Authentication on the wired side. Maybe we should phase out port-security??
(0002108)
obilodeau (reporter)
2011-07-15 09:25

Non cisco phones do work on cisco switches. This ticket is too broad, I'm closing it for now.

For DHCP integration into registration VLAN's regarding voice vlans, see 0001233.

Other tickets should be filed for specific cases of specific devices not working or specific switches not working.

- Issue History
Date Modified Username Field Change
2009-06-08 13:38 user4 New Issue
2010-04-15 17:43 obilodeau Project PacketFence 1.9 => PacketFence
2010-05-05 16:55 obilodeau Category 1.9.0 => 1.9.x
2010-11-19 14:40 obilodeau Reporter user4 => obilodeau
2010-11-19 14:40 obilodeau Category 1.9.x => hardware modules
2010-11-19 14:40 obilodeau Target Version => 2.1.0
2011-01-31 17:12 fgaudreault Note Added: 0001844
2011-03-03 15:15 obilodeau Target Version 2.1.0 => +1
2011-03-03 15:19 obilodeau Target Version +1 => +2
2011-07-15 09:25 obilodeau Note Added: 0002108
2011-07-15 09:25 obilodeau Status new => resolved
2011-07-15 09:25 obilodeau Resolution open => no change required
2011-07-15 09:25 obilodeau Assigned To => obilodeau
2011-12-30 23:46 obilodeau Target Version +2 =>
2012-06-14 12:24 obilodeau Status resolved => closed


Copyright © 2000 - 2012 MantisBT Group
Powered by Mantis Bugtracker