Home > ATT > Communications System > ATT DEFINITY Communications System Generic 3V4 Instructions Manual

ATT DEFINITY Communications System Generic 3V4 Instructions Manual

    Download as PDF Print this page Share this page

    Have a look at the manual ATT DEFINITY Communications System Generic 3V4 Instructions Manual online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 164 ATT manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.

    Page
    of 397
    							ASAI and Domain Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
    Message Not Compatible with Call State (CS0/98)
    The specified call at the station is not in the alerting, bridged, held state or
    active state.
    Resources not available (CS3/40)
    The host attempted to add a seventh party to a call with six parties active
    (bridging and held cases only).
    Invalid number/domain (CS0/28)
    The call_id contained in the request is invalid.
    Mandatory Information Element missing (CS0/96)
    A mandatory parameter is missing from the request.
    Protocol Error (NAK) Causebbbbbbbbbbbbbbb
    The switch issues the following cause for a protocol processing error:
    Protocol error (CS0/111)
    The Q.932 protocol has been violated or the capability invoked is not
    consistent with this association.  For example, invoking a Third Party
    Domain Control Request over a Call Control association is inconsistent.
    NOTE:
    For more information regarding protocol errors and a complete list of
    reason codes (cause values), see the 
    DEFINITY Communications
    System CallVisor ASAI Protocol Reference
    , 555-230-221.
    Considerationsbbbbbbbbbbbbbbb
    The Third Party Answer capability can be used to answer a call present at any
    station type (for example, analog, DCP, hybrid, and BRI), as long as the station
    is domain-controlled.  A call that is already connected when the Third Party
    Answer request is made results in a positive acknowledgement (ACK).
    Multifunction Station Operationbbbbbbbbbbbbbbb
    For a multifunction station user, this capability is successful in the following
    cases:
    The user is being alerted on-hook and can either be forced off-hook or is
    manually taken off-hook within five seconds of the request (the switch
    selects the ringing call appearance).
    The user is off-hook idle; the switch selects the alerting call appearance
    and answers the call.
    The user is off-hook listening to dial tone; the switch drops the dial tone
    call appearance and answers the alerting call on the alerting call
    appearance.
    A held call is answered on the held call appearance, providing the user is not
    busy on another call.
    5-10  Issue 4  September 1995 
    						
    							ASAI and Domain Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
    A bridged call is answered on the bridged call appearance, providing the user is
    not busy on another call, or the exclusion feature is not active for the call.
    An Automatic Callback (ACB), PCOL, or TEG call is answered on a free call
    appearance, providing the user is not busy on another call.
    A multifunction station user can also have other call appearances with alerting,
    bridged, or held calls while requesting the Third Party Answer capability on a call.
    If the station is active on a call (talking), listening to reorder/intercept tone, or
    does not have an idle call appearance (for ACB, ICOM, PCOL, or TEG calls) at
    the time the Third Party Answer capability is requested, the request is denied.
    Analog Station Operationbbbbbbbbbbbbbbb
    For an analog station user, this capability is successful only under the following
    circumstances:
    The user is being alerted on-hook (and is manually taken off-hook within
    five seconds).
    The user is off-hook idle (or listening to dial tone) with a call waiting; the
    switch drops the dial tone (if any) and answers the call waiting call.
    The user is off-hook idle (or listening to dial tone) with a held call (soft or
    hard); the switch drops the dial tone (if any) and answers the specified
    held call (there could be two held calls at the set, one soft-held and one
    hard-held).
    An analog set may only have one or two held calls when invoking the Third Party
    Answer capability on a call.  If there are two held calls, one is soft-held, the other
    hard-held.  Third Party Answer of any held call (in the absence of another held
    call and with an off-hook station) resets the switch-hook flash counter to zero, as
    if the user had manually gone on-hook and answered the alerting/held call.  Third
    Party Answer of a hard-held call (in the presence of another, soft held call, and
    with an off-hook station), leaves the switch-hook flash counter unchanged.  Thus,
    the user may use subsequent switch-hook flashes to effect a conference
    operation between the previously soft-held call and the active call (reconnected
    from hard-hold).  Third Party Answer of a hard-held call in the presence of
    another soft-held call and with the station on-hook is denied.  This is consistent
    with manual operation because when the user goes on-hook with two held calls,
    one soft- and one hard-held, the user is re-alerted and goes off-hook, and the
    soft-held call is retrieved.
    If the station is active on a call (talking) or listening to reorder/intercept tone at
    the time the Third Party Answer capability is requested, the request is denied
    (CS0/17 Ð User Busy).
    Issue 4  September 1995  
    5-11 
    						
    							ASAI and Domain Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
    Third Party Selective Holdbbbbbbbb
    The adjunct uses this capability to place a controlled extension on hold.  The
    effect is as if the specified party depressed the hold button on his or her terminal
    to locally place the call on hold.  For analog sets (phones) with only one call
    active, selective hold places the call on conference hold (the same as if the
    switch-hook was flashed once).  For analog sets which already have a held call,
    this request places the active call on hard hold.
    Information Flowbbbbbbbbbbbbbbb
    The adjunct expects a response to its request.
    The switch either:
    Ð Places the call on hold and sends the adjunct an acknowledgement, or
    Ð Denies the request (see causes below)
    Third Party Selective Hold Parameterbbbbbbbbbbbbbbb
    call_id[mandatory]  Identifies the call to be placed on hold
    ACK (Positive Acknowledgement)
    Parameters
    bbbbbbbbbbbbbbb
    None for this capability
    Denial (NAK) Causesbbbbbbbbbbbbbbb
    The switch issues one of the following reasons as the cause for ending the
    association:
    Invalid association (CS0/81)
    The association does not exist.
    Invalid number/domain (CS0/28)
    The number contained in the request is an invalid call_id value.
    Invalid state (CS0/98)
    The call is not in the talking state in order to be put on hold.
    Mandatory IE missing (CS0/96)
    The required call_id is missing in this request.
    Invalid information element contents (CS0/100)
    The party_id or call_id value of the request is invalid (for example, the
    party is alerting).
    User Busy (CS0/17)
    The user is busy with another ASAI request. |
    5-12  Issue 4  September 1995 
    						
    							ASAI and Domain Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
    Invalid call type (CS3/43) |
    The call cannot be held due to the type of call (for example, emergency, |
    wakeup, or service observed).
    Protocol Error (NAK) Causebbbbbbbbbbbbbbb
    The switch issues the following cause for a protocol processing error:
    Protocol error (CS0/111)
    The Q.932 protocol has been violated or the capability invoked is not
    consistent with this association.  For example, invoking a Third Party
    Domain Control Request over a Call Control association is inconsistent.
    NOTE:
    For more information regarding protocol errors and a complete list of
    reason codes (cause values), see the 
    DEFINITY Communications
    System CallVisor ASAI Protocol Reference
    , 555-230-221.
    Considerationsbbbbbbbbbbbbbbb
    The adjunct must know the call_id before placing the extension on hold.
    If the call is already on hold at the controlled station, when the switch receives
    the request, a positive acknowledgement (ACK) is returned.  See the ``Third
    Party Reconnect section in Chapter 4 for additional ``Considerations.
    Issue 4  September 1995  
    5-13 
    						
    							ASAI and Domain Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
    Third Party Reconnectbbbbbbbb
    The adjunct uses this controlling capability to reconnect a held call to a station.
    Information Flowbbbbbbbbbbbbbbb
    The adjunct expects a response to its request.
    The switch either:
    Ð Reconnects the call after validating the parameters, or
    Ð Denies the request if the call_id parameter is incorrect
    Third Party Reconnect Parametersbbbbbbbbbbbbbbb
    call_id[mandatory]  Identifies the call to be reconnected
    ACK (Positive Acknowledgement)
    Parameters
    bbbbbbbbbbbbbbb
    None for this capability
    Denial (NAK) Causesbbbbbbbbbbbbbbb
    The switch issues one of the following reasons as the cause for ending the
    association:
    Invalid association (CS0/81)
    The association does not exist.
    Invalid number/domain (CS0/28)
    The call_id is incorrect or invalid.
    Invalid state (CS0/98)
    The call is not currently in the hold state so it cannot be reconnected.
    Mandatory Information Element missing (CS0/96)
    The call_id is missing in the request.
    Resources not available (CS3/43) |
    The call cannot be reconnected due to too many parties on the call or |
    other switch-specific resource problems.
    No User Responding (CS0/18)
    The party was on-hook when the request was made and it did not go
    off-hook within five seconds (call remains held).
    5-14  Issue 4  September 1995 
    						
    							ASAI and Domain Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
    Protocol Error (NAK) Causebbbbbbbbbbbbbbb
    The switch issues the following cause for a protocol processing error:
    Protocol error (CS0/111)
    The Q.932 protocol has been violated or the capability invoked is not
    consistent with this association.  For example, invoking a Third Party
    Domain Control Request over a Call Control association is inconsistent.
    NOTE:
    For more information regarding protocol errors and a complete list of
    reason codes (cause values), see the 
    DEFINITY Communications
    System CallVisor ASAI Protocol Reference
    , 555-230-221.
    Considerationsbbbbbbbbbbbbbbb
    The adjunct uses previously acquired call_id information about the call to release
    it from the held state.  The call must have been placed on (hard or soft) hold from
    the station set or via the adjunct.
    If the party is already reconnected on the specified call when the switch receives
    the request, an ACK is returned.
    Issue 4  September 1995  
    5-15 
    						
    							ASAI and Domain Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
    Redirect Callbbbbbbbb
    The adjunct uses this capability to re-route a call that is already alerting a station
    extension.
    Information Flowbbbbbbbbbbbbbbb
    The adjunct expects a response to its request.
    The switch either:
    Ð Redirects the call and drops the alerting party after validating the
    parameters, or
    Ð Denies the request and maintains the alerting party
    Domain Control Redirect Call Parametersbbbbbbbbbbbbbbb
    call_id[mandatory] The call_id of the call to be redirected
    redirected-to-
    number[mandatory] Identifies the number the call is routed to (may be
    on or off-switch).  If more than 24 digits are provided, only the
    first 24 are used.
    ACK (Positive Acknowledgement)
    Parameters
    bbbbbbbbbbbbbbb
    An acknowledgment is sent to the adjunct if the request is successfully
    completed and the call stops alerting the redirecting station.
    Denial (NAK) Causesbbbbbbbbbbbbbbb
    The switch issues one of the following reasons as the cause for denying the
    request:
    Request is for release prior to G3V4 (CS0/111)
    This service is only available beginning with Release G3V4.
    Mandatory Information Element missing (CS0/96)
    The call_id or redirected-to number or other IE is missing in the request.
    Invalid CRV (CS0/81)
    The Call Reference Value is missing or invalid.
    Invalid destination (CS3/43)
    Invalid destinations include the following: empty (0 digits), unassigned
    extension (invalid dial plan numbers), incomplete number of digits for
    AAR/ARS pattern, or non-AAR/ARS FAC.
    Redirected-to Station Busy, or Terminating Extension Group (TEG) has
    one or more members busy (CS0/17)
    5-16  Issue 4  September 1995 
    						
    							ASAI and Domain Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
    Miscellaneous Restrictions Ð Redirected-to Number
    The redirected-to number is a Remote Access Extension, or the COR
    check fails (CS3/43).
    The redirected-to number cannot be the same as the originating number
    or the redirecting number (CS3/42).
    Miscellaneous Restrictions Ð Redirecting Number
    The redirecting number is not a station extension, the call_id does
    not exist, or the call is not in the alerting state or is redirecting while
    in vector processing (CS3/63)
    The redirecting station is origination-restricted (CS3/43), or the call
    is redirecting on the first leg of a switch-classified call (CS3/42).
    Calls that result in intercept treatment will not be allowed to redirect
    even if normally such calls would be sent to an attendant (CS3/63).
    Protocol Error (NAK) Causesbbbbbbbbbbbbbbb
    The switch issues the following cause for generating a protocol processing error:
    Protocol error (CS0/111)
    The Q.932 protocol has been violated or the capability invoked is not
    consistent with this association.  For example, invoking the Third Party
    Make Call capability on a Domain Control association is inconsistent.
    NOTE:
    For more information regarding protocol errors and a complete list of
    reason codes (cause values), see the 
    DEFINITY Communications
    System CallVisor ASAI Protocol Reference
    , 555-230-221.
    Considerationsbbbbbbbbbbbbbbb
    With this service, when a call is routed to a new number, if the new number is a
    station on the switch, it begins alerting (if available to receive the call) and the
    originally-alerted call is dropped.  At this point, this alerting call is eligible to be
    redirected again.  If the new (redirected-to) number is off-premises, the call is
    routed there and the caller hears call progress tones. In this case, the call may
    not be redirected again.
    For both on- and off-switch redirection, the switch will not drop the redirecting
    party until success is assured.  It is at this point that the positive
    acknowledgement is sent.  If the switch cannot redirect the call, NAK is provided
    and the alerting call will not be affected.
    There is a special case where an adjunct can receive a positive
    acknowledgment, but the redirect may fail.  For example, if the call is redirected
    to an off-premises number and the network trunk is seized, the switch considers
    this successful redirection and drops the redirecting party.  The caller may hear
    any network-provided call progress tones.
    Issue 4  September 1995  
    5-17 
    						
    							ASAI and Domain Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
    Party_ids may be re-used if the call is redirected more than once.
    An application using this feature should consider the timing for redirecting a call,
    particularly when redirecting away from a display user. If a display station user
    gets an incoming call and the application redirects it immediately, the station user
    may not have enough time to read the display (the incoming call information)
    before it is cleared by the application.
    Since it is not possible to redirect busy calls, if possible an application should
    check whether the call had resulted in a busy condition before attempting to
    redirect it.  This may be done if the application receives the appropriate call
    progress events from the switch (such as ``busy, ``reorder/denial, or
    ``connected).
    The call state may change between the Alerting event and the service request for
    redirection. An application should therefore expect certain NAKs and handle
    them appropriately.
    5-18  Issue 4  September 1995 
    						
    							ASAI and Domain Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
    Third Party Mergebbbbbbbb
    The adjunct requests that two calls (already existing at the domain-controlled
    station) be merged.
    Information Flowbbbbbbbbbbbbbbb
    The adjunct expects a response to its request.
    The switch either:
    Ð Validates the parameters, sends an acknowledgement to the adjunct, and
    merges the two calls, or
    Ð Denies the request if the parameters are invalid
    Third Party Merge Parametersbbbbbbbbbbbbbbb
    common_party_id[ignored] Identifies the common endpoint with regard to
    the merged call.  This endpoint must have one call on
    hold and one active (talking) state call.
    call_id[mandatory] The held call_id to be merged with the active
    call.
    call_id2[mandatory] The active call_id to be merged with the held
    call.
    conf/trans_flagThe conf/trans_flag must be PRESENT.  If set to
    TRANSFER, the call transfers and the controlled station is
    dropped from the call.  The transfer operation merges the
    two existing calls and drops the controlled station from the
    call.
    An acknowledgement is sent to the controlling adjunct
    (with party/extension information) when the transfer
    function is successful.
    If the conf/trans_flag is CONF, the call conferences. The
    controlled station is retained in the resultant call.
    ACK (Positive Acknowledgement)
    Parameters
    bbbbbbbbbbbbbbb
    An acknowledgement is sent with a call identifier for the merged call (call_id), a
    list of up to six party identifiers for the parties on the call (party_id), and a list of
    up to six extensions of the parties on the call to the controlling adjunct when the
    conference is complete.
    Issue 4  September 1995  
    5-19 
    						
    All ATT manuals Comments (0)

    Related Manuals for ATT DEFINITY Communications System Generic 3V4 Instructions Manual