So I've double checked my settings, NAT, port forwarding and run the Stun Server. Phone asked for extension and password, the hangs at Discover (Public IP Address). This is what I show on my H323 events. I'm whooped!

110121mS H323Evt: Recv GRQ from c646a471
110121mS H323Evt: e_H225_AliasAddress_dialedDigits alias
110121mS H323Evt: found number <520>
110122mS RasTx: v=Src=192.168.202.50:1719, Dst=192.168.1.57:49304 peb=0
RasMessage = gatekeeperConfirm

115507mS RasRx: v=IFace=LAN2, Src=XXX.XXX.XXX.XXX:54957, Dst=192.168.202.50:1719 peb=0
RasMessage = gatekeeperRequest

115508mS H323Evt: Recv GRQ from c646a471
115508mS H323Evt: e_H225_AliasAddress_dialedDigits alias
115508mS H323Evt: found number <520>
115509mS RasTx: v=Src=192.168.202.50:1719, Dst=192.168.1.57:49304 peb=0
RasMessage = gatekeeperConfirm

120508mS RasRx: v=IFace=LAN2, Src=XXX.XXX.XXX.XXX:54957, Dst=192.168.202.50:1719 peb=0
RasMessage = gatekeeperRequest

120509mS H323Evt: Recv GRQ from c646a471
120509mS H323Evt: e_H225_AliasAddress_dialedDigits alias
120509mS H323Evt: found number <520>
120510mS RasTx: v=Src=192.168.202.50:1719, Dst=192.168.1.57:49304 peb=0
RasMessage = gatekeeperConfirm

XXX.XXX.XXX.XXX is the public address at the remote end, 192.168.1.57 is the internal address of the Remote 9620L set, and 192.168.202.50 is the internal address if the IP Office.

Are you sure your problem is at the IP Office side? I've found that there are a good number of home routers from various manufacturers that don't work with the remote phones even when the main site is configured correctly. Have you taken the phone to another location with a different router type?

Kyle Holladay / IPOfficeHelp.com
ACSS/ACIS/APSS Avaya SME Communications
APDS Avaya Data
MCP/MCTS Exchange 2007/2010
Adtran ATSA, Aruba ACMA

"Thinking is the hardest work there is, which is the probable reason why so few engage in it." - Henry Ford

That has not crossed my mind. I will have to try that. May even have another brand of home router to try tomorrow. Thanks for the tip, will look into it later and let you know.

Unfortunately it doesn't seem that the remote H.323 extensions are quite as simple as Avaya would have you believe. And perhaps that isn't their fault.

Kyle Holladay / IPOfficeHelp.com
ACSS/ACIS/APSS Avaya SME Communications
APDS Avaya Data
MCP/MCTS Exchange 2007/2010
Adtran ATSA, Aruba ACMA

"Thinking is the hardest work there is, which is the probable reason why so few engage in it." - Henry Ford

We have tested remote Mitel phones and Avaya phones side by side and even though both use the same principle the Avaya phones do not work in half the places the Mitel phones do unfortunately

I'd put money on this being an IP routing issue. Check you IP routes. If necessary put a static route in for 192.168.1.57 and see if that fixes it.

Saw a similar thing on a VPN phone once.

ACSS (SME)

One of these days everything will work as it should, and then we'll all be out of a job!

I know in my case I had specific routes in the IP Office (which shouldn't have been required but i put them there anyway) and still no joy.

Kyle Holladay / IPOfficeHelp.com
ACSS/ACIS/APSS Avaya SME Communications
APDS Avaya Data
MCP/MCTS Exchange 2007/2010
Adtran ATSA, Aruba ACMA

"Thinking is the hardest work there is, which is the probable reason why so few engage in it." - Henry Ford

do you have a defualt route in the ipo

0.0.0.0
255.255.255.255
192.168.202.x x=your gateway
Lan1 or Lan2 this is the lan port you are using

I also take it that 192.168.1.xxx does not clash with LAN2?

ACSS (SME)

One of these days everything will work as it should, and then we'll all be out of a job!

Don't forget to run STUN on IPO. As I mentioned on other forum tree for some stupid reason it doesn't work it you don't run it. Also set to run it on boot.
Also in such cases i put phones in DMZ behind home routers.