Paging Central Software Configuration

Every paging service provider has its own central number and modem pool configuration. For each paging service provider that will be used, add a paging-central child element to the alpha-pager element of the DGE's <TRAVERSE_HOME>/etc/emerald.xml file. For each service provider, set the following parameters:

Paging Configuration Parameters

Parameter	Description
name	A name that uniquely identifies this service provider to the DGE.
number	The number the DGE must dial to reach Paging Central, including any prefixes. You can find many Paging Central phone numbers at http://www.notepager.net/tap-phone-numbers.htm or a similar site.
speed	The highest speed supported by the service provider. Possible values include the following: 0 (110bps) 2 (300bps) 4 (1200bps) 5 (2400bps) 6 (4800bps) 7 (9600bps) The default value is 5.
parity	The type of parity checking, if any, supported by the service provider. Possible values include the following: 0 (none) 1 (odd) 2 (even) 3 (mark) 4 (space) The default value is 2.
databits	The number of data bits supported by the service provider. Possible values are 2 (7 bits) and 3 (8 bits). The default value is 2.
stopbits	The number of end-of-byte bits supported by the service provider. Possible values are 1, 1.5, and 2. The default value is 1.
flowcontrol	The type of handshaking supported by the service provider to prevent data loss during transmission. Possible values include the following: 0 (none) 1 (XONXOFF) 2 (CTSRTS) 3 (DSRDTR) The default value is 2.

The alpha-pager parent element also includes a sender id, which identifies the modem that is used to communicate with the specified paging central locations, as well as one or more device priority child elements that specify what port is used.

Note that it is typical to have several <paging-central> definitions since your staff might have pagers (cell phones) from different vendors, and each vendor has their own phone number for paging. While creating action profiles, the vendor is specified using the pager-pin@pager-central-name syntax.

If the modem is not available or busy, pages are queued on the DGE. Undeliverable pages older than 1 hour are ignored. Tthese parameters can be controlled via the configuration in emerald.xml also.

Example Paging Configuration in emerald.xml

<alpha-pager>

 <sender id="3035557777"/>

 <device priority="10" port="/dev/ttyS0" />

 <device priority="20" port="/dev/ttyS2" />

 <paging-central name="attws"> <!-- name should be unique -->

   <number>9998887777</number> <!-- number to dial, including prefix -->

   <speed>5</speed> <!-- 0=110bps, 2=300bps, 4=1200bps 5=2400bps, 6=4800bps, 7=9600bps -->

   <parity>2</parity> <!-- 0=none, 1=odd, 2=even, 3=mark, 4=space-->

   <databits>2</databits> <!-- 2=7bits, 3=8bits -->

   <stopbits>1</stopbits>

   <flowcontrol>1</flowcontrol> <!-- 0=none, 1=xonxoff, 2=ctsrts 2=ctsdtr, 3=dsrdtr -->

 </paging-central>

 <paging-central name="nextel"> <!-- name should be unique -->

   <number>3035551212</number>

   <speed>5</speed>

   <parity>0</parity>

   <databits>3</databits>

   <stopbits>1</stopbits>

   <flowcontrol>0</flowcontrol>

 </paging-central>

</alpha-pager>