messageactivity

The messageactivity table stores information about voice messages, not text messages. This table has a primary key based on the TxMillis column.

Table 1. messageactivity table
Column	Type
TxMillis	`bigint(15) unsigned NOT NULL default '0'` The TxMillis column gives each row in the table a unique identifier. The value represents the number of milliseconds since January 1, 1970 (a date specified for internal use by the report system). Because of the uniqueness constraint, it may not reflect the exact actual date and time of the event. See TxDateTime.
TxDateTime	`datetime NOT NULL default '0000-00-00 00:00:00'` The TxDateTime column stores the date and time of an event, accurate to the second.
TxDate	`date NOT NULL default '0000-00-00'` The TxDate column stores the date of an event, accurate to the day.
UserType	`varchar(20) NOT NULL default ''` Specifies which type of user initiated the message activity. Example values: User, Phone
UserID	`varchar(70) default NULL` Specifies the user ID of the person who initiated the message activity. This value corresponds to a User ID specified via the Administration Console or the User Console on the Vocera Server.
UserSite	`varchar(70) default NULL` In a multi-site installation, the UserSite column specifies the Vocera site with which the user is associated. In a single-site installation, this value is null.
Operation	`varchar(64) NOT NULL default ''` Specifies the operation; leavemessage is the only operation supported currently.
Parties	`varchar(512) default NULL` Specifies a comma-delimited list of Vocera groups or users to which the message was sent.
Duration	`bigint(15) unsigned NOT NULL default '0'` Specifies the duration of the message activity in seconds.
IdMsgActivity	`bigint(15) unsigned NOT NULL default '0'` Identifies a Vocera message activity, which may not be unique. Any given message activity could have the same IdMsgActivity value as another Message Activity that took place earlier or later.
IdGenie	`bigint(15) unsigned NOT NULL default '0'` The IdGenie column identifies a Genie session. A single Genie session may comprise several events. For example, a Genie session for a badge-to-badge call may include the "Vocera" prompt played on the calling party's badge and the "Can you talk to..." prompt played on the called party's badge. In the table, rows for events in the same Genie session have the same value in the IdGenie column. However, this value is not guaranteed to be unique. Any given Genie session could have the same IdGenie value as another Genie session that took place earlier or later. One way to distinguish Genie sessions is to compare values in the TxMillis column.