Feedback
Table Of Contents
B
Last Updated: April 16, 2010backup category
To specify the type of data to be backed up and initiate the backup process, use the backup category command in Cisco Unified Messaging Gateway (Cisco UMG) offline-EXEC mode.
backup category { all | configuration | data }
Syntax Description
Command Default
All data is backed up.
Command Modes
Cisco UMG offline-EXEC (offline)
Command History
Usage Guidelines
This command indicates the content of the backup file to be saved to the FTP server.
CautionWe strongly discourage doing the data only type of backup and restore because of its potential to introduce inconsistency between configuration and data files.
The systems assigns a backupid to each backup, and it is this backup ID that you must reference when you restore a file. Use the show backup history command to locate the backup ID of the file you want to restore.
Offline mode terminates message forwarding and directory exchange. We recommend backing up at times when there is little or no messaging activity.
Cisco UMG 1.0 does not support scheduled backups.
Examples
The following examples illustrate the use of all three of the backup category commands:
umg-1# offline!!!WARNING!!!: If you are going offline to do a backup, it is recommended that you save the current running configuration using the `write' command prior to going to the offline state.Putting the system offline will terminate all end user sessions.Are you sure you want to go offline[n]? : yumg-1(offline)# backup category allumg-1(offline)# continueumg-1 enumg-1#umg-1# offline!!!WARNING!!!: If you are going offline to do a backup, it is recommended that you save the current running configuration using the `write' command prior to going to the offline state.Putting the system offline will terminate all end user sessions.Are you sure you want to go offline[n]? : yumg-1(offline)# backup category configurationumg-1(offline)# continueumg-1 enumg-1#umg-1# offline!!!WARNING!!!: If you are going offline to do a backup, it is recommended that you save the current running configuration using the `write' command prior to going to the offline state.Putting the system offline will terminate all end user sessions.Are you sure you want to go offline[n]? : yumg-1(offline)# backup category dataumg-1(offline)# continueumg-1 enumg-1#Related Commands
backup revisions
To specify the maximum number of versions of backups to be stored at any one time, use the backup revisions command in Cisco Unified Messaging Gateway (Cisco UMG) configuration mode. To revert to the default setting, five backups, use the no form of this command.
backup revisions nnnn
no backup revisions nnnn
Syntax Description
Command Default
Five backup versions are stored.
Command Modes
Cisco UMG configuration mode (config)
Command History
Usage Guidelines
Set this parameter when doing your initial configuration. You must do this before you can back up any files.
When setting the maximum number of backup versions, consider the amount of storage space that each backup file requires.
When the system reaches the limit you set, the next backup file overwrites the oldest stored backup file.
The system assigns an identifier to each backup file it makes. This identifier is the backupid. Reference this backup ID value when restoring a file. Use the show backup history command to find out what backup-id the system has assigned to the file you want restored.
You can backup different types of data (dynamically captured data, configuration data or both). The number of backup revisions applies indiscriminately to both types, so that out of a possible total of five backups, you may find three configuration and two data file backups on file. See the backup category command for information about different backup types. See the show backup and show backup history command for information about the backup.
Examples
The following example sets a limit of seven backups.
umg-1# config tumg-1(config)# backup revisions 7umg-1(config)# backup server url ftp://branch/umgbackups username ftpusername password ftppasswordRelated Commands
backup server url
To specify the server where backup files are to be stored and its access information, use the backup server url command in Cisco Unified Messaging Gateway (Cisco UMG) configuration mode. To specify no backup server, use the no form of this command.
backup server url backup-ftp-url username backup-ftp-usrname password backup-ftp-password}
no backup {revisions number | server url backup-ftp-url}
Syntax Description
Command Default
No backup server is set.
Command Modes
Cisco UMG configuration mode (config)
Command History
Usage Guidelines
Set these parameters when doing your initial configuration. You must do this before you can back up any files.
Consider the amount of storage space available on the FTP server you are specifying. If you have already set the number of backup files to be maintained (using backup revisions), you must choose a server that has space for that quantity of data.
You can back up different types of data (dynamically captured data, configuration data, or both). See the backup category command for information about different backup types. See the show backup history command for information about the backup.
Examples
The following example sets backups to be stored on an FTP server called `ftpinfrastructure' in the umgbackups directory, with the username `ftpusername' and password `ftppassword'.
umg-1# config tumg-1(config)# backup revisions 7umg-1(config)# backup server url ftp://ftpinfrastructure/umgbackups username ftpusername password ftppasswordRelated Commands
block location-id
To prevent an endpoint of the type Cisco Unity Express 3.1 and later versions from autoregistering, use the block location-id command in Cisco Unified Messaging Gateway (Cisco UMG) registration-configuration mode. Use the no form of this command to unblock endpoints.
block location-id location-id
no block location-id location-id
Syntax Description
block location-id location-id
Location ID of Cisco Unity Express 3.1 and later versions endpoint to be prevented from autoregistering.
Command Default
No endpoints are blocked.
Command Modes
Cisco UMG registration-configuration (config-reg)
Command History
Usage Guidelines
Because Cisco UMG allows all appropriately configured endpoints of the type Cisco Unity Express 3.1 and later versions to autoregister, to prevent an endpoint from doing so, you must block it.
Blocking has no impact on already autoregistered endpoints; the action will only take effect when the endpoint registration period expires. To have an immediate impact on an endpoint, first block it, then deregister it by using the no endpoint command. It will be unable to autoregister again immediately because you have already blocked it.
Only Cisco Unity Express 3.1 and later versions can autoregister. To delete endpoints of the type Cisco Unity Express 3.0 and earlier versions, use the clear endpoint command.
Examples
The following example illustrates the use of the block location-id command:
umg-1# config tumg-1(config)# registrationumg-1(config-reg)# block location-id 4085550100umg-1(config-reg)# end
umg-1(config)# end
umg-1# show registration block
UMG registration block list :
location-id 4085551212
umg-1#
Related Commands
broadcast-id
To provision a broadcast VPIM ID to local endpoints of the type Cisco Unity Express 3.0 and earlier versions, use the broadcast-id command in Cisco Unified Messaging Gateway (Cisco UMG) endpoint configuration mode. To clear the configuration, use the no form of the command.
broadcast-id broadcast-id
no broadcast-id broadcast-id
Syntax Description
broadcast-id
Endpoint's broadcast VPIM ID. This alphanumeric string of up to 15 characters/digits cannot include spaces.
Command Default
The default is vpim-broadcast.
Command Modes
Cisco UMG endpoint configuration mode (config-endpoint).
Command History
Usage Guidelines
•
•
•
•
Examples
The following example illustrates the use of the broadcast-id command:
umg-1# config t
umg-1(config)# endpoint 11 cue
umg-1(config-endpoint)# broadcast-id 0100
umg-1(config-endpoint)# end
umg-1(config)# end
umg-1# show endpoint local 11
Location Id: 11
Hostname: cue-11
Domain: cuesim1
Prefix: 408555
NAT: Disabled
Type: CUE
Broadcast VPIM ID: 0100
Primary Gateway ID: 50000
Secondary Gateway ID:
Status: Auto-Registered-Offline
Related Commands
broadcast location
To enable a subscriber to send a System Broadcast Message (SBM) to all subscribers on a specified endpoint, whether local or remote, use the broadcast location command in Cisco Unified Messaging Gateway (Cisco UMG) configuration mode. To revoke the privilege, use the no form of the command.
broadcast location location-id privilege number
no broadcast location location-id privilege number
Syntax Description
broadcast location location-id
Location ID of the endpoint where the message is to be broadcast.
number
Telephone number of the authorized sender.
Command Default
There is no authorized sender.
Command Modes
Cisco UMG configuration mode (config)
Command History
Usage Guidelines
•
•
•
•
•
Note
Examples
The following example illustrates the use of the broadcast location command:
umg-1# configumg-1(config)# broadcast location 11 privilege 4085550101umg-1(config)# endumg-1# show broadcast location 11 privilegeA total of 1 Authorized Sender(s) have been found for location 11:4085550101umg-1# endRelated Commands
