|Announcement Service Urls|
Conference call announcement settings in the following format:
http://announcement_server_IP_or_hostname:12222|Priority or List of IP addresses of FE/AVMCU servers
- Priority: The recorder service will balance the load amongst the announcement services with the same priority.
- FE / AVMCU Preference: The recorder service selects the announcement service based on the IP address of the SfB/Lync FE / AVMCU used of the conference call in order to ensure that the same announcement service is selected by different recording services (even different recording services in different Verba clusters). In this case, there is no dynamic load balancing, and the FE / AVMCU IP addresses have to be split across multiple announcement servers manually in the configuration.
|title||Configuration for large multi-site deployments|
The configuration should consist of two parts:
- In the first part, the frontend IPs has to be assigned to the announcement servers. Each line represents an announcement server. Every announcement server has to be represented only once. Multiple IPs can be assigned to the same announcement server, but an individual IP can be assigned to only one announcement server (so an IP should show up only in one line). This part represents the primary announcement servers for each frontend. This part should be the same at all recorder configuration, regardless the site! Example:
- The second part represents the failover announcement servers. This part can vary per site, based on the nearest announcement server. At this part, the priority should be set instead of the list of the IPs. For example:
So for example, the final configuration for Site1 should be something like this:
Load balancing and failover configuration with priorities (2 announcement servers per datacenter):
Load balancing and failover configuration with FE / AVMCU preference (1 announcement server per data center):
|Announcement Service Uris||The SIP addresses of the announcement service, one in a line. Required for hiding transfer information in metadata.|