Multi-site server edition architecture sanity check

[g18c]

Hi all, after some sanity checking please as per my understanding of Server Edition (R10) setups and how they should be done verses what i am seeing, sorry if some questions are facepalm but need to sort out a system that I have inherited.

Ideal scenario:

Phones registers to primary gatekeeper (Server Edition @ 10.0.0.5).

At each site, we also have IPO500V2 chassis (Server Edition Expansion System V2 with site B @ 192.168.20.5, and site C @ 192.168.30.5).

VPN and H323 SCN between all sites.

We have set a DHCP 242 option for MCIPADD=10.0.0.5,192.168.20.5, 192.168.30.5 and VPN between sites to allow re-registration in event central server goes down we can re-register to either of the other two surviving expansion system v2 at sites B or C.

A call is made from a phone at site B (which is registered to the central call server at site A) that will go out a PSTN at site B, direct media path will kick in and hand off RTP between phone and gateway (expansion system v2 @ site B) – is this correct?

Everything can be managed centrally, and aside for shared services like voice mail or hold music, everything is good?

Actual scenario:

All gateways are licensed as server edition gateways and VPN/SCN (IP Office line) between each site.

Site A all users created on server edition, and all users at site A register there.

Site B and C, all users created local on each of their respective site's expansion system v2 (site B has 50 users, site C has 100 users).

One-X portal on central server edition (site A).

A user (which is created on site B expansion system V2) is then registering to the central server edition one-x… this user doesn’t exist on the central server edition, so is it being picked up via the SCN?

When placing a call from a one-x user at site B, to go out of a PSTN also at site B, but registered to the one-x server, it will go site b phone -> site a one-x -> site b expansion system v2 -> site b pstn trunk. This seems to be the case, it doesn’t go direct site b phone -> site b expansion -> site b pstn.

To fix

If we centralise all users on the server edition, will I need to buy more endpoint licenses (as currently the IP endpoint licenses are for site b, creating users on site a we would be short of IP endpoints) or are these shared as a whole across the entire system?

Any licenses issues to allow fail-over to the other expansion systems, or is this handled centrally/shared and processed with SCN and fact each expansion system has a server edition license (which show on the central server system as "Server Edition" and at each remote site as "Virtual Server Edition")?

Thanks in advance for the sanity check and any pointers to docs I can review.

 

[wrenchmonkey]

If you use a weblm server all licenses are centralized. They could be centralized now, but without knowing more it's impossible to say. Another piece of the puzzle will be if it's ADI licensing or PLDS licensing. If it's PLDS, you could move the license yourself.

 

[janni78]

You don't wanna have all IP Offices in the DHCP Option.
They should only register to the main site.

Then you can use Locations to assign which backup system the phones use as failover.
You don't want your 192.168.30.x phones to register to the 192.168.20.5 system if main goes down.

"Trying is the first step to failure..." - Homer

 

[g18c]

Gotcha, thanks for the replies makes sense, especially the locations thanks.

And to clarify, if they are registered to the main site, and a call is made from a phone that is on the same site as a local gateway, will direct media path setup the call RTP stream between the handset and local gateway (PSTN trunk)?

 

[janni78]

As long as you have Direct Media enabled.

"Trying is the first step to failure..." - Homer