Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

New Avaya 5610SW ip phone - dhcp error-looping conditions in script

Status
Not open for further replies.

markm75E

IS-IT--Management
May 25, 2010
10
US
We have the avaya ip office 500 system.. I have dhcp setup via my windows 2008 server, which has worked fine..

We had auto extension creation set to on, but i have since turned that off (either way i cant get this new phone to register).

I created a new extension in the ip office manager and a new user.. all existing ports do not have ips listed in the ip office manager somehow either.

We received a new 5610sw ip phone.. i plug it into a working switch (same cord from an existing one that worked fine)..

I initially did get it to get an ip address.. though it would never register or prompt for an extension.. Then the next time i plug it in i get:

Contact DHCP/TFTP administrator, L20 params in option 43/176 or xxx.scr script file have looping conditions.

If this worked as expected, shouldnt it have gotten an ip address and prompted me to enter an extension for this phone?

**EDIT: if i manually enter a static ip address.. i still get that dhcp error..

we had 43 other phones work fine prior to this.. this is the same switch too.. i dont think i have vlans setup on the switch either.. the phone is picking vlan = o in the auto config.



Any thoughts?

Thanks
 
I should also note that we are using the netgear FS728TP POE switch.. pretty much at defaults except that QOS is set to DSCP.

 

The phone place we had install the phones had changed it from CoS.. i guess i should set it back to Cos on the switch then correct?

In dhcp, i didnt have an option 176..
I now have option 176 setup and set to this: L2Q=1,L2QVLAN=0,VLANTEST=0 (string value)..

I reset my one test phone.. it still gets the dhcp 176 error after attempting to get an ip for awhile.

I found the ip boot test software from avaya.. did a simulation for 2 phones.. it said 2 addresses were requested and successfully obtained.

As far as that script file.. i dont believe so?


 
Did you do a Hold CLEAR on the phone first, also are you planning on assigning the IP address of the system and tftp/http server manually as that info isn't getting passed by that string, also is it even getting an IP address correctly :)

ACSS (SME)
APSS (SME)

 
I did do the hold to clear it.. my dhcp server is a win 2008 box on 172.16.1.71 and the voicemail/officemanger box is 172.16.1.103.. thats what we have for tftp server ip address in the office pro manager system tab.. in that setting area, dhcp is disabled..

so would the 176 option look like this:

L2Q=1,L2QVLAN=0,VLANTEST=0,MCIPADD=172.16.1.71,MCPORT=1719,TFTPSRVR=172.16.1.103

Thanks again

(still not sure why the test software would report things are ok, but the actual phones fail)

 
MCIPADD=172.16.1.71,MCPORT=1719,TFTPSRVR=172.16.1.103

if your running your network with no VLAN's it would look like the above.

Kevin Wing
ACSS Small and Medium Enterprise (SME) Communications
ACS- Implement IP Office
ACA- Implement IP Office
Carousel Industries
 
@kwing11200.. when i do that, i get "badfilesvaddr" on the phone.. (176 option = MCIPADD=172.16.1.71,MCPORT=1719,TFTPSRVR=172.16.1.103)

However, i dont think i was able to clear the phone.. what is the exact method.. hit hold.. then release.. then type out reset and #? or clear and #.. i've tried both combinations as well as holding down the hold button while typing out the words..

 
update.. i did manage to get reset to work, had to be on a prompt on the screen for it to go through..

now, using these settings in 176 dhcp:
MCIPADD=172.16.1.71,MCPORT=1719,TFTPSRVR=172.16.1.103,FileSv=172.16.1.103

Things almost work, except discover fails.. it points at 172.16.1.71, which should be the ip of the ipoffice box 172.16.0.30

Do i need one more entry for that?
 
Update again lol

i changed to this:

MCIPADD=172.16.0.30,MCPORT=1719,TFTPSRVR=172.16.1.103,FileSv=172.16.1.103

under 176 in dhcp.. this phone worked! woopie.. finally

Not sure why this 176 entry was so important when it worked fine with all the other phones, but it did work.

Now i have to figure out why this new phone/user doesnt have the preset buttons, i think i missed a user rights section somewhere.

Thanks again
 
I was able to get the buttons in there by doing a copy from other user's buttons.. however, next to the users name is not the little red key that i see on other users in the manager.. any ideas what that means?

Also.. i'm trying to login to the voicemail pro server, and i cant recall what the default userid and password is.. (when doing it remotely it asks for it)...

 
It's not a red key it's a red(Hot)desk, meaning they have a login code set, the users that don't have the red desk don't have login codes set :)

ACSS (SME)
APSS (SME)

 
we have

option 176 MCIPADD=172.17.0.50,MCPORT=1719,TFTPSRVR=172.17.0.50,PROCSTAT=0,PROCPSWD="27238"

option 242
MCIPADD=172.17.0.50,MCPORT=1719,HTTPSRVR=172.17.0.50,PROCSTAT=0,PROCPSWD="27238"

the extra bits useful if your phones have been locked down by a previous config
 
thats a nice suggestion - would have been useful a while a go when a customer managed to bork installing an IP handset over the phone.....
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top