rfc1861.txt

著名的RFC文档,其中有一些文档是已经翻译成中文的的.

   When the PAGEr command is processed, the pager ID (and password) is
   submitted to the paging terminal with LEVEl, COVErage, HOLDtime, and
   ALERt.  If these parameters have not been altered, then their
   defaults are assumed for the transaction.  After the next PAGEr
   command has been processed, these option parameters are reset their
   defaults.  Using this type of "option-option-option-go" scheme, it is
   possible to specify a different priority level for "Jeff," and an
   alternate coverage area for "Kathy," while sending the same message
   to each.

   Possible responses from the SNPP server, with suggested text, in
   response to a PAGEr command are:

    250 Pager ID Accepted
    421 Too Many Errors, Goodbye (terminate connection)
    421 Gateway Service Unavailable (terminate connection)
    550 Error, Invalid Pager ID or Password
    552 Max Recipients Exceeded
    554 Error, failed (technical reason)

4.5.3 LEVEl <ServiceLevel>

   The LEVEl function is used to specify an optional alternate level of
   service for the next PAGEr command.  Ideally, "ServiceLevel" should



Gwinn                        Informational                    [Page 12]

RFC 1861                   SNPP - Version 3                October 1995


   be an integer between 0 and 11 inclusive.  The TME protocol specifies
   ServiceLevel as follows:

    0 - Priority
    1 - Normal (default)
    2 - Five minutes
    3 - Fifteen minutes
    4 - One hour
    5 - Four hours
    6 - Twelve hours
    7 - Twenty Four hours
    8 - Carrier specific '1'
    9 - Carrier specific '2'
   10 - Carrier specific '3'
   11 - Carrier specific '4'

   The choice on how to implement this feature, or to what level it
   should be implemented, should be optional and up to the discretion of
   the carrier.

   Possible responses from the SNPP server, with suggested text, in
   response to a LEVEl command are:

    250 OK, Alternate Service Level Accepted
    421 Too Many Errors, Goodbye (terminate connection)
    421 Gateway Service Unavailable (terminate connection)
    500 Command Not Implemented
    550 Error, Invalid Service Level Specified
    554 Error, failed (technical reason)

4.5.4 ALERt <AlertOverride>

   The optional ALERt command may be used to override the default
   setting and specify whether or not to alert the subscriber upon
   receipt of a message.  This option, like the previous command, alters
   the parameters submitted to the paging terminal using the PAGEr
   command.  The TME protocol specifies AlertOverride as either 0-
   DoNotAlert, or 1-Alert.

   Possible responses from the SNPP server, with suggested text, in
   response to a ALERt command are:

    250 OK, Alert Override Accepted
    421 Too Many Errors, Goodbye (terminate connection)
    421 Gateway Service Unavailable (terminate connection)
    500 Command Not Implemented
    550 Error, Invalid Alert Parameter
    554 Error, failed (technical reason)



Gwinn                        Informational                    [Page 13]

RFC 1861                   SNPP - Version 3                October 1995


