Server Edition Select Deployment Best Practices 4

[IPOTS]

Customer has Server Edition Select Primary/Secondary and 5 Expansions. R11

The original installer configured the users on each expansion IP500v2 i.e. 75 users at one location, 50 at another etc...
No users or extensions configured on the Primary. It's only used for voicemail. PRI is being used for the main line off an expansion.

The customer wants to implement IX Workplace for various users across the solution.
In order to implement IX Workplace I would need an separate FQDN at each site in order to register to that local IP500v2. Is that correct?

My other option is to remove all the users from the expansions and move them to the Primary server. Use the expansions for trunking and analog/digital stations. Best practice would have them all on the Primary and failover to the Secondary. (or other expansions)
What is the advantage to having all the users register to the local gateway?

 

[sizbut]

As far as I'm aware (happy to be corrected), the Workplace users could all register against the primary, even if the user (and any other extension they have) are configured on another system in the network.

You would only need to connect them to other systems in the network if there was some practical reason (widely differing geographic locations, most of the user internal at each site rather than external remote connections, need to send different settings to the clients based on to which system they register).

For users and extensions in general, I'm a fan of configuring them on the systems that is their most sensible geographic host. Provides them with continued local support if any other parts of the customer network are having problems.

On the subject of resilience, almost all the resiliency features provided by a primary/secondary SE pair rely on the primary hosting at least one local IP phone desk phone (SIP or H323). Its that phone not being able to see the primary and so asking the secondary if it can connect that triggers the resiliency features.

Stuck in a never ending cycle of file copying.

 

[IPOTS]

Thanks, I'll test out the registration on IX from a user on the expansion in my lab. That would save me a lot of time reprogramming.

 

[IPOTS]

Update: That worked. Thats sizbut.

User and extension located on expansion. IX Workplace URL to Primary for registration.
User shows in Primary as Simultaneous and physical extension on the expansion in SSA. Like magic. haha

 

[BFG9K]

This sort of SCN magic has saved my butt plenty of times lol, have a star sizbut

Cheers,
BFG9K
Avaya IPO/ACCS Technician
Melbourne, Australia