How to Use 2Ring with PageGate

PageGate can be easily integrated with 2Ring by writing directly to the PageGate Database.

Developers that are familiar with database access can directly integrate with PageGate's database. This is probably the most efficient way to add messages to the message queue, but may not be an option in all programming environments. Another downside to this method is that it may be version specific (if the database structure changes in a future version of PageGate, the integration may stop working).

PageGate uses a Jet 4.0 database as it's back end. This is a MS Access 2000 compatible database. If you have the ability to write to MS Access 2000 databases, then you can write to the PageGate's database directly. New messages can be added to the PageGate's message queue by adding a new record to the 'messages' table in the 'pagegate.mdb' database.

The field definitions and descriptions of the 'Messages' table follows:

Label	Field Type	Value
user	Text	This field must match the name of a Recipient or Group within the PageGate Admin.
pin	Text	Must be set to a zero length string (""). This field value CANNOT be left Null.
message	Memo	This field is the text of the message to be sent
carrier	Text	Must be set to a zero length string (""). This field value CANNOT be left Null.
date_time_requested	Date	This field specifies the date and time to send this message. By default, set the current date and time.
date_time_sent	Date	Leave unset
frm	Text	This field specifies the name of the Sender of the message.
sent	Boolean	Set to False
error	Boolean	Set to False
ascii_file	Text	Must be set to a zero length string (""). This field value CANNOT be left Null.
mail_file	Text	Must be set to a zero length string (""). This field value CANNOT be left Null.
lock	Boolean	Set to False
scheduled	Boolean	Set to False
reliapage_index	Numeric	Set to 0
repeat_interval	Numeric	Set to 0
repeat_stop	Date	Leave unset
station	Numeric	This field provides a unique identifier that can be referenced when performing reports to identify the source of the message. Values 0 through 9 are system reserved and cannot be used. Set this field value to 10 ≥
message_id	Auto Number	Leave unset
retries	Numeric	Set to 0
lasty_try	Date	Leave unset
transaction	Numeric	REQUIRED VALUE This field must be a unique number (long integer). The best way to handle this is to edit the control database record, read the current value of the 'unique' field, increment it, and then write this value back to the control table. The transaction number can be reused after approximately 1 hour.
dialer	Numeric	Set to 0
creator_name	Text	If security is enabled within PageGate, this is the name of the user who created the message. Otherwise, set the field value to a zero length string (""). This field value CANNOT be left Null.
creator_machine	Text	This is the machine name of the computer that created the message. This field value CANNOT be left Null.
original_recipient	Text	Set this field value to the same value as the user field.
last_recipient	Text	Set this field value to the same value as the user field.
server	Text	This field is not used but must be set to a zero length string (""). This field value CANNOT be left Null.
archived	Boolean	Set to False.
priority	Numeric	Set this field value to 0.

Integration with 2Ring

Integrating 2Ring with PageGate

Steps to Send Text and SMS Messages from 2Ring

Integration with 2Ring

Integrating 2Ring with PageGate Steps to Send Text and SMS Messages from 2Ring

Integrating 2Ring with PageGate

Steps to Send Text and SMS Messages from 2Ring