Converting a 9608 and 9620 from SIP to H.323

[normc62]

Ok, we've had our Avaya system for ten years now, and while I'm not formally trained, I'm as close as we've got to an "expert". So... don't beat me up too much

Our system is H.323 and we're just beginning to dip our toes into SIP, but we're not there, yet. I recently acquired a quantity of 9608 phones, pre-loaded and configured as SIP phones/ However, I need some of them to be downgraded to H.323 for an immediate need.

Here's where it gets confusing [and annoying]. Other posts I have found suggest that all I need to do is change the SIG setting from SIP to H.323 and the phone should work. In my case, it does not. To ensure I am getting an expected IP address and all other IP parameters are correct, I am manually entering them in to the phone. I can see during boot that is it has found the 96x1Hupgrade.txt file, but after about a minute or so, it tells me that there is "No file server address". After another minute, it shows "Empty SIP Proxy Server..." and presents a login page. I can put in a valid extension and password, but it returns to the login screen as it is expecting a SIP-enabled extension.

I enter the setup screens and in the ADDR section, there is no Call Server parameter available. To me, that indicates I don't have the right firmware loaded for what I want to do. The question is - how do I force the phone to, essentially, downgrade itself to the software I wish to use?

Thanking you all in advance for any suggestions you may have!

 

[derfloh]

Try to coy the current (autogenerated) 96x1Hupgrade.txt to 96x1Supgrade.txt

IP Office remote service

https://www.fwilke.com/home

Fixed price SIP trunk configuration:

https://www.fwilke.com/en/ip-office-sip-trunk-en/

CLI based cale blocking:

https://blog.fwilke.com/ip-office-block-calls-from-specific-cli/

SCN fallback over PSTN:

https://blog.fwilke.com/ip-office-scn-fallback/

 

[normc62]

Fortunately, I think we have been able to move past this problem. With the help of our vendor, who was actually working on a semi-related project, they were able to put the pieces of our puzzle back together. I don't have access to one of the utility servers that hold the updated/modified configuration, but that, along with an issue with the DHCP configuration, fixing those two things seems to have solved it all.

I am now slowly converting 50 SIP phones back to H.323... fun, fun


Thanks all,

 

[critchey]

I think I can shed some light on the issue you had here as I have done some testing on this exact issue.

If you are running an older version (I know R7 works) then a system will take a SIP phone and convert it to H323 no problem.

If you are running a newer version (I think R9 and newer not sure about R8 and R8.1) then the IPO will NOT server 96XX phones in SIP H323 firmware. It shoots out some weird error in monitor and will not serve the firmware. In that case you need to setup a http server (anything will do but I use fenix because it is super easy to setup and use and it is free) to serve the firmware to the phone. Once you do that it is a fairly simple process to take phones out of SIP and put them in H323.

So the reason you see some posts say simply change it from SIP to H323 is probably because they are older posts or the poster had an older system. Hopefully this saves someone some frustration down the road.

The truth is just an excuse for lack of imagination.