J169 / J179 H.323 VPN

[dsm600rr]

Hello all,

Curious why Avaya says this is not supported? I loaded the H.323 Firmware and the phone booted up like a 9608 would and built a tunnel back to my ASA and is working perfectly fine.

The reason this came up is I have a customer with J179's and they need a few temp remote phones, so rather than sell them 9608's I tried this on the J179 to keep everything consistent and all is working just fine.

They already had an ASA so a SBC seems silly.

R11.0

Thoughts?

ACSS

 

[TouchToneTommy]

I have plenty of customers on R11 using J phones loaded with H.323 working just fine.

 

[dsm600rr]

TouchToneTommy: Thank you - My test phone has been up and running just fine as well. Was just curious if there was a reason or if Avaya was just being Avaya.

When you downloaded the "Avaya Deskphone H.323 6.8.3 Software for the 9608/9608G/9611G/9621G/9641G/9641GS and J169/J179" file, did you:

- Just put the files in the main folder to the systems SD Primary Folder?

What about the contents of the "signatures" Folder as well?

ACSS

 

[dsm600rr]

ACSS

 

[TouchToneTommy]

Didn't bother with the Signatures folder, although it may be important in the long run, I don't know.

And actually I uploaded these to one of our cloud-hosted IP Office SE's. I set the J phones HTTP Server address to the public IP of the hosted system and the signalling to H.323. Let it connect and download the firmware files, when it reboots in H.323 mode I go into the craft menu and clear it. After that reboot I program in the VPN parameters so it will connect to the system that is set up for VPN phones, perhaps download more firmware to match the IPO, and register it to the system before shipping off to the ultimate user.

 

[dsm600rr]

TouchToneTommy: "perhaps download more firmware to match the IPO, and register it to the system before shipping off to the ultimate user."

What do you mean by this?

ACSS

 

[TouchToneTommy]

Since I'm abusing a cloud hosted IPO to get the phone switched from SIP to H.323, I may be loading a different version of firmware than what is running on the real system with the VPN. If so, when the phone connects to the VPN it asks for the upgrade.txt file, compares what it is running and what the system is supplying, and if different it will up/down grade itself to match.

My situation is I work from a remote office, a customer wants to deploy VPN phones. The phones are shipped to me, I configure and test them, and then ship to the users. I don't have an IPO running in my home office to provide the H.323 conversion files. If you are hosting your own file server, or you are doing the H.323 conversion at the customer premise, you'll have the correct revision to start out with.