Provisioning provides a command line script utility that can be used to schedule periodic processor and Domain synchronizations. The synchronization script enables you to regularly schedule a subset of the synchronization operations at different periodic intervals and across multiple time zones. You should use the sync.sh file available in the /opt/cupm/sep/build/bin/ folder.
However under the above mentioned file, the contents are as follows:
Not sure if you have solved this yet or not but this may help
Provisioning provides a command line script utility that can be used to schedule periodic processor and Domain synchronizations. The synchronization script enables you to regularly schedule a subset of the synchronization operations at different periodic intervals and across multiple time zones. The sync.sh file is available at /opt/cupm/sep/build/bin/ folder.
To schedule synchronization:
Login to the Provisioning server as root using SSH.
Enter crontab -e to edit a copy of the crontab file in vi editor.
Press the i key to enter insert mode.
To run synchronization at regular intervals, enter the following: minute hour day-of-the-month month day-of-week command-to-be-executed
Minute-Valid range is from 0 to 59.
Hour-Valid range is from 0 to 23.
Day of the month-Valid range is from 1 to 31.
Month-Valid range is from 1 to 12.
Day of the week-Valid range is from 0 to 6 (Sunday = 0).
For example, to run Call Processor synchronization at 3:24 pm every day, enter the following:
Mass Synchronization invokes synchronization operations for all objects of the specified class. Both infrastructure and subscriber synchronizations run for each processor. The order of the synchronization is as follows: call processor, unified message processor, presence processor, and then domain.
Granular Synchronization invokes synchronization operations that are specified in a formatted file, where
<filename>—is a text file that has lines of the appropriate format: <object class>.<object name>: <sync type> that is,
pp.all: both—equivalent to the [presenceprocessor] mass sync
ad.all:—ActiveDirectory mass sync
<option>—(Optional field) the following are available as options:
test—Allows a script to run without performing any syncs, but list the processors and Domains that will be synchronized.
abortonfail—Instructs the script to quit after a synchronization failure. If this parameter is not specified, the sync script will continue on success or failure.
forcedomainsync—Allows the domain sync to be performed even if one of the devices in the domain had a failed sync. If this parameter is not specified, then the domain sync will not proceed if there are device sync errors.
parallel—runs the device syncs in parallel
help—Displays usage information.
For example, if you want to run granular synchronization at 1:15 pm every Saturday, enter the following command:
Attracted by the concept of dial plan and the passion of writing, I launched a challenge to write a workbook with practical scenarios covering in details this concept, the result is a workbook with 30 practice labs treating many components such route patt...
Understanding Media Negociation in Interworking / Traversal Call : SIP <-> H323 through Expressway. Inside SDP and H245. Both signaling and Media goes through the Expressway so the IP address of expressway is offered to both SIP and H.323 endpoin...
Sometimes you troubleshoot the phone presence status issue, or you are wondering how the status is retrieved by IMP, the best place to start is to look at the SIP Publish message sent by the CUCM to IMP, Capture the SIP Publish message using wireshark, in...
The translation pattern is the most important tool in the Call Routing Process on Cisco Unified Communication manager.By definition a Translation Pattern is used to match the DIALED NUMBER (CALLED). After a match is found we perform a digits manipulation....
Sometimes, you want to populate the Self Service User ID and the Primary Extension + the Conference Now Meeting Number automatically with the IpPhone or Telephone Number LDAP Attribute used in the LDAP Directory configuration page when importing AD users ...