J179 SIP setup - R11.0.4.2 3

[rgunther]

Hey guys we just upgraded to release R11.0.4.2, and am setting up our first J179 SIP phone (all other phones we use are 96xx series). I got the phone up and working, however am confused on one setting - HTTPS server. So we always got our phone firmware files for our phones from a different HTTP server and never needed to use HTTPS. On the J179, the phone comes up and works fine with limited buttons (only 3 line appearance buttons) when i enter in the SIP Proxy address only. It also then detects the phone as a J179 phone in manager. However, when I enter in an HTTPS server (the IP Office address) it then populates the full buttons on the phone - however IPO manager detects it as an Unknown SIP device. Can anyone explain this to me? Do i have to have the HTTPS server?

Thanks,

 

[TouchToneTommy]

You should only need to put the IP Office's IP address into the HTTP server field. The phone will pull the 46xxsettings.txt file, which will give it all of the other information it needs to connect and operate properly.

 

[rgunther]

Yes, but we have a seperate HTTP server we use for phone firmware. So the phone needs to register to the SIP proxy (IP Office) but yet pull the firmware via HTTP from the HTTP server. This works fine and our phone updated firmware and is working - but all the button mapping is not there.

 

[rgunther]

Got it! Just updating for others- but I had to change the SET ENABLE_IPOFFICE attribute in the 46xxsettings file from value of 1 to 2. This puts the J179 in IP office mode with all additional features drivers by the IP office SIP proxy.
I was then only required to put in my HTTP server (file server), and SIP Proxy (IP office) settings, and the phone updated firmware and loaded all buttons normally.
Thanks!

 

[Westi]

thanks rgunther
resolutions are always worth some pink.

Joe
FHandw, ACSS (SME)

Remembering intrigrant 2019

 

[bahmonkeys]

The issue is the Avaya Environment and possibly a certificate issue. Also setup your option242 string with TLSSRVR= and HTTPSRVR=. Never touch the 46xxsettings.txt! If you have to make changes to the 46xxsettings.txt use 46xxspecials.txt this will keep the systems auto-generated 46xxsettings.txt which can cause issues with connecting phones due to invalid certs.

No need to change the above SET ENABLE_IPOFFICE string keep it auto-generated by the system. This will cause issues if you are connecting J129 phones. You can put in this string SET ENABLE_AVAYA_ENVIRONMENT 1.
I do suspect that this is a certificate issue.

You should not have to enter anything manually into the phone! Sip proxy is got from the phone system presuming it is setup correctly. Option 242 will point the phones to the .bin files and 46xxsettings text

 

[Pepp77]

https://www.tek-tips.com/viewthread.cfm?qid=1799086

- I spent ages on these phones and came up with this

| ACSS SME |

 

[rgunther]

bahmonkeys - thanks for the info. So we currently only use 2 different phone types - 9611G & now J179. The only other settings we manipulate in the 46xxsettings.txt file are the SET SCREENSAVER ON XX & SET SCREENSAVER fields - to produce the screensaver company logo. Can I move these settings to the 46xxspecials.txt file as well under #GENERALSPECIALS section? Then also like you mentioned above I will try putting the SET ENABLE_AVAYA_ENVIRONMENT 1 under the #J1X9SPECIALS Section.

 

[rgunther]

The thing that is tough in our environment is that we have 7 IPO's in an SCN. So we do not use option 242 as all phones have different call servers. Which is also why we push firmware from a different HTTP server - so we dont have to update firmware files on 7 different SD cards. We simply put the 46xxsettings.txt file & updated firmware on our HTTP server, and manually set the phone's call server address & http server address for all phones.

With that said I did add a 46xxspecials.txt file on our HTTP server (where our 46xxsettings.txt file exists). I put the GET 46xxspecials.txt command at the end of 46xxxsettings.txt - and added the SET ENABLE_AVAYA_ENVIRONMENT 1 under the # J1X9SPECIALS. The phone did grab both files correctly, but same issue as before where the buttons were not there on the phone. I replaced the SET ENABLE_AVAYA_ENVIRONMENT 1 command with SET ENABLE_IPOFFICE 2 command and viola buttons appeared on the phone again. Not sure why but i have to have the SET ENABLE_IPOFFICE 2 command in the 46xxspecials.txt or 46xxsettings file.

 

[sizbut]

The point of moving things to the specials file is that you can then let the IP Office systems auto-generate the settings file which is automatically include updated settings like those to enable all the J179 features.

Stuck in a never ending cycle of file copying.

 

[derfloh]

And all phones that connect to those 7 IPOs are in the same LAN?

I would try to separate them in different VLANs. If all switches share the same client VLAN it's also (with most switches) to push the VLAN ID to the phones using LLDP MED policies based on the switch port.

IP Office remote service
Fixed price SIP trunk configuration
CLI based call blocking
SCN fallback over PSTN

 

[rgunther]

Yes currently all phones and IPO's are on the same LAN. We currently are not using VLANs on the local LAN - but plan to implement in the near future. Thanks for everyones input. For now i was able to get it working by using and modifying a 46xxspecials.txt file / but again the only way the phone buttons would display correctly was to add the SET ENABLE_IPOFFICE 2 under the #J1X9SPECIALS.

 

[sizbut]

When you have a few minutes, just download the 46settings.txt file from the system and then delete it on the system. Then using a browser go to

http://<system_address>/46xxsettings.txt.

You'll see the autogenerated version which you can save. Then put you own files back on the system.

It pretty easy to then read the auto-generated settings file as if your a J179 and see the settins that the system would apply.

Stuck in a never ending cycle of file copying.

 

[bahmonkeys]

Yes rgunther using the specials text file allows you to overwrite the 46xxsettings which is auto-generated keeping any changes you do to specific models instead of system wide. It is better putting the SET ENABLE_IPOFFICE 2 under the #J1X9SPECIALS but just remember this will work for all J100 series phones except J129. So if your plan is never to purchase the J129 you will never have an issue.

Seems a bit messy with all the Call Servers. You ever try moving them to the Server Edition and if you need the physical pbx units set them up as Expansion units from the main Server. This way all changes is done on one system rather than physical entering in IP Addresses into the phones. With the option 242 on the DHCP server you can reserve all the IP Addresses for all the phones so you don't run into IP conflicts on the network.

You can also enable web management on those J179 using the specials text.