When installing a new system, it is hard to escape the paradigm of creating yet another user database and new passwords for each one of these users.

How does this happen? The engineer who configures the system usually starts by adding a few accounts manually to perform the first test calls and then more and more, until all users are created. This approach has clear drawbacks, since it is:

• Error-prone: it is easy to make mistakes
• Time-consuming
• Not secure: users are not removed, even when they leave the organization.

The best way to manage accounts creation is to let somebody or something else do it for us. The ideas described below also apply to customer contact creation in the UC server.

Continue reading →

(2 votes, average: 5.00 out of 5)

Loading...

Depending on how critical the UC service is for the organization, it might be necessary to put service continuity scenarios in place, including:

• Failover: a secondary server is used in case the primary server fails.
• Load Sharing: both systems work at the same time, but if one goes down, the other can manage the whole load.

Let’s start analyzing the simplest scenario: one UC Server and X users / devices connected to it. Failover is perfectly fine in this first scenario.

Continue reading →

(3 votes, average: 5.00 out of 5)

Loading...