Install Core with Enterprise Plus

Note Enterprise Plus License Only



Install additional Services

With the Enterprise Plus License, you will be able to use additional Services for separate UCC’s. The installation of the additional Services and UCC’s has to be done manual, with the following steps. The previous installed Service (last step, or already running), will be the base for the next new services. This can be found in the Anywhere365 folder.

6.3: C:\Program Files\Anywhere365\Core\UCC\

6.1: C:\Program Files\Anywhere365\Core\

5.0: C:\Program Files\UCC\

  1. Copy the Core folder to another place. We suggest to create a folder, where you will add all these folders (for example: “Anywhere365 UCC”).

  2. Give the folder a name, to separate them from other folders, for Example “NL”.

  3. Create a new Services, which will looks to the new created folder, with the following command:

    New-Service -name "UnifiedContactCenterService" -BinaryPathName "C:\Program Files\Anywhere365 UCC\CreatedUCCFolder\Wsp.Anywhere365.Ucc.Service.exe" -DisplayName "Anywhere365 UCC NL Service" -StartupType Automatic -Credential domain\serviceaccount

  4. Create a new UCC for this Services, with the Extra UCC Script. The manual can be found here: Learn More

  5. When adding this UCC to the config file, additional information has to be added. This is on MSMQ. A global MSMQ has to be assigned and the Services will have its own.

    Note MSMQ name needs to start with "MSMQ_".

    <UnifiedContactCenters GlobalMsmq="MSMQ_GlobalMSMQName">

    <UnifiedContactCenter Name="ucc_name" Msmq="MSMQ_ServiceMSMQName">

    The Global MSMQ is the Server name and is added to the main UnifiedContactCenters. The Services MSMQ is added to the UnifiedContactCenter and has to be configured / added for every UCC, which is advised to keep the same as the folder name, like MSMQ_NL

  6. The MSMQ has to be added to the Attendant and Dashboard Services of the UCC Server, so network traffic will be placed in the correct Message Queue. Here for, we open the web.config, which can be found in the following folder:





  7. In the appsettings of the web.xml, a new “Add Key” has to be added.

    <add key="MSMQ_ServiceMSMQName" value="ucc_name" />

  8. Add Presence provider, learn more.


Install extra UCC’s

When installing UCC’s for the Services, additional steps has to be done after the creation of the new UCC. This additional steps are on MSMQ Level.

  1. Install an additional UCC with the “Extra UCC” script, followed by the following Manual: Learn More

  2. After you installed the new UCC and added to the config.xml, the MSMQ has to be assigned to this new UCC. This MSMQ will the same as the other MSMQ’s and is the Services MSMQ.

    <UnifiedContactCenter Name="ucc_name2" Msmq="MSMQ_ServiceMSMQName">

  3. The extra UCC name, also has to be added to the web.config files of the Attendant and Dashboard Services.

    <add key="MSMQ_ServiceMSMQName" value="ucc_name,ucc_name2" />

  4. The UCC can be started by saving the config.xml


Agent Provider Port (Interceptor)

In order to use the InterceptorThe Interceptor is a service installed on the Lync / Skype for Business Front End(s). It monitors all the calls going over it. When a call going to or coming from an Agent it will come in to action. By intercepting that call and redirecting it you the Anywhere365, it lets you manage the Direct Inbound and Outbound dialogues of the Agents., the Agent Provider port has to be assigned to each Service. The port should be unique for every service and has to be configured in the config.xml of each Core on each Anywhere365 server and the Wsp.Anywhere365.SipInterceptor.Service.exe.config of the Interceptor on each Front End server.

  1. Open the config.xml of the UCC Services and add the following string to the config.


    Start at the first config.xml with the 10000 and add up one for each Services you have.

  2. Save the config.xml and (re-)start the services, to active the Agent Provider Port

  3. Follow step 1 and 2 for all Services you have created.

The Interceptor also needs to be re-configured in order to establish the connection between the Front End server(s) and the Anywhere server(s) services.

  1. Open the Front End Server(s) and navigate to the SipInterceptor program folder (usually c:\Program Files\SipInterceptor\).

  2. Open the following file in Notepad: Wsp.Anywhere365.SipInterceptor.Service.exe.config

  3. Alter the line “<add key="urls" value="http://<fqdn1>:<port1>, http://<fqdn2>:<port1>" /> “,”/>”, add the FQDNA fully qualified domain name (FQDN), sometimes also referred as an absolute domain name, is a domain name that specifies its exact location in the tree hierarchy of the Domain Name System (DNS).'s and Agent Ports you provided in the Services. When multiple Anywhere365 servers are installed each fqdn needs to be included.

    http(s)://FQDN1:10000, http(s)://FQDN1:10001, http(s)://FQDN2:10000, http(s)://FQDN2:10001

  4. Add the other Agent Provider Ports, and save the Wsp.Anywhere365.SipInterceptor.Service.exe.config

  5. Perform above steps for all Front End Services.

    Note Make sure the given ports are opened on the firewall on all servers.


Install Presence Provider

The Presence Provider is used for the subscriptions for the agents in one specific UCC Services. To get this working for the other UCC’s as well, the Presence Provider needs to be installed.

The presence provider can easily be installed with the “Extra UCC” script, which van be found in the Helper Scripts of the UCC install folder.

We suggest the following way of naming the Presence Provider:

ucc_<<servicename>> (example:

The Application ID will be: urn:application:ucc_serviceNam_presenceprovider (example: urn:application:ucc_ServiceName_presenceprovider)

After creating the Presence Provider, you can add this to the Services, which should look like:

<PresenceProvider maxPresenceSubscriptionsPerSecond="15" failedPresenceSubscriptionsResubscribeDelay="15" maxFailedPresenceSubscriptionsPerUri="3">

<UcmaPresenceSource enabled="true" ApplicationId="urn:application:ucc_ServiceName_presenceprovider" >

<UserEndpoint UserUri="sipThe Session Initiation Protocol (SIP) is a protocol to make multimedia communication (audio, video and other data communication) possible and it is also used for Voice over IP (VoIP). SIP has similarities with other Internet protocols such as HTTP and" PoolFqdn="" />

<ApplicationEndpoint OwnerUri="" />


<PstnPresenceSource enabled="true" />

<AttendantServiceSource enabled="false">

<Match pattern="" />

<Match pattern="" />