|
|
The Bulk Extension Mobility wizard uses a single CSV file for both input and output to specify which action (login, logout, status) to perform. The CSV file follows standard CSV specifications and includes the following 8 columns:
•Phone - contains the phone name.
•User - contains the Cisco Extension Mobility end-user id.
•UDP - contains the User Device Profile for Cisco Extension Mobility end-user. Currently Cisco refers to this as "Device Profile".
•Action Performed - contains the action (e.g. get status, logout, login) last performed.
•Time Performed - contains the timestamp of the last performed action.
•Status Performed - contains the result of the last performed action.
•Command - contains the overriding action to be performed next time.
•Message - contains additional output of the UPLINX Phone Control Tool about the performed action.
The header line must be present and the columns must be in the same order as in the example below.
Depending on whether the CSV file is used as input or output and the action being performed, some columns will be read or written and others ignored. Please note that instead of specifying phones in the CSV file, a list of phones can be chosen manually. The following rules are employed when executing a bulk EM operation:
•Unless the action is Commands , the Command column is ignored. For example, if a user executes a Login action and selects a CSV as input, the Login action will be performed on every row of the CSV file, regardless of Command column of that row. If the action is Commands, the Command column determines which action will be performed on the row.
•When used as input, only columns Phone, User, UDP, Command of the Bulk EM CSV are (optionally) used. The other columns (Action Performed, Time Performed, Status Performed, Message ) are ignored.
oGet Status: if the Phone column is present and theUser and UDP columns are missing, Get Status will resolve User and UDP from the Phone column. Otherwise, if the User is present and the Phone and UDP are missing, Get Status will resolve Phone and UDP from User .
oLogin: takes Phone, User, UDP as input and attempts to login the User on the Phone with specified UDP .
oLogout: takes Phone as input and logs out whoever is logged in on the phone.
•When used as output, all columns of Bulk EM CSV may be written. The columns Action Performed, Time Performed, Status Performed and Message contain historical information regarding the executed action.
oGet Status : Phone / User / UDP are always filled to indicate who is logged in on a phone. If User and UDP are empty, that means no user is logged in on the phone. Command is always "none".
oLogin: Phone / User / UDP are used to indicate who has (just) been logged in on the phone. Command is always "logout".
oLogout: Phone / User / UDP indicate who has (just) been logged out on the phone. Command is always "login" (ready to be used later to restore EM status).
Example of CSV file format (copy and paste into notepad, then open in Excel to format):
Phone,User,UDP,Action Performed,Time Performed,Status Performed,Command,Message
SEP00070E16C0C7,,,none,12:44:42 PM,,get status,
SEP001D70FC98BA,,,none,12:44:42 PM,,get status,
SEP0021A00E2877,,,none,12:44:42 PM,,get status,
SEP0021A02BC8B8,,,none,12:44:42 PM,,get status,
SEP0021A02DFE28,,,none,12:44:42 PM,,logout,
SEP04C5A44D2C77,Test10,UDP_Test10_up4,none,12:44:42 PM,,login,
SEP108CCF7469E3,Test10,UDP_Test10_up4,none,12:44:42 PM,,login,
SEP503DE57D6060,,,none,12:44:42 PM,,logout,
SEP64168DBB39D0,,,none,12:44:42 PM,,logout,
SEPC89C1DB5CBA9,,,none,12:44:42 PM,,logout,
SEPC89C1DB61489,,,none,12:44:42 PM,,logout,
|
|
