ip office secondary server

[azrael2000]

Question... and hopefully someone can advise me on this.

I have a customer with a primary and secondary IP Office server edition.

In the primary system, I have all of the licensing for both site, except for the virtual server license that automatically shows up on the secondary server.

In the primary server, I have created all of the users for that site, and they are in the primary server user list.
In the secondary, the users that are at that location are in the secondary site location have been put into the secondary site server.

A co worker is telling me that everything, including the secondary site users have to be in the primary site. But on the system, I have the scn line backing up the users, huntgroups, voicemails.

Doesn't this make them backup the failed system stuff both ways to the working system?

Regards

 

[derfloh]

If primary and secondary are at different sites you usually create each user and extension with the local server. The other server will act as fallback system.

Technically you can also create all users and extension on primary, which makes it easier to program and you don't have to move anything when the user moves from one site to the other.

You can do it the way you did as well but you will hear the users cry because the user will not automatically register on his base extension if the IPO service restarts.

 

[azrael2000]

Thanks derfloh.

I kinda new this; but now I can tell a ... uh... trying to find a nice way to say things... person that just because he says it has to be one way, it isn't so. (I don't know how many times I have been left to clean up her mistakes...).

And in a way it makes sense doesn't it? With users on their "home site" they aren't going over the network to get to services on the primary all the time, tying up bandwidth.

Regards

 

[derfloh]

If direct media is enabled and routing is well done bandwidth is not an issue. Call signaling would be done from second site to primary server but call traffic between phones at secondary site will not pass primary server.

It all depends on the location of outside trunks as well...

 

[azrael2000]

They have a good network, derfloh. From what i have seen of it.

However, my thinking, based on the IP Office Knowledge Base, was that you put the primary location users on the primary, secondary location users on the secondary, and then, if either one fails, the units will send all of the failed users onto the up system.

Is that correct?

Regards

 

[Pepp77]

For me you put the users onto the system they are located at, if that means all are on the primary then all are on the primary, if the users are split between sites, then those at the primary site are programmed on the primary system and those at the secondary site are programmed on the secondary system, but that's just me

| ACSS SME |

 

[janni78]

Considering that max users on Server Edition (without Select) is 2000 but you can only have 1500 on a single server I assume that you should put the users on the server that is "closest" to their location.

It's a bit strange that they don't support the max on a single server and makes you wonder what happens if you have a fail over and one server is supposed to handle 2000 users.

On Select they support 3000 on a single server and as total which makes more sense.
Looking at Aura you configured all your users on one site and then they would fail over to the backup server for each site.

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

 

[derfloh]

You can do it the same way with IPO select.

Depending on the number of users I would decide if I have all users and extensions at one server (easier to maintain but heavier load on primary) or distributed (load is shared, config errors will be found immediately and not in case of a fallback).