Hello All,
I have ran into this issue once before and the only resolution I could find was upgrading their system to 9.0. This customer is on 8.0(66). They have the same ZyXel made ZyWall USG 20 as all of our other 60 or so customers using remote phones. Port forwarded all of the ports used by Avaya as done in the past and ran STUN. Comes back Port Restricted Cone Nat as is always the case. Turned on remote H.323 extn enable on the VoIP page and created my default route to go out the ZyXel. Created the extension remembering to tick off Remote Extn Enable. Created the remote user and turned on Remote Worker. This is the only one in the system. When attempting to register the phone, the screen alternates between Registering and Phone with Line 1, Line 2, Line 3. The phone never actually gets to a working state. The phone is being tested from the same wide open network that we always use. I have seen this issue once before with a customer on 8.0(44) and we never actually found a resolution for it. That customer happened to be paying A LOT for maintenance so we simply upgraded them to 9.0. Without changing any settings, the phone immediately came up following the upgrade. Am I missing something on 8.0? Ask away; I am an open book!
Thank you!
I have ran into this issue once before and the only resolution I could find was upgrading their system to 9.0. This customer is on 8.0(66). They have the same ZyXel made ZyWall USG 20 as all of our other 60 or so customers using remote phones. Port forwarded all of the ports used by Avaya as done in the past and ran STUN. Comes back Port Restricted Cone Nat as is always the case. Turned on remote H.323 extn enable on the VoIP page and created my default route to go out the ZyXel. Created the extension remembering to tick off Remote Extn Enable. Created the remote user and turned on Remote Worker. This is the only one in the system. When attempting to register the phone, the screen alternates between Registering and Phone with Line 1, Line 2, Line 3. The phone never actually gets to a working state. The phone is being tested from the same wide open network that we always use. I have seen this issue once before with a customer on 8.0(44) and we never actually found a resolution for it. That customer happened to be paying A LOT for maintenance so we simply upgraded them to 9.0. Without changing any settings, the phone immediately came up following the upgrade. Am I missing something on 8.0? Ask away; I am an open book!
Thank you!
