On-premise Database Tables Schema
mesibo on-premise gives you complete access to your data and total control over it. All the database tables created by mesibo on-premise and the data written in them are accessible to you.
While you can view all the data in the mesibo on-premise database, you can only use data from the below-listed tables and the columns. All other tables and columns are for mesibo on-premise use only and can be modified or deleted without notice. Hence, you MUST not access or use them.
You must not write to tables in the on-premise mesibo database under any circumstances. Also ensure that you do not overload the mesibo on-premise database. If frequent reads are needed, consider setting up the database in a master-slave replication configuration. This allows read operations to be performed on the slave, reducing load on the master. The slave can then be accessed to retrieve required data as needed.
mesibo on-premise stores all the messages between your users in the
messages table when you enable message retention. Following are the columns you can read.
|refid||Message Reference ID|
|uid||UID of the user to whom the message was sent|
|src||UID of the sender|
|gid||Group ID if the message was sent to the group|
|flags||message flags used when sending|
|rich||1 = Rich message with image, location, title, etc., 0 = Normal text message|
|title||Title of the rich message (valid only if rich=1)|
|subtitle||Message part of the rich message (valid only if rich=1)|
|image||Image URL of the rich message (valid only if rich=1)|
|latitude||Latitude - (valid only if rich=1 and the value is in range -90 and +90 )|
|longitude||Longitude - (valid only if rich=1 and the value is in range -180 and +180 )|
|message||Normal Text or Binary message (valid only if rich=0)|
mesibo on-premise stores all the call logs in the
calls table. Following are the columns you can read.
|uid||UID of the user who initiated the call|
|duid||UID of the user to whom the call was made|
|huid||UID of the user who hanged up the call|
|ts||Time when the call was made|
|rts||Time when ringing on the destination started|
|ats||Time when destination answered|
|ets||Time when the call was ended|
|type||Type of the call, 0 = voice, 1 = video|
|status||Real-time Call Status|
mesibo on-premise stores all the group call logs in the
groupcalls table. Following are the columns you can read.
|uid||UID of the user who joined the call|
|peer||UID of the publisher if the uid is the subscriber, 0 if the uid is the publisher|
|sts||Time when the call was started, in epoch seconds|
|ets||Time when the call was ended, in epoch seconds|
|bw||Bandwidth consumed (in bytes)|
mesibo on-premise stores all users in the
users table. You can join this table with
calls table to find the address from the UID. Following are the columns you can read.
|uid||UID of the user|
|address||Address of the user|
|online||Online status of the user, 1 = online, 0 = offline|
|active||Active status of the user, 1 = active, 0 = not active|