9608's won't upgrade/connect after upgrade 2

[redswine]

Upgraded a customers IPO to 11.0.4(SP3) from 9.1 and all the digital phones upgraded just fine. But they have 3 remote locations with VPN connections and 9608's that just say connecting (according to the customer). I had them unplug the phones. I've rebooted the IPO, but still no luck. Any suggestions?

Thanks

 

[icet500]

Is it failing on building vpn tunnel or is it say discovering call server?

 

[bahmonkeys]

You will need to setup option 242 DHCP Option. Point the http server to the phone system where the firmware files are located.

 

[redswine]

ok, I'm onsite. The phones are connecting across the public network. I have verified the address they're looking for is the same it's always been. The public IP address is setup under LAN2 as are the firewall settings and the stun server. When the phone reboots, it looks for the upgrade.txt from the HTTPS and HTTP server, like always. Then contacting call server and then it just says connecting.

 

[teletechman]

Sounds like they are remote phones as apposed to VPN. If that is correct make sure that the correct ports are still forwarded in the firewall. The phone will not upgrade across the public internet unless you open those ports as well. Do you see the phone hitting the IPO in the Monitor program?
Mike

 

[redswine]

They're definitely not VPN phones. There are no VPN settings in the phone. They worked perfectly prior to the upgrade, and now they don't. I've been trying everything today. They definitely are seeing the IPO because it won't let you log the extension in with the wrong password. Here's what monitor spits out when the phone tries to connect:

13:17:08 1018207mS H323Evt: Recv GRQ from 74.106.227.29:49300
13:17:08 1018207mS H323Evt: e_H225_AliasAddress_dialedDigits alias
13:17:08 1018208mS H323Evt: found number <519>
13:17:08 1018260mS H323Evt: Recv: RegistrationRequest 74.106.227.29:49300 on 1; Endpoints registered: 0; Endpoints in registration: 2, tpkt user: 00000000
13:17:08 1018260mS H323Evt: e_H225_AliasAddress_dialedDigits alias
13:17:08 1018260mS H323Evt: found number <519>
13:17:08 1018261mS H323Evt: RRQ --- CallSigProtocol is H323AnnexL_P. Go for Avaya 4600IP phone
13:17:08 1018261mS H323Evt: RRQ --- Register extn 519 using product IP_Phone, version 6.3116, id Concrete Protec_5eeb695409131258
13:17:08 1018261mS H323Evt: <519> registered, ipo behind nat 1, phone behind nat 1
13:17:08 1018262mS H323Evt: RASSRV: GetAlternate GK list returns <none>

 

[redswine]

another weird thing, is that even though none of the ip phones are coming up. All of the teleworker and power user licenses are showing in use. If I unplug an extension that has a power user assigned to it, it does not change what system status says.

 

[Qzwsa]

I believe that the assignment of the power/teleworker user licenses is what marks them as in use. It doesn't matter if they are assigned to phones that are plugged in, users unassigned to extensions, or anything like that. If assigned, then used.

- Qz

 

[derfloh]

The monitor trace shows "behind NAT". It requires remote phone ticked. It's strongly recommend to disable NAT on the site to site VPN.

IP Office remote service
IP Office certificate check
CLI based call blocking
SCN fallback over PSTN

 

[gwebster]

It looks like the 9608 is still running 6.3.1 firmware. Try upgrading it to the recommended version for IPO 11.0.4.3.

 

[Westi]

teletechman already said it

they are not VPN phones but remote phones as they are at a public IP requesting registration. That means you have to forward port 80 to the system for the phones to get the files.

easier way, unplug them, load them into the car, drive to the main site and plug them in. Then when they are upgraded bring them back.

Joe
FHandw, ACSS (SME)

Remembering intrigrant 2019

 

[ACSscott]

Do you have Enable Remote Worker checked for these users? What is the "Phone File Server Type" in the system tab? If it's set to "Memory Card" then look in Embedded File Management to make sure the necessary files were uploaded to the card during the upgrade process.