4.5.5 COVErage <AlternateArea>

   The optional COVErage command is used to override the subscriber's
   default coverage area, and allow for the selection of an alternate
   region.  This option, like the previous command, alters the
   parameters submitted to the paging terminal using the PAGEr command.
   AlternateArea is a designator for one of the following:

    - A subscriber-specific alternate coverage area
    - A carrier-defined region available to subscribers

   As an example, Mary Ghoti is a subscriber having local service in
   Chicago, Illinois (Mary's region '1').  Her account has been set up
   in such a manner as to allow Mary's pager to be paged nationwide upon
   demand (Mary's region '2').  Specifying "COVErage 2" prior to issuing
   the appropriate "PAGEr" command allows the default Chicago area to be
   overridden, and Mary's pager to be messaged nationally for that
   transaction.  It is assumed that the carrier providing Mary's service
   will keep track of how many pages have been sent to her pager in this
   manner, and will bill her accordingly.

   Possible responses from the SNPP server, with suggested text, in
   response to a COVErage command are:

    250 Alternate Coverage Selected
    421 Too Many Errors, Goodbye (terminate connection)
    421 Gateway Service Unavailable (terminate connection)
    500 Command Not Implemented
    550 Error, Invalid Alternate Region
    554 Error, failed (technical reason)

4.5.6 HOLDuntil <YYMMDDHHMMSS> [+/-GMTdifference]

   The HOLDuntil command allows for the delayed delivery of a message,
   to a particular subscriber, until after the time specified.  The time
   may be specified in local time (e.g. local to the paging terminal),
   or with an added parameter specifying offset from GMT (in other
   words, "-0600" specifies Eastern Standard Time).  This option, like
   the previous command, alters the parameters submitted to the paging
   terminal using the PAGEr command.

   Possible responses from the SNPP server, with suggested text, in
   response to a HOLDuntil command are:

    250 Delayed Messaging Selected
    421 Too Many Errors, Goodbye (terminate connection)
    421 Gateway Service Unavailable (terminate connection)
    500 Command Not Implemented



Gwinn                        Informational                    [Page 14]

RFC 1861                   SNPP - Version 3                October 1995


    550 Error, Invalid Delivery Date/Time
    554 Error, failed (technical reason)

4.5.7 CALLerid <CallerID>

   The CALLerid function is a message-oriented function (as opposed to
   the subscriber-oriented functions just described).  This allows for
   the specification of the CallerIdentifier function as described in
   TME.  This parameter is optional, and is at the discretion of the
   carrier as to how it should be implemented or used.

   Possible responses from the SNPP server, with suggested text, in
   response to a CALLerid command are:

    250 Caller ID Accepted
    421 Too Many Errors, Goodbye (terminate connection)
    421 Gateway Service Unavailable (terminate connection)
    500 Command Not Implemented
    550 Error, Invalid Caller ID
    554 Error, failed (technical reason)

4.5.8 SUBJect <MessageSubject>

   The SUBJect function allows is a message-oriented function that
   allows the sender to specify a subject for the next message to be
   sent.  This parameter is optional and is at the discretion of the
   carrier as to how it should be implemented or used.

   Possible responses from the SNPP server, with suggested text, in
   response to a SUBJect command are:

    250 Message Subject Accepted
    421 Too Many Errors, Goodbye (terminate connection)
    421 Gateway Service Unavailable (terminate connection)
    500 Command Not Implemented
    550 Error, Invalid Subject Option
    554 Error, failed (technical reason)

4.6 Level 3 - Two-Way Extensions

   This section specifies enhancements to the SNPP protocol to support
   acknowledgment-based paging (2-way).  One of the more powerful
   features of ReFLEX-style paging, in addition to confirmed message
   delivery, is the ability to "seed" a message with multiple-choice
   type responses.  After the recipient views the message, she can reply
   with one of the seeded messages.  In addition to the multiple-choice
   responses (MCR's), the sender may elect to receive confirmation when
   the message is first viewed by the recipient.



Gwinn                        Informational                    [Page 15]

RFC 1861                   SNPP - Version 3                October 1995


4.6.1 2WAY

   The 2WAY command prefaces each two-way transaction (see previous
   example).  This places the server in the mode to receive and process
   a single 2-way transaction. The server returns to "non-2WAY" mode
   upon the completion of a SEND command or a RESEt command.  In 2WAY
   mode, it is, however, possible to do multiple MSTAtus commands (to
   check responses from field message units).  Possible responses are:

    250 OK, Beginning 2-Way Transaction
    550 Error, Standard Transaction Already Underway, use RESEt
    421 Gateway Service Unavailable (terminate connection)
    500 Command Not Implemented
    554 Error, failed (technical reason)

   4.6.2 PING <PagerID | Alias>

   This command localizes (finds) the field message unit on the system
   and returns its location and/or status.  Because of the sensitive
   nature of location information, the subscriber may elect to have a
   generic "pager located" message (ACLU mode) rather than to return her
   actual location. Possible responses are:

    820 <Locus_Code> Unit On System, This Area
    821 Unit On System, No Location Information Available (ACLU mode)
    750 Unit Valid But Not Online At This Time
    920 Unit Not Online, But Can Queue Message for Later Delivery
    550 Can't PING; Unit NOT 2-way capable
    550 Unknown or Illegal ID
    421 Gateway Service Unavailable (terminate connection)
    500 Command Not Implemented
    554 Error, failed (technical reason)

4.6.3 EXPTag <hours>

   Changes the default expiry time for a queued message delivery.  If
   the message is not delivered in the specified number of hours, then
   it is deleted and the MSTAtus tag is updated to reflect the inability
   to deliver (code 760).  Possible responses are:

    250 Message Expiry Time Changed to 'nnn' Hours
    550 Cannot Change Expiry Time
    421 Gateway Service Unavailable (terminate connection)
    500 Command Not Implemented
    554 Error, failed (technical reason)






Gwinn                        Informational                    [Page 16]

RFC 1861                   SNPP - Version 3                October 1995


4.6.4 NOQUEUEing

   Specifies that the server should not allow message queuing for this
   2WAY transaction.  In this mode, if a pager is not online, the client
   will receive a "750" series response to a PAGEr command.  This
   command must be specified prior to a PAGEr command.  Possible
   responses are:

    250 Queuing Disabled, This Transaction
    550 Can't Disable Queueing
    421 Gateway Service Unavailable (terminate connection)
    500 Command Not Implemented
    554 Error, failed (technical reason)

4.6.5 ACKRead <0|1>

   Activates or deactivates message "read" acknowledgment.  When
   activated, instructs the field message unit to return a message when
   the subscriber actually views the received message.  This feature is
   independent of the actual reply.  Possible responses are:

    250 Read Acknowledgment <Enabled|Disabled>
    550 Cannot modify Read Acknowledgment
    421 Gateway Service Unavailable (terminate connection)
    500 Command Not Implemented
    554 Error, failed (technical reason)

4.6.6 RTYPe <Reply_Type_Code>

   Changes the type of reply expected from the field message unit that
   is acceptable to the client program.  Initial appropriate reply type
   codes are:

    NONE        - (default) No Reply Permitted
    YESNO       - Seeds a simple "Yes" or "No reply
    SIMREPLY    - Only pre-coded replies from providers's reply base
    MULTICHOICE - Allows full multiple choice replies
    TEXT        - Allows full text replies (generated by field unit)

   Possible responses to an RTYPe command are:

    250 Reply Type Accepted
    550 Illegal Reply Type
    503 Already Entered That
    421 Gateway Service Unavailable (terminate connection)
    500 Command Not Implemented
    554 Error, failed (technical reason)




Gwinn                        Informational                    [Page 17]

RFC 1861                   SNPP - Version 3                October 1995


4.6.7 MCREsponse <2-byte_Code> Response_Text

   This command is issued prior the the SEND command, and "seeds" the
   transaction with an acceptable multiple choice response. Each
   response is specific to the current message.  The number of
   acceptable responses may be limited by the SNPP server as desired by
   the provider.  Examples of MCREsponse(s) are:

    MCREsponse 1E2C Here is one response
    MCREsponse 0002 This is another response