PocsagRX Service

Version 1.0

POCSAG page reception is a capability found on some LRSN devices that allows receiving POCSAG pages. The PocsagRX service exposes this functionality.

πŸ“˜

Please refer to the Alphapager Protocol documentation for more information on POCSAG and the LRS extensions to it. Please refer to product specific documentation for POCSAG reception restrictions.

When a POCSAG page is received, the LRSN server sends a <PocsagRX> message to all clients subscribed to the PocsagRX service. The message takes one of two forms, depending upon whether or not the capcode could be decoded into an LRS style system ID and pager ID pair.

System ID and Pager ID

For received POCSAG pages which can be converted to an LRS style system ID and pager ID, the following format is used:

<PocsagRX pager="PAGER_ID" system_id="SYSTEM_ID">MESSAGE</PocsagRX>

where:

  • PAGER_ID - Pager ID (integer)
  • SYSTEM_ID - System ID (integer)
  • MESSAGE - Message (text)

πŸ“˜

Any newline characters in MESSAGE will be converted to XML entities so that the entire PocsagRX message is on a single line.

The following example shows a received message for system ID 4, pager ID 105. The message contains a newline, plus an alert override code to flash and vibe for 30 seconds.

<PocsagRX pager="105" system_id="4" capcode>This is a&#xa;multiline test&#xc;F30Vv5</PocsagRX>

Capcode

If the received capcode can not be converted to an LRS style system ID and pager ID pair, then the PocsagRX message will be in the following format:

<PocsagRX capcode="CAPCODE">MESSAGE</PocsagRX>

where:

  • CAPCODE - Pager capcode (integer)
  • MESSAGE - Message (text)

As with the other PocsagRX, any newlines in MESSAGE are replaced with XML entities so that the entire PocsagRX message is on a single line. The following example shows the message "Testing" received on capcode 700001:

<PocsagRX capcode="700001">Testing</PocsagRX>