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!

Equinox with multiple expansion systems

Status
Not open for further replies.

JazzWizzard

Technical User
Oct 28, 2019
67
CA
Hello

I have a setup with dozens of expansions system and 2 server select in resiliency. I'm planning on deploying Equinox/IX Workplace. Some users are registered on the server (primary), while the others are registered on their local expansion system. We'll be installing an Avaya SBCE, too, for security purposes.

For this to work in Zang, I'll have to create a profile for each systems, and have their SIP FQDN resolvable both internaly and externaly, but here's the issue: our client only has 1 public IP.

Is it possible to have all the external FQDNs of all the expansion systems and servers pointing to the same external IP ?

I know this can be done with web servers, but don't know if that's possible with call servers...

Thanks a lot, guys!

 
I am not sure tbh. In R11 oder definition (or some pre announcement) it was mentioned that soft clients like IX Workplace, OneX Mobile, Communicator are allowed to register with any node in Server Edition and not only in the user's home system.

But I am not sure if it really works because I never tested it myself. And I don't know if it is a Select only option.

IP Office remote service
Fixed price SIP trunk configuration
CLI based call blocking
SCN fallback over PSTN
 
Ok no problem. I don't mind having all the Equinox users registering on the main server, my only issue is what will happend when they dial 911. I want the system to give the correct adress to the emergency first responders.
 
If its 11.0.4 (maybe even earlier) then I'm sure that users from any system can register their Equinox using the address of the primary. Should be easy enough to test with one user.

Registering against different systems is only really necessary if their in widely different geographic locations, in which case it would also be very odd for the sites not to have their own local internet connections.

Stuck in a never ending cycle of file copying.
 
Well, the issue is that our client is a municipality, therefore, all sites are connected to the HQ via fiber where all the routing is done. So in essence, remote sites don't have independant internet connectivity. They all use the same fiber infrastructure across all the city's various branches.
 
You can create multiple profiles in the same zang account.
Site 1 (points to 46xxsettings.txt on primary )
Site 2 (points to 46xxsettings.txt on secondary )
Etc.. etc..

When a user enters their email to register they will be presented with a drop down box. They select the site appropriate to them, and register.

I do in my lab. One profile for production and one for POC users.



Travis
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top