Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

9608s issue to Cloud base IPO

Status
Not open for further replies.

Rjanson

Technical User
May 5, 2020
12
US
We are having some trouble getting a J169 (SIP) and a 9608 (H323) online and working. However, connecting a phone to the Cloud/Virtual Server is where we are getting hanged up.

We changed the HTTP and HTTPS to the public IP Address of the server, but the phones get stuck in Discovery Mode.

Everything seems right in the IPO, we have 2 extensions built out (1) SIP and (1) H323, including the users. We do have SIP and H323, Gatekeepers enabled. We are able to ping the IP Address of the server
from the phones themselves but we just can't get them to register.

The 9608 (H323) does act like it's registering and even will give me the screen where button programming features appear, but before the text appears it goes back to discovery mode, and this constantly repeats.

Has anyone ran into this problem or experienced something similar and if so what was the resolution?
 
Did you check Enable Remote Worker on the User? Did you check H.323 and SIP Remote Extension Enable on the LAN VoIP tab?
 
Hello and thanks for the reply. Yes we did check this and both settings are enabled, but still no luck.
 
When you say cloud, is this powered by avaya or it’s installed in a cloud server like aws?

What is the IP address in the call server or sip proxy on the phones?

Monitor is your best friend, have you run a monitor trace and checked if there is any registration request coming from your IP or phones extensions?
 
If its cloud are you putting the http and https ports on the end of the servers ip address? for cloud should be 411 and 8411.
 
Thanks for the replies, we were able to resolve this!
 
It had something to do with our STUN Server and NAT rules on the IPO not being configured properly
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top