Partnerships:

Development Resources Center - SNPP

1. System Overview

The SNPP (Simple Network Paging Protocol) Server enables clients to send messages to 1Way and/or 2Way subscribers over the Internet and check the status of a message that was sent to 2Way subscribers. Clients can also connect securely to SNPP Server using SSL and have access to the same features. The implementation of this server is based on the rfc1861 proposal. (Parts of that document have been used here with little or no alteration).

2. Connection Information

3. Basic System

The base functionality consists of 6 commands: PAGEr, MESSage, RESEt, SEND, HELP and QUIT. The commands are not case sensitive and only the first four characters of the command are required.

Basic messages will be sent as a non-subscriber. If the message is sent successfully to a non-2Way PIN, a positive response will be returned to the client. If the message is sent successfully to a 2Way PIN, a 250 success status will be returned to the sender along with the PIN and a claim check ID. Submitting the Message status command along with the PIN and claim check ID will retrieve the sent message status.

A user may also attach Multiple Choice Response (MCR) to a message intended for a 2Way PIN. This may be accomplished by using the MCREsponse command.

At any time, the user may wish to remove all data entered to that point without disconnecting and start anew to enter information by submitting the RESEt command to the system.

The user should also consider the conflicts that can occur between the 1Way numeric pagers and alphanumeric messages. If a 1Way numeric PIN has been entered followed by an attempt to enter an alphanumeric message, the alphanumeric message will be rejected. Conversely, if an alphanumeric message has been entered followed by an attempt to enter a 1Way numeric PIN, the 1Way numeric PIN will be rejected.

Messages sent to 2Way PINs will be truncated at 500 characters. Messages to 1Way PINs will be truncated based upon the maximum message length set for each 1Way PIN.

Examples:

1. Send Message.

In order to send a message to a subscriber, receive a claim check for the message and end the session (PIN = 1366180):

2. Retrieve Message Status.

In order to retrieve the status of a message to a subscriber (PIN = 1366180, Claim Check ID = 3518):

3. Reset Session.

In order to send a message to a subscriber then clear or reset current session and send another message to a subscriber:

4. Multiple Choice Responses.

In order to attach multiple choice responses to a 2Way message (PIN = 1366180):

5. Request Help.

In order to receive system help:

6. System Login.

In order to login to the paging system as a subscriber (PIN = 1366180, Password = 123456):

7. Multi-Line Message.

The Data command is used in order to send a multiple line message, (PIN = 1366180):

4. Commands

The SNPP Server supports 13 commands. The commands are:

The SNPP Server has 3 levels of operations. The levels are:

Supported Command Levels

What Commands We Support

SNPP Commands That We Do Not Support

5. Return Codes

The SNPP server returns all of the codes as specified by the SNPP RFC(1861).

General return Commands

220 Gateway Ready
421 Too Many Errors, Goodbye
500 Command Not Implemented
554 Error, Unclassified

Page Commands

Message status commands

(If only one associated message)>
889 00 <Date&Time> <Full_Text_Response>
or
861 00 <Date&Time> Message Delivered, Awaiting
Reply
or
960 00 <Date&Time> Message Queued; Awaiting
Delivery

 

(If only more than one associated message)
214 Message Status Information
861 00 <Date&Time> Message Delivered, Awaiting
Reply
or
889 00 <Date&Time> <Full_Text_Response>
or
960 00 <Date&Time> Message Queued; Awaiting
Delivery
250 End of Message Status

 

554 Error, failed
550 Error, Invalid Pager Id or Claim Check Id
Empty String
Invalid Claim Check ID
Invalid Subscriber (not in db)