-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 After moving to 4.0.2, I took a look at the new option to add VoIP for a switch. To my surprise, it listed the switch as not having VoIP.
Checking the switches.conf file, the option was clearly enabled : VoIPEnabled=yes I tried bouncing a port I knew had a VoIP device (which I deregistered) on it and it successfully came back online, in the correct VLAN. Next I edited the switch and added the checkmark in the VoIP field. Checking switches.conf, the option now looks like this : VoIPEnabled=Y I can make this change manually in my switches.conf for the other 100+ switches, but I'm somewhat confused by the change. What standard are you going to be using moving forward? Will it be Y/N? Or will it keep changing. I've seen 1/0 and yes/no in previous versions. - -- - --------------------------- Jason 'XenoPhage' Frisvold [email protected] - --------------------------- "Any sufficiently advanced magic is indistinguishable from technology." - - Niven's Inverse of Clarke's Third Law -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.19 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlHgwjsACgkQ8CjzPZyTUTRRkACfVP190plZ9GhyjtIDbO6FhLZS 1p0AoIwhX2z+VK8ftmXyvaAKIkxd7fhn =7NaD -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
