- Preface
- Introduction
- Accessibility
- User Attributes
- Users
- Contacts
- System Distribution List
- Telephony Integration
- Call Management
- Message Storage
- Networking
- Messaging
- LDAP
- SpeechView
- Notifications
- Video
- System Settings
- Advanced System Settings
- Fax Server
- Tools
- User Settings
- Bulk Administration Tool
- Tenant Partitioning
- Index
Bulk Administration Tool
This chapter provides the information on required and optional CSV fields when creating, updating, or deleting different objects using Bulk Administration Tool (BAT).
Required and Optional CSV Fields in BAT
The BAT tool allows you to create, update, and delete multiple user accounts, contacts, distribution lists, distribution list members, or unified messaging accounts by importing information contained in a comma separated value (CSV) file. For more information on BAT, see the Bulk Administration Tool section.
The tables in this section list the required and optional fields to include input CSV files. The fields are listed in alphabetical order, except for the required fields that are listed first.
Use the applicable table, depending on the type of object:
- Users With or Without Voice Mailboxes— Table B-1
- Contacts— Table B-2
- Distribution Lists— Table B-3
- Distribution List Members— Table B-4
- Unified Messaging Accounts— Table B-5
Table B-1 Required and Optional CSV Fields for User
|
|
|
|
|
---|---|---|---|---|
The unique text name for the user account. Any combination of ASCII or unicode alphanumeric characters, periods, commas, spaces, and the special characters `, ~, !, @, #, $, %, ^, &, -, _, ', up to a maximum of 64 characters. You should use only printable ASCII characters in the Alias field, because some messaging features do not support non-printing ASCII characters or Unicode. (The non-printing ASCII control characters are those below code 0x20.) For example, IMAP only supports user names that contain printable ASCII characters, so users with aliases that contain non-printing characters or unicode are unable to access their Connection messages via IMAP clients. In addition, the Cisco Object Backup and Restore Application Suite (COBRAS) is unable to back up messages for such users, because COBRAS uses IMAP to perform the backup. |
||||
The number that callers dial to reach the user. The value must be unique among users in the partition. Any combination of ASCII alphanumeric characters, from 3 to 40 characters long. |
||||
The unique text name for the user template to apply to the account during creation. |
||||
The unique characters that the user enters to access Unity Connection web applications. Any combination of alphanumeric characters, and the following special characters: ~!@#$%^&*()-_+={}|[]:"';<>?/\., To help protect Unity Connection from unauthorized access and toll fraud, enter a long, eight or more characters and non-trivial password. |
||||
The unique digits that the user enters to access voice messages by phone. Any combination of digits 0 through 9. To help protect Unity Connection from unauthorized access and toll fraud, enter a long—six or more digits—and non-trivial PIN. |
||||
The physical address, such as a house number and street name where the user is located, or with which the user is associated. Any combination of ASCII or unicode characters up to a maximum of 128 characters. |
||||
An alternate version of the first name. Unity Connection considers alternate names when users and callers use voice recognition to place a call or address voice messages. To create/update more than one alternate first name per user, separate them by semicolons (;). If an alternate name needs to contain a semicolon, precede the semicolon with another semicolon to indicate to Unity Connection that the name contains a semicolon. Use this field in conjunction with the AltLastNames field to add nicknames or maiden names for users. You can also use alternate names to add phonetic spellings of hard-to-pronounce names. Alternate first names and alternate last names are stored as a pair in the database. When submitting multiple alternate names, make sure that you have the same number of alternate first names and alternate last names. For example, if you have a user named Elizabeth Brown, who is sometimes known as “Liz” and sometimes known by her maiden name of “Smith,” you would enter the following AltFirstNames and AltLastNames to ensure that all four combinations are submitted to the database: |
||||
An alternate version of the last name. Unity Connection considers alternate names when users and callers use voice recognition to place a call or address voice messages. To create/update more than one alternate last name per user, separate them by semicolons (;). If an alternate name needs to contain a semicolon, precede the semicolon with another semicolon to indicate to Unity Connection that the name contains a semicolon. Use this field in conjunction with the AltFirstNames field to add nicknames or maiden names for users. You can also use alternate names to add phonetic spellings of hard-to-pronounce names. Alternate first names and alternate last names are stored as a pair in the database. When submitting multiple alternate names, make sure that you have the same number of alternate first names and alternate last names. For example, if you have a user named Elizabeth Brown, who is sometimes known as “Liz” and sometimes known by her maiden name of “Smith,” you would enter the following AltFirstNames and AltLastNames to ensure that all four combinations are submitted to the database: |
||||
An alternate spelling of the user first name in an internationally recognizable format (i.e., ASCII only characters). The value is used by the phone interface to search for users and to address messages. Any combination of ASCII alphanumeric characters up to maximum of 64 characters. |
||||
An alternate spelling of the user last name in an internationally recognizable format (i.e., ASCII only characters). The value is used by the phone interface to search for users and to address messages. Any combination of ASCII alphanumeric characters up to maximum of 64 characters. |
||||
Organization-specific information about the user, such as accounting information, department names, or project codes. The information can be included in user reports. Any combination of digits from 0 through 9 up to a maximum of 32 digits. |
||||
The name of the building where the user is based. Any combination of ASCII or unicode characters up to a maximum of 64 characters. |
||||
The name of a locality, such as a city or other geographic region where the user is located, or with which the user is associated. Any combination of ASCII or unicode characters up to a maximum of 64 characters. |
||||
The two letter ISO 3166-1 country code where the user is located, or with which the user is associated. |
||||
The name or number for the department or sub division of an organization to which the user belongs. Any combination of ASCII or unicode characters up to a maximum of 64 characters. |
||||
The user name that appears on the administration and user interfaces. If Displayname is empty and both Firstname, Lastname are present, then Displayname would be combination of "Firstname Lastname", else Displayname would be Alias. Any combination of ASCII or unicode characters up to a maximum of 64 characters. |
||||
The user name that appears on the administration and user interfaces. If Displayname is empty and both Firstname, Lastname are present, then Displayname would be combination of "Firstname Lastname", else Displayname would be Alias. Any combination of ASCII or unicode characters up to a maximum of 64 characters. |
||||
The email address of the user. This corresponds to the Corporate Email Address field in Cisco Unity Connection Administration. Note The field is only for directory information purposes. Unity Connection does not use the address to deliver incoming messages. Any combination of ASCII alphanumeric characters, and the special characters hyphen, underscore, period and at sign (“@”), up to a maximum of 320 characters. |
||||
Name used to construct part of SMTP address before the @ sign. A name is needed for unicode aliases that cannot be converted into a valid SMTP addresses. |
||||
The numeric or alphanumeric identifier assigned to a user, typically based on order of hire or association with an organization. Any combination of ASCII or unicode characters up to a maximum of 64 characters. |
||||
The unique text name used to identify and authenticate the user with an RSA SecurID security system. Any combination of ASCII or unicode characters up to a maximum of 50 characters. |
||||
Any combination of ANSI or Unicode alphanumeric characters, periods, commas, spaces, and the special characters `, ~, !, @, #, $, %, ^, &, -, _, ', up to a maximum of 64 characters. |
||||
The initials of part or all of the user name. Any combination of ANSI or unicode alphanumeric characters, periods, commas, spaces, and the special characters `, ~, !, @, #, $, %, ^, &, -, _, ', up to a maximum of 6 characters. |
||||
The preferred language of the user. Use the Windows language code, such as 1033 for U.S. English. For a list of supported languages and the corresponding language codes, see the “Numeric and Alphabetic Codes for Supported Languages” section in the System Requirements for Cisco Unity Connection 10.x at http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/10x/requirements/10xcucsysreqs.html#pgfId-172173. |
||||
Any combination of ANSI or unicode alphanumeric characters, periods, commas, spaces, and the special characters `, ~, !, @, #, $, %, ^, &, -, _, ', up to a maximum of 64 characters. |
||||
The name of the manager or supervisor of the user. Any combination of ASCII or unicode characters up to a maximum of 64 characters. |
||||
For users located in the United States, the zip code where the user is located, or with which the user is associated. For users located in Canada, Mexico, and other countries, the postal code where the user is located, or with which the user is associated. Any combination of ASCII or unicode characters up to a maximum of 40 characters. |
||||
The full name of the state or province where the user is located, or with which the user is associated. Any combination of ASCII or unicode characters up to a maximum of 64 characters. |
||||
The position or function of the user within the organization, for example “Vice President.” Any combination of ASCII or unicode characters up to a maximum of 64 characters. |
||||
The unique text name that is displayed on the user interfaces for the class of service (COS) with which the user account is associated. Any combination of ASCII or Unicode characters, up to a maximum of 64 characters. |
||||
The required Client Matter Code (CMC) to transmit to Cisco Unified Communications Manager (CM), if applicable, when the user makes an outbound call. CMCs are typically used to enable the system to track calls for account or billing purposes. The value is used only if the system is using Cisco Unified CM and if the version of Cisco Unified CM is 4.1 and later. Whether the CMC is transmitted depends on the setting for outbound calls. The user CMC is used only if the outbound call does not have its own CMC. |
||||
(Applicable only to the Alternate transfer rule.) Determines the way in which Unity Connection transfers calls from the automated attendant or a directory handler to the user phone for the Alternate transfer rule: |
||||
(Applicable only to the Alternate transfer rule.) Determines the number of times the user extension rings before Unity Connection considers the call unanswered (“ring-no-answer”) and plays the applicable greeting. This setting is applicable only when the TransferType is configured for a supervised transfer. |
||||
(Applicable only to the Alternate transfer rule.) The phone number that Unity Connection transfers calls to if TransferAction is set to 1. |
||||
(Applicable only to the Alternate transfer rule.) Determines whether Unity Connection transfers the incoming calls for the user to the user greeting or to the extension specified in TransferExtension: |
||||
(Applicable only to the Alternate transfer rule.) This setting is applicable only when the TransferType is configured for a supervised transfer. Determines whether Unity Connection transfers the call to the applicable greeting or releases the call to the phone system when a call is unanswered (“ring-no-answer”): |
||||
(Applicable only to the Standard transfer rule.) Determines the way in which Unity Connection transfers calls from the automated attendant or a directory handler to the user phone for the standard (default) transfer rule: |
||||
(Applicable only to the Standard transfer rule.) Determines the number of times the user extension rings before Unity Connection considers the call unanswered (“ring-no-answer”) and plays the applicable greeting. This setting is applicable only when the StandardTransferType is configured for a supervised transfer. |
||||
(Applicable only to the Standard transfer rule.) The phone number that Unity Connection transfers calls to if StandardTransferAction is set to 1. |
||||
(Applicable only to the Standard transfer rule.) Determines whether Unity Connection transfers the incoming calls for the user to the user greeting or to the extension specified in StandardTransferExtension: |
||||
(Applicable only to the Standard transfer rule.) This setting is applicable only when the StandardTransferType is configured for a supervised transfer. Determines whether Unity Connection transfers the call to the applicable greeting or releases the call to the phone system when a call is unanswered (“ring-no-answer”): |
||||
(Applicable only to the Closed transfer rule.) Determines the way in which Unity Connection transfers calls from the automated attendant or a directory handler to the user phone for the Closed transfer rule: |
||||
(Applicable only to the Closed transfer rule.) Determines the number of times the user extension rings before Unity Connection considers the call unanswered (“ring-no-answer”) and plays the applicable greeting. This setting is applicable only when the ClosedTransferType is configured for a supervised transfer. |
||||
(Applicable only to the Closed transfer rule.) The phone number that Unity Connection transfers calls to if ClosedTransferAction is set to 1. |
||||
(Applicable only to the Closed transfer rule.) Determines whether Cisco Unity Connection transfers the incoming calls for the user to the user greeting or to the extension specified in ClosedTransferExtension: |
||||
(Applicable only to the Closed transfer rule.) This setting is applicable only when the StandardTransferType is configured for a supervised transfer. Determines whether Unity Connection transfers the call to the applicable greeting or releases the call to the phone system when a call is unanswered (“ring-no-answer”): |
||||
The phone number (extension) of the default message waiting indicator (MWI) to light when callers leave messages for the user. If no value is provided, Unity Connection uses the number of the primary extension. |
||||
The text name displayed on the system administration interface of the phone system used to turn message waiting indicators on and off for the phone number specified in the MWIExtension column. If no value is provided, Unity Connection uses the phone system specified in the MediaSwitchDisplayName column. |
||||
The maximum duration (in seconds) for recording a message from an outside (unidentified) caller. |
||||
Indicates whether Unity Connection plays a recording to the callers after a message has been sent:
Note By Default the System Default Recording option is selected. |
||||
Indicates whether Unity Connection plays a recording to callers before allowing them to leave a message for the user. You can also indicate whether all callers hear the recording or only unidentified callers:
|
||||
The display name of the post-greeting recording that plays after the greeting for this user. |
||||
The required forced-authorization code (FACs) to transmit to Cisco Unified Communications Manager, if applicable, when the user makes an outbound call. Your organization may use FACs to prevent toll fraud. For example, users may have to provide FACs to place long-distance calls. The value is used only if the system is using Cisco Unified CM and its version is 4.1 and later. |
||||
Determines whether the user is included in the phone directory for outside callers: |
||||
Determines whether Unity Connection uses the value in the EmailAddress column (Corporate Email Address field in Cisco Unity Connection Administration) to automatically create a new SMTP proxy address, so that IMAP messages to or from this email address can be properly identified by Unity Connection as belonging to this user. If you uncheck it, no such SMTP proxy address is automatically created. |
||||
The text name displayed on the system administration interface of the phone system used for Telephone Record and Playback (TRAP) sessions and to turn message waiting indicators on and off. Any combination of ASCII or unicode characters up to a maximum of 64 characters. |
||||
Any combination of the digits 0–9, T, t, commas, hashes (#), and asterisks (*), up to a maximum of 38 characters. |
||||
The text name for the user home phone displayed on the Unity Connection interfaces. Any combination of ASCII or Unicode characters, up to a maximum of 64 characters. |
||||
Any combination of the digits 0–9, T, t, commas, hashes (#), and asterisks (*), up to a maximum of 38 characters. |
||||
The text name for the user work phone displayed on the Unity Connection interfaces. Any combination of ASCII or unicode characters up to a maximum of 64 characters. |
||||
Any combination of the digits 0–9, T, t, commas, hashes (#), and asterisks (*), up to a maximum of 38 characters. |
||||
The text name for the user mobile phone displayed on the Unity Connection interfaces. Any combination of ASCII or unicode characters up to a maximum of 64 characters. |
||||
Any combination of the digits 0–9, T, t, commas, hashes (#), and asterisks (*), up to a maximum of 38 characters. |
||||
Digits to send to the pager. This is referred to in Unity Connection Administration as “Extra Digits.” For numeric pagers, the field holds numeric text to send to the pager; for text pagers, the field is blank. |
||||
The text name for the user pager displayed on the Unity Connection interfaces. Any combination of ASCII or unicode characters up to a maximum of 64 characters. |
||||
This phone number is entered in the From field on the default SMTP device for the user. Any combination of ASCII only alphanumeric characters, hyphens, underscores, periods, at signs (“@”), commas and hashes (#), up to a maximum of 40 characters. |
||||
Message notifications for the user are sent to this SMTP address. Note The SMTP address cannot include non-ASCII characters. |
||||
The text name for the user text pager displayed on the Unity Connection interfaces. Any combination of ASCII or unicode characters up to a maximum of 64 characters. |
||||
The first alternate extension for the user. The value must be unique in the partition. Any combination of ASCII alphanumeric characters, from 1 to 40 characters long. |
||||
The text name of the partition to which the first alternate extension belongs. |
||||
The second alternate extension for the user. The value must be unique in the partition. Any combination of ASCII alphanumeric characters, from 1 to 40 characters long. |
||||
The text name of the partition to which the second alternate extension belongs. |
||||
The third alternate extension for the user. The value must be unique in the partition. Any combination of ASCII alphanumeric characters, from 1 to 40 characters long. |
||||
The text name of the partition to which the third alternate extension belongs. |
||||
The fourth alternate extension for the user. The value must be unique in the partition. Any combination of ASCII alphanumeric characters, from 1 to 40 characters long. |
||||
The text name of the partition to which the fourth alternate extension belongs. |
||||
The fifth alternate extension for the user. The value must be unique in the partition. Any combination of ASCII alphanumeric characters, from 1 to 40 characters long. |
||||
The text name of the partition to which the fifth alternate extension belongs. |
||||
The sixth alternate extension for the user. The value must be unique in the partition. Any combination of ASCII alphanumeric characters, from 1 to 40 characters long. |
||||
The text name of the partition to which the sixth alternate extension belongs. |
||||
The seventh alternate extension for the user. The value must be unique in the partition. Any combination of ASCII alphanumeric characters, from 1 to 40 characters long. |
||||
The text name of the partition to which the seventh alternate extension belongs. |
||||
The eighth alternate extension for the user. The value must be unique in the partition. Any combination of ASCII alphanumeric characters, from 1 to 40 characters long. |
||||
The text name of the partition to which the eighth alternate extension belongs. |
||||
The ninth alternate extension for the user. The value must be unique in the partition. Any combination of ASCII alphanumeric characters, from 1 to 40 characters long. |
||||
The text name of the partition to which the ninth alternate extension belongs. |
||||
The Cisco Unified Communications Manager user ID that is associated with the user. Any combination of characters except for non-printing ASCII characters, up to a maximum of 128 characters. |
||||
The display name of the Exchange 2003 external service that corresponds with the Exchange 2003 server that contains the Exchange 2003 mailbox for this user. To add an Exchange 2003 external service for a user, include values for both the Exchange2003Service_ServiceDisplayName and Exchange2003Service_EmailAddress fields in the CSV input file. To remove the Exchange 2003 service for a user, set at least one of either the Exchange2003Service_ServiceDisplayName and Exchange2003Service_EmailAddress fields to %null% in the CSV input file. |
||||
The primary email address that is associated with the Exchange mailbox that you want this user to be able to access. To add an Exchange 2003 external service for a user, include values for both the Exchange2003Service_ServiceDisplayName and Exchange2003Service_EmailAddress fields in the CSV input file. |
||||
The User ID setting in Exchange 2003 (useful when the setting is different from the user alias). To add an Exchange 2003 external service for a user, include values for both the Exchange2003Service_ServiceDisplayName and Exchange2003Service_EmailAddress fields in the CSV input file. |
||||
The display name of the Exchange 2007 external service that corresponds with the Exchange 2007 server that contains the Exchange 2007 mailbox for this user. To add an Exchange 2007 external service for a user, include values for both the Exchange2007Service_ServiceDisplayName and Exchange2007Service_EmailAddress fields in the CSV input file. To remove the Exchange 2007 service for a user, set at least one of either the Exchange2007Service_ServiceDisplayName and Exchange2007Service_EmailAddress fields to %null% in the CSV input file. |
||||
The primary email address that is associated with the Exchange mailbox that you want this user to be able to access. To add an Exchange 2007 external service for a user, include values for both the Exchange2007Service_ServiceDisplayName and Exchange2007Service_EmailAddress fields in the CSV input file. |
||||
The Windows domain alias for the user in Exchange 2007 (useful when the setting is different from the user alias). |
||||
The display name of the Exchange 2010 external service that corresponds with the Exchange 2010 server that contains the Exchange 2010 mailbox for this user. To add an Exchange 2010 external service for a user, include values for both the Exchange2010Service_ServiceDisplayName and Exchange2010Service_EmailAddress fields in the CSV input file. To remove the Exchange 2010 service for a user, set at least one of either the Exchange2010Service_ServiceDisplayName and Exchange2010Service_EmailAddress fields to %null% in the CSV input file |
||||
The primary email address that is associated with the Exchange mailbox that you want this user to be able to access. To add an Exchange 2010 external service for a user, include values for both the Exchange2010Service_ServiceDisplayName and Exchange2010Service_EmailAddress fields in the CSV input file |
||||
The Windows domain alias for the user in Exchange 2010 (useful when the setting is different from the user alias). |
||||
Specifies the address to relay incoming message when one or more of the actions (EmailAction, VoicemailAction, FaxAction, DeliveryReceiptAction) is set to 2 (Relay the message). RelayAddress is in the format of someone@somewhere or someone@somewhere.com. |
||||
The full SMTP proxy addresses for users. To create/update more than one address per user, separate them by commas and surround them all with double quotes. For example: |
||||
The value of the LDAP field that you mapped to the Unity Connection Alias field when you configured Cisco Unity Connection to integrate with an LDAP directory. See the Task List for Configuring LDAP section. This field is used when you create Unity Connection users by importing LDAP user data and when you integrate existing Unity Connection users with LDAP users. |
||||
Note that the field is only for directory information purposes. Cisco Unity Connection does not use the phone number to route calls. |
||||
A descriptive name for the notification device. This field is required if you want to create an HTML notification device. |
||||
The phone number that the user use to play and record voice message. |
||||
Disallow the users to change the mobile number from Cisco PCA and Mini Web inbox. |
||||
Disallow the users to change the notification template from PCA. |
||||
The email address of the user text-compatible mobile phone, or another email account (such as a home email address). Up to 128 characters can be entered in this field. SmtpAddress_HTML column is mandatory if Active_HTML column is set to 1. |
||||
|
|
|
|
|
---|---|---|---|---|
The alias of the Unity Connection user for which you want to add a unified messaging account. Note the following: |
||||
The descriptive name for the unified messaging service that you want to associate with this unified messaging account. Note the following: |
||||
A unique identifier that distinguishes multiple unified messaging accounts for the same user. Note the following: |
||||
Exchange only: Determines which Exchange email address to access for unified messaging features:
|
||||
Exchange only: Determines whether calendar and contact functionality is enabled for this user: |
||||
Cisco Unified MeetingPlace only: Determines whether the MeetingPlace Scheduling and Joining feature is enabled for this user. If the feature is not enabled in the unified messaging service specified by serviceDisplayName, the value that you specify here, if any, is ignored. |
||||
Exchange only: Determines whether the Synchronize Connection and Exchange Mailboxes (single inbox) feature is enabled for this user. If the feature is not enabled in the unified messaging service specified by serviceDisplayName, the value that you specify here, if any, is ignored. |
||||
Cisco Unified MeetingPlace only: Determines whether MeetingPlace meetings sre set up through the server listed in the unified messaging service specified by serviceDisplayName. |
||||
Required when creating unified messaging accounts for MeetingPlace. Required when creating unified messaging accounts for Exchange when all of the following are true:
If you specify a loginType of:
|
||||
Required when creating unified messaging accounts for MeetingPlace. Required when creating unified messaging accounts for Exchange when all of the following are true:
|