![]() ![]() |
#1
|
|||
|
|||
![]()
I have a remote site with existing IP phones and we are adding a small Sales group that needs to have the secondary network port on the 9608 phone blocked. A new customized 46xx file has been created to shut down the port and the file is residing on a new folder in the TFTP server.
The part I don't understand is how can you direct the Sales group phones to the new customized 46xx file if there is already a existing voice vlan and standard 46xx file. New voice vlan? |
#2
|
|||
|
|||
![]()
You would normally edit or replace the existing file and then send a command to restart the phones. Its a normal part of their restart cycle for the phones to request a copy of the file from the address they have already been configured with as a file server.
|
#3
|
|||
|
|||
![]() Quote:
I don't want the Sales group phones to pick up the settings file for the existing phones on the same floor. Hope that make sense.. |
#4
|
|||
|
|||
![]()
You normally do this via your dhcp scope options
|
#5
|
|||
|
|||
![]()
You really need to go to support.avaya.com and get a copy of the 9600 Series LAN Administrators manual.
First I think 9600 Series phones don't do TFTP, they use HTTP or HTTPS. For what you want the normal approach would be to use a GROUP id. For each of the Sales team phones that can be set through the phone's local admin menus. In the 46xxsettings file you would have a section like the following: IF $GROUP SEQ 1 goto SALES goto NOTSALES # SALES ...settings unique to the sales team phones... goto COMMON # NOTSALES ... settings unique to all other phones... goto COMMON # COMMON ...settings common to all phones... Last edited by markgallagher; 11-08-2017 at 03:50 AM. |
#6
|
|||
|
|||
![]()
... have edited the previous to make minor correction to my outline of the script (first time round non-sales phones would have skipped their own settings)
|
#7
|
|||
|
|||
![]()
Thank you all.
|
![]() |
Thread Tools | Search this Thread |
Display Modes | |
|
|