|
|
Joined: Oct 2006
Posts: 7
Member
|
Member
Joined: Oct 2006
Posts: 7 |
I know this post is old Is this still the best way ? Firmware 4.0 will support LLDP-MED now but only for some phones . If this is the best way is the config info downloaded from the FTP server persistent data ? Does the config.gz get written to NVRAM ? If I temporarily setup my laptop as the FTP server will the phones still remember the VLAN info when I take my laptop out of the system ? For some reason there appear to be no DHCP options that the phone understands controlling layer 2 stuff like VLAN TOS etc. The network stuff seems so primitive compared to the 5000 or 3300. I know that any additional phones added later would have to have the VLAN etc hand keyed but for the initial 100 phones I definitley don't want to do it by hand Thanks
|
|
|
Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.
|
|
|
Joined: Oct 2007
Posts: 49
Member
|
Member
Joined: Oct 2007
Posts: 49 |
I like to use IP phone manager whenever I can. Not a bad tool if you take time to learn it. The only drawback is it can not scan the ip sets riding on different network that your PC is in !
|
|
|
|
Joined: Jun 2007
Posts: 490
Member
|
Member
Joined: Jun 2007
Posts: 490 |
without doubt if you have a switch that support LLDP/MED or CDP (Cisco) that is a far better way to set the VLAN ID than putting that in the config file. The phones boot time will decease substantially when the phone learns it's VLAN ID via layer 2 protocols such as LLDP or CDP.
|
|
|
Forums84
Topics94,513
Posts639,938
Members49,844
|
Most Online5,661 May 23rd, 2018
|
|
0 members (),
135
guests, and
48
robots. |
Key:
Admin,
Global Mod,
Mod
|
|
|
|
|