J179 Phone Model in H.323 Mode not booting

[hethersue]

Hi All,

We are trying to add a J179 phone to our environment. We don't have any currently. Uploaded the appropriate Firmware to the utility server and checked that the 46xxsettings file was recent enough to support this phone model, and added to the 46xxsettings file SET SIG 1 so that the phone will se H.323 instead of SIP. When we boot these devices (which happen to be on a new voice VLAN), they seem to get stuck on the screen looking for the 'File Server'. A port capture shows that while we haveion 242 enabled, the MCPORT=1719 and HTTPSPORT=443 are both coming back as invalid parameters.

Our option 242 string is simple:
MCIPADD=x.x.x.x(callserver),MCPORT=1719,HTTPSRVR=x.x.x.x(Utility Server IP),HTTPSPORT=443

How can these parameters be invalid? Any ideas?

I then figured bypass all this and just configure the phones manually as a test to see if I can just register one, and there is noplace on this phone to manually enter the Call Server address. I can see where you can enter the default gateway, HTTP Server, etc...but where on earth can I enter the Call Server address?

Thanks for any advice!!!!

 

[avayaguy23]

Try http instead of https for the utility server. You’d have to switch your utility server to use http though.

 

[ZeroZeroOne]

To manually set up the J100 series phones go into the CRAFT menu and scroll down and select SIP, then select SIP global settings to set your domain and also set the SIP proxy policy to Manual.

Back up one level and you can select SIP proxy list to enter your Session Manager address(es).

[Edit]... Oh, you wanted h.323.... never mind.

 

[SloTCMS]

I too am in the process of replacing our 9611's... You might try :543 port for HTTP...

 

[phoneguy55]

are you sure its h323? By default these phones are SIP. When you first boot it will ask about auto provision. Answer no. Then press admin. enter the craft password. scroll down to signaling. Select h.323 and save it. The phone will boot as h323 and upgrade if necessary.

 

[IPEXE]

Plz check pcap trace