H. 323 upgrade file location? 7

[Rhinorhino]

After unzipping the H.323 upgrade files what location do I drop them in and do I need to do an Upgrade?

Thanks

 

[tsackl]

For IP Office 500v2 it is /system/primary (located on the SD-Card).
For Server Edition it is /Disk/system/primary.

Expand the zip archive and copy all files to the destination.
Do not forget to transfer the folder "signatures" as well.

 

[Rhinorhino]

Thanks the upgrade worked.

I now see the H.323 sets with the upgraded SW with I look at them I SS.

I was trying to get the J 179 to emulate the 9611 and I'm at this point in the Pic. Any suggestions?

 

[derfloh]

It didn't load the H323 firmware. You have to set the IPO as file server and change signaling to H323. It should.the reboot and load 96x1Hupgrade.txt followed by the 96x1 firmware.

But I never did this myself. Alternatively you can try to copy the 96x1Hupgrade.txt and save it as J100Supgrade.txt. But this will only work if the phone accepts the firmware even if the signaling is set to SIP.

 

[Rhinorhino]

Thanks I will make those changes.
In the meantime this is currently what the phone is displaying after a reboot

 

[derfloh]

Seems like it's asking for the file server address

 

[Rhinorhino]

This is my current setting in System/System:

 

[Rhinorhino]

The J179 s actually creating a user extension number

 

[Rhinorhino]

Also the J179s configuration shows an IP address for the phone and server and Mask have been automatically assign to the phone by the IPOs DHCP

 

[derfloh]

What is your question now?

 

[Rhinorhino]

It's just stuck on waiting for dhcp. Do I have the correct settings if it's looking for the file server address? Thank you

 

[derfloh]

You can configure all settings manual if the DHCP doesn't deliver the needed information.

IP address, subnet mask, gateway, HTTP server, call server, signaling

 

[Rhinorhino]

Yes I did that on the J179 config but it still is stuck.

 

[derfloh]

What do you in SysMon? Do you see DHCP request/reply? Do you see file download?

 

[Rhinorhino]

I'm heading over there today I'll check. Thank you

 

[Rhinorhino]

From the j189 I can ping the IPO successfully it still assigns an Avaya IP address to the J179 but then still gets stuck on waiting on DHCP.

The Monitor does not show any activity and sometimes after reboot I get this in the J179 display

 

[derfloh]

Sound like you have a second DHCP server in the same network.

 

[Rhinorhino]

I tried plugging it into the secondary port using 182.168.43.1 that I usually use as a maintenance port and set it to DHCP and still got the same results.

I got the idea of find this after reading Shaun E. Post within this thread:

[https://www.tek-tips.com/threads/j179-on-ip-office-9-1-it-works.1806086/

 

[Shaun E]

From the j189 I can ping the IPO successfully it still assigns an Avaya IP address to the J179 but then still gets stuck on waiting on DHCP.

The Monitor does not show any activity and sometimes after reboot I get this in the J179 display

Have you changed the signalling in admin mode to H323?

That is the interface when it's running SIP firmware.

The "Waiting for DHCP" prompt on the J100 series is also misleading. It will show that even when it has successfully received a DHCP IP address and is pulling down configuration. You need to go to Admin mode then Log -> Boot Logs which should show more information on what it is requesting and any failures.

 

[TouchToneTommy]

Run Monitor and check the boxes for File Sys, HTTP, and DHCP on the Services tab, and color code them so that it is easier to see on the screen.

The J phones do NOT show the file request and response on their screens like the 96xx phones.

After the phone gets its address via DHCP, while it is requesting and receiving files, it shows "Waiting for DHCP" which is the most irritating thing that Avaya every designed.

You will see that the phone gets an IP Address from the IP Office (is the IPO the DHCP server??), and you will see the file requests and responses.