46xx Name for DHCP??

[MCP2000]

Hello Everyone:

Does anyone know of a way to get a 46xx telephone to provide a "name" to the DHCP server when requesting an IP address?

Here is why I ask:
Our network administrators, in the heat of the moment, sometimes see a lease provided to one of our 4610SW telephones, but when they don't see a "name" associated with the address, they kill the lease. This obviously has some consequences for the 4610SW user.

I was wondering if there was a way to get the phone to supply a default name, the MAC, or some other identifier so that the admins don't think they have a "hung lease." Thanks

 

[vtec]

Hi,

Assuming you're using Win 2003 server, when defining reservations for the IP addresses for your IP phones, you can also set a label that allows you to identify IP phones in the IP address pool list...

Good luck,

David

 

[MCP2000]

vtec,

thanks for the response. The problem that I will have with that is that there is no separate VLAN or IP scope for the telephones. The phones are simply "integrated" into the existing IP scope.

Any ideas for this?? I was hoping there was a way to enter something in the 46xxsettings.txt file that would have it send the MAC as a name or something.

Thanks

 

[JeremyParr]

Sounds like you just need new network admins. Deleting a lease because there is no hostname associated to it is pretty dense.

 

[MCP2000]

Well, back before my company was purchased, I was an admin. Now I'm just a "phone guy," so I don't get to make those calls anymore. Thanks for the help...

 

[randyb19]

I don't remember which version of phone code this was implemented, but I have names associated with my phones on the DHCP servers. The format that Avaya came up with is "AVAxxxxxx.<domain name>", where x is the last 3 groups of the MAC address. Also, the 4690's begin with "SEP" and show the full MAC address.

 

[m4ilm4n]

Dynamic DNS should support this; you should be able to have a pool of host names created when the lease is activated.

That said, you shouldn't have to force in a kludge because of poor network design. Voice and data traffic should be in separate network spaces - period.

Alternately, you could show the responses in this thread to your admins to try and influence them to change their ways, or you could just explain to the user precisely why their phone doesn't work anymore, then redirect their wrath to the network admins.