Option 242 for 96xx 2

[telcomwork]

Would someone be so kind to share the an example DHCP option 242 string and 96xxsettings file they are using successfully without the sensitive info?

 

[optionsleft]

hi,

this string works fine with me.

MCIPADD=0.0.0.0,0.0.0.0,MCPPORT=1719,TLSSRVR=1.1.1.1,HTTPSRVR=1.1.1.1,L2Q=1,L2QVLAN=25,L2QAUD=5,L2QSIG=3,DSCPSIG=26,DSCPAUD=46

You must have to set your http server correctly. The rest of the values after the http servers are optional depending on your network configurations. Hope this may help.

 

[sjforcum]

NOTE: This string is putting in QOS Values which with today's equipoment should not necessarily be a big deal, but some legacy network gear might have problems with some of the values in this string.

SJF

 

[telcomwork]

Thanks all!

 

[telcomwork]

COuld this same string be used for 1600 series phones?

 

[telcomwork]

Also HTTPSRVR=1.1.1.1 is for HTTP as well as HTTPS?

 

[telcomwork]

I'm unfortunate to have a HTTP / IIS Microsfot at my disposal so apologies if I'm asking too many questions.

In the admin guide I see the following ....


"In configuration where the upgrade script and application files are in the default directory on the HTTP server, do not use the HTTPDIR=<path>.You do not have to use Option 242. If you do not use this option, you must ensure that the key information, especially HTTPSRVR and MCIPADD, is administered appropriatley elesewhere."


I plan on using option 242 from the above example with the following string with my specific information
MCIPADD=0.0.0.0,0.0.0.0,MCPPORT=1719,TLSSRVR=1.1.1.1,HTTPSRVR=1.1.1.1,L2Q=1,L2QVLAN=25,L2QAUD=5,L2QSIG=3,DSCPSIG=26,DSCPAUD


I don't plan on using HTTPDIR=<path> and instead placing the upgrade script and application files are in the default directory on the HTTP server. Dumb question but what/where is the default directory on a Microsoft 2003 Server running IIS?

 

[telcomwork]

Would an example of the Default directory (root directory) be ..... C:/Inetpub/

http://wwwroot

 

[moev99]

While we're on the topic, I'm curious why the documentation for the 96xx phones states examples of how to configure DHCP on Windows servers and not linux. Currently, I am using dhcpd in linux that was bundled with CM4.0. In fact, the rpm version has -AV tacked onto the end, implying that it was tweaked by Avaya. Is there a reason why they omitted giving dhcpd setup instructions?

 

[jimbojimbo]

Perhaps Linux admins are smart enough to know how to set up DHCP.......

Or at least know how to read....

I do agree that like many vendors out there a bias towards Micro$ seems to exist. Linux gives me much better tools for working and troubleshooting.

I use 'option hipphone code 242 = text;'

then in the subnet 'option hipphone "<string here>";

I have both 176 and 242 so I just added an 'h' to identify the http options.

Have noticed a little 'quirk' with the ip option settings and multiple subnets.

Jimbo