|Database Details / Vocera Usage Data|
The speechports table stores data about speech port usage.
bigint(15) unsinged 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.
datetime NOT NULL default '0000-00-00 00:00:00'
The TxDateTime column stores the date and time of the event, accurate to the second.
date NOT NULL default '0000-00-00'
The TxDate column stores the date of an event, accurate to the day.
varchar(20) NOT NULL default ''
The UserType column specifies which type of user uttered the speech. Example values: User, Phone
varchar(70) default NULL
The UserID column specifies the user ID of the person who uttered the speech. When the UserType value is User, this value is either a User ID specified via the Administration Console or the User Console on the Vocera server, or the literal string value __NLI__, which stands for Not Logged In. When the UserType value is Phone, this value is the literal string __PHONE__.
varchar(50) 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.
mediumint(8) unsigned default '0'
The Duration column specifies the duration of the utterance, in seconds.
int(5) unsigned NOT NULL default '0'
The SpeechPort column specifies which speech port processed the utterance. Example value: 3
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.