Synchronizing the Registration Cache
ECB Sync data includes the Oracle Enterprise Communications Broker's registration cache. The user can enable registration cache sync via a checkbox within the Sync config settings under the ECB Sync icon.
When enabled, the Oracle Enterprise Communications Broker presents its registration cache to all ECB Synch agents every nine minutes. Each ECB Sync agent uses this data to create a separate, ECB Sync-only registration cache table that includes contacts and the ECB from which it learned the cache entry.
When a call comes for a contact found in the ECB Sync-only registration cache, the Oracle Enterprise Communications Broker receiving the call adds a URI parameter to the request URI of the TO header and forwards the message to the Oracle Enterprise Communications Broker in the table. This URI parameter informs the target Oracle Enterprise Communications Broker that is must only use its registration cache for routing this call. This parameter appears as follows.
TO sip:user2@server2.com;orcl-regonly=true
In these cases, both Oracle Enterprise Communications Brokers forward the call. The Oracle Enterprise Communications Broker receiving the call uses all other routing sources to route the call, including LDAP, LST and UserDB. The Sync agent Oracle Enterprise Communications Broker routes the call using its registration cache, and skips all other routing sources, including LDAP, LST and UserDB.
Enable Sync Operations
Enable sync configuration when you want one Communications Broker to share information with another Communications Broker. For example, to share information about users, routes, dial plans, and agents. To use Sync, you must enable the service and set the authentication secret. You can optionally enable the system to sync the configuration and the registration cache from one Communications Broker to another.
The secret that you enter in the Sync configuration must match the secret used by the Sync agents.
Add an Communications Broker Sync Agent