rfc3064.txt

最新的RFC

2.5. Events and Signals for the "MD" package:

   The following codes are used to identify events and signals for the
   "MD" package.

    Table 9 "MD" Package Events and Signals
 ---------------------------------------------------------------------
|Code|Description       |Event|Signal |Additional Info                |
|---------------------------------------------------------------------|
|ans |Call Answer       |  P  |  BR   |                               |
|awk |Acknowledge wink  |  P  |  BR   |                               |
| bl |Call Block        |  S  |  BR   |                               |
| bz |Busy tone         |  -  |  TO   |Time-out = 30 seconds          |
|cwk |Continue Wink     |  -  |  BR   |                               |
|inf |Information Digits|  x  |  TO   |Time-out when signals completed|
|    |                  |     |       | out-pulsing                   |
| oc |Operation Complete|  x  |   -   |                               |
| of |Operation Fail    |  x  |   -   |                               |
|rel |Release Call      |  P  |  BR   |                               |
|res |Resume call       |  P  |  BR   |                               |
|rlc |Release complete  | P,S |  BR   |                               |
| ro |Reorder tone      |  -  |  TO   |Time-out = 30 seconds          |
| rt |Ringback tone     |  -  |  TO   |Time-out = 180 seconds         |
|sup |Call Setup        | P,S |  TO   |Time-out when signals completed|
|    |                  |     |       | out-pulsing                   |
|sus |Suspend call      |  P  |  BR   |                               |
|swk |Start Wink        |  x  |   -   |                               |
 ---------------------------------------------------------------------























Foster                       Informational                     [Page 12]

RFC 3064                   MGCP CAS Packages               February 2001


2.6. Events and Signals for the "MO" package:

   The following codes are used to identify events and signals for the
   "MO" package.

    Table 10 "MO" Package Events and Signals

 ---------------------------------------------------------------------
|Code|Description       |Event|Signal |Additional Info                |
|---------------------------------------------------------------------|
|ans |Call Answer !Note |  P  |   -   |                               |
| oc |Operation Complete|  x  |   -   |                               |
| of |Operation Fail    |  x  |   -   |                               |
|orbk|Operator Ringback |  x  |   -   |                               |
|rbz |Reverse make busy | P,S |   -   |                               |
|rcl |Operator Recall   |  -  |  BR   |                               |
|rel |Release Call      |  P  |  BR   |                               |
|res |Resume Call       |  -  |  BR   |                               |
|rlc |Release complete  | P,S |  BR   |                               |
|sup |Call Setup        |  -  |  TO   |                               |
|sus |Suspend Call      |  -  |  BR   |                               |
|swk |Start Wink        |  x  |   -   |                               |
 ---------------------------------------------------------------------
!Note: There is no indication that the operator answered the call.
       The "ans" event is an indication that off-hook was received
       from the far end which simply indicates that the destination
       address was received properly and the calling number is in the
       process of being outpulsed.

2.7. Event and Signal Descriptions

   The following provides a list of the event and signal descriptions.

   The event/signal name appears in parenthesis followed by the
   corresponding Event + Signal attribute code plus a list of the
   packages in which the event/signal occurs.

   Call answer (ans; P + BR; DT,MD,MS,MO): Off-hook signal normally
   indicates that the call has been answered and that cut-through has
   been established.  The exception is the "MO" package where it simply
   indicates that off-hook was received and the calling number is in the
   process of being sent (i.e., there is no event available to indicate
   that the operator answered the call for operator services signaling).

   Acknowledgement Wink (awk; P + BR; MD): This event is only applicable
   to the "md" package.  It provides an indication that all digits have
   been received correctly.  In an outgoing trunk, the event is
   requested and when received indicates that the connecting switch



Foster                       Informational                     [Page 13]

RFC 3064                   MGCP CAS Packages               February 2001


   received all of the addressing information.  On an originating trunk,
   this signal is sent to inform the other end that all addressing
   information has been received.  If the Call Agent is providing a
   transit application for example, in which incoming and outgoing
   trunks are both EANA trunks, then after acknowledgement wink is
   received from the terminating trunk, it is passed to the originating
   side so that the originating side knows that addressing has passed to
   the destination switch.

   Call Block (bl; S + BR; DT,MS,MD): A steady off-hook signal applied
   to one-way incoming trunks to indicate that no further calls will be
   accepted.  When "bl" is used as a signal then the "rel" signal is
   used to release the blocking condition.

   A Call Agent should only request the "bl" event in a case where it
   knows that this is a one-way outgoing trunk, and it should never see
   an incoming call-setup request ("sup" event).  As such if "bl" is
   requested as an event, then "sup" is suppressed as a persistent
   event.

   Busy tone (bz ; - + TO; BL,DT,MD,MS): Refer to ITU E.180.  The
   definition of the tone is defined by the national characteristics and
   may be established via provisioning.  Station Busy is defined in GR-
   506-CORE - LSSGR, SIGNALING, Section 17.2.6. as a combination of two
   AC tones with frequencies of 480 and 620 Hertz and levels of -24 dBm
   each, to give a combined level of -21 dBm.  The cadence for Station
   Busy Tone is 0.5 seconds on followed by 0.5 seconds off, repeating.

   Caller Id (ci(time, number, name); x + -; DO): See TR-NWT-001188,
   GR-30-CORE, and TR-NWT-000031.  Each of the three fields are
   optional, however each of the commas will always be included.

      The time parameter is coded as "MM/DD/HH/MM", where MM is a two-
      digit value for Month between 01 and 12, DD is a two-digit value
      for Day between 1 and 31, and Hour and Minute are two-digit values
      coded according to military local time, e.g., 00 is midnight, 01
      is 1 a.m., and 13 is 1 p.m.

      The number parameter is coded as an ASCII character string of
      decimal digits that identify the calling line number.  White
      spaces are permitted if the string is quoted, however they
      will be ignored.

      The name parameter is coded as a string of ASCII characters that
      identify the calling line name.  White spaces are permitted if the
      string is quoted.





Foster                       Informational                     [Page 14]

RFC 3064                   MGCP CAS Packages               February 2001


   A "P" in the number or name field is used to indicate a private
   number or name, and an "O" is used to indicate an unavailable number
   or name.  The following example illustrates the use of the caller-id
   event:

      O: ci(10/14/17/26, "555 1212", somename)

   Continue Wink (cwk ; - + BR; MD): This signal is only applicable to
   the "md" package.  It provides an indication that digits sent have
   been accepted, and further digits must be sent in order to process
   the call.  For example, when using FGD EAIN signaling, this would
   correspond to sending a wink after the country access code had been
   received to indicate readiness to receive identification and address
   fields.

   Dial-tone (dl ; - + TO; BL,DT): Refer to ITU E.180.  The definition
   of the tone is defined by the national characteristics and may be
   established via provisioning.  In GR-506-CORE - LSSGR, SIGNALING,
   Section 17.2.1, sial Tone is defined as a combination of two
   continuous AC tones with frequencies of 350 and 440 Hertz and levels
   of -13dBm each to give a combined level of -10 dBm.  It is considered
   an error to try and play dial-tone on a phone that is on hook and an
   error should consequently be returned when such attempts are made
   (error code 402 - phone on hook).

   Information Digits (inf(<inf-digits>); x + TO; MS,MD): On an outgoing
   call ("md" package only) it is used as a signal to out-pulse the
   address information when doing overlapped sending.

   On an incoming call it is used as an event to indicate that an MF
   digit string has been received.  In this case, <inf-digits> are all
   of the digits accumulated up to and including the digit delimiters
   ST, ST', ST'', ST'''.  Multiple sequences of digits ending with one
   of the ST digits may be passed in a single "inf" event.  (Note that
   K0 is the same as KP, K1 is sometimes referred to as KP' etc.
   Similarly S0 is the same as ST, S1 is the same as ST' and so on.

   The value of <inf-digits> is a comma separated list of MF digits:
   MF1, MF2, ..., MFn

   where each of MFi will be one of the following MF digit symbols:










Foster                       Informational                     [Page 15]

RFC 3064                   MGCP CAS Packages               February 2001


             Table 11 MF Digit Symbols

             -------------------------
            | Symbol |MF digit         |
            |   0    |   MF 0          |
            |   1    |   MF 1          |
            |   2    |   MF 2          |
            |   3    |   MF 3          |
            |   4    |   MF 4          |
            |   5    |   MF 5          |
            |   6    |   MF 6          |
            |   7    |   MF 7          |
            |   8    |   MF 8          |
            |   9    |   MF 9          |
            |   K0   |   MF K0 or KP   |
            |   K1   |   MF K1         |
            |   K2   |   MF K2         |
            |   S0   |   MF S0 or ST   |
            |   S1   |   MF S1 or ST'  |
            |   S2   |   MF S2 or ST'' |
            |   S3   |   MF S3 or ST'''|
             --------------------------

   Thus, an example signal or event might look like:

      inf(k0, 5,5,5,1,2,3,4, s0)

   An example where the inter-digit timer expired after the 5,5,5 would
   appear as follows:

      inf(k0, 5,5,5)

   Operation Complete (oc ; x + -; all): The operation complete event is
   generated when the gateway was asked to apply one or several signals
   of type TO on the endpoint, and one or more of those signals
   completed without being stopped by the detection of a requested or
   persistent event such as setup.  The completion report may carry as a
   parameter the name of the signal that came to the end of its live
   time, as in:

      O: ms/oc(ms/sup)

   or

      O: bl/oc(bl/rg)

   When the operation complete event is requested, it cannot be
   parameterized with any event parameters.



Foster                       Informational                     [Page 16]

RFC 3064                   MGCP CAS Packages               February 2001


   Note that when requested at the same a signal for "sup" (out-pulsing
   - a TO event), the operation complete event will indicate when out-
   pulsing is complete.

   Operation failure (of; x + -; all):  In general, the operation
   failure event may be generated when the endpoint was asked to apply
   one or several signals of type TO on the endpoint, and one or more of
   those signals failed prior to timing out.  The completion report may
   carry as a parameter the name of the signal that failed, as in:

       O: ms/of(ms/sup)

   or

       O: bl/of(bl/rg)

   When the operation failure event is requested, it cannot be
   parameterized with any event parameters.

   Operator ringback (orbk; x + -; MO): The description of the signaling
   MF CAS signaling that results in this event is describe in the
   appendix of TR-NPL-000258 [3].  In brief, it is normally a wink-on
   signal which may or may not be followed by an MF tone.  This event
   will be generated when the operator service requests that the calling
   party be alerted ("mo" package only).

   Reverse make busy (rbz; P + -; MO): This event corresponds to a
   "blocking" (off-hook) generated by the other end of the one-way