Application Programming Guide


 Return to Library  Contents  Previous Topic  Bottom of Topic  Next Topic  Index  Help


Chapter 3. Agent Operations

   

This chapter includes sections about the CallCoordinator APIs related to agent operations. These sections are:

Each section explains the function of the API and describes when it would be useful. It also explains how to use the APIs and defines the CICS communication data area required for each one.

The CallCoordinator APIs are defined as general-use programming interfaces. See "Programming Interfaces" for a definition of general-use programming interfaces.


Sign On API (CAMI710C)

             

What This API Does

 

This API allows an application program to sign an agent on to CallCoordinator, enabling coordinated voice and data. This ensures that when calls come in or are transferred, the associated panel is displayed along with the call.    

The invoking program, using the terminal status field of this API, can request the following actions:

Also, for the actions that perform a sign-on, the following processing occurs:

In addition to the above actions, certain input fields in the Commarea can be updated. See Table 11 for a complete list of input data for this API.  

When to Use This API

CallCoordinator provides a Sign On/Off panel which agents can use to sign on and off of CallCoordinator. It is invoked by Transaction ID (V810). Refer to the Operations section of the CallPath CallCoordinator/CICS System Management Guide for information about this function.

You can use this API, in combination with the Sign Off API, to replace the CallCoordinator-supplied sign on/off panel.  

How to Use This API

Before executing this API, execute the Inquire Agents API (see "Inquire Agents API (CAMI720C)") to get the required agent information.

You can use this API, in combination with the Sign Off API, to replace the CallCoordinator-supplied sign on/off function. There are two ways to do this:

The requirements for each action this API performs are as follows:

For all of the above actions, you can blank out updatable fields in the Agents VSAM file and Agents Table by setting the input fields to low values.

This API validates all input before applying any updates. If an input field fails an edit, the value returned in the RETURN-CODE field is a 9, the value returned in the REASON-CODE field identifies the input field that is not valid and the ERROR-MSG field contains the number of the message that explains the error (refer to the CallPath CallCoordinator/CICS Problem Determination for the message text).

To use the Sign On API in your application program, do the following:

  1. Create a CICS communication data area in working storage of the program by copying the communications data area for this API.     The fields for this data area are described in Table 11. A layout for this data area is provided in the CallCoordinator SEZPCOPY target library, member name CAMC710. Refer to the library member for the actual field names.

    If calling the API from COBOL II or later, INITIALIZE the Communication data area (CAMC710-COMMAREA-DATA) before setting any of the fields.

    Table 11. CICS Communication Data Area for the Sign On API (CAMC710)
    Field Attributes In/out Description
    COMMAREA N/A N/A 01 level name.
    COMMAREA-LEN PIC S9(04) COMP VALUE +1024 N/A Length in bytes of the CICS communication data area.
    COMMAREA-DATA N/A N/A 03 level name.
    FROM-PROGRAM-NAME PIC X(08) In The name of the program invoking this API.
    TO-PROGRAM-NAME PIC X(08) In The name of this API (CAMI710C).
    RETURN-CODE PIC 9(04) Out Indicates the result of the attempted operation. In some situations, it is necessary to examine the reason code as well as the return code to determine the specific cause of the problem.

    0
    No errors were detected. The request has been successfully processed.

    1
    The entry was not found.

    2
    The Agent ID parameter was not specified.

    3
    The terminal ID was not specified.

    4
    One or more CallCoordinator modules (CTM or MIS) are shut down. See the status flag fields for these modules.

    5
    Not used.

    6
    A VSAM error was encountered while accessing the Agents VSAM file.

    7
    The Agent ID specified in CAMC710-AGENT-ID for a CAMC710-STATUS-ADD (an add) already exists in the VSAM file and so cannot be added.

    8
    API routing error. See the reason codes under "API Router".

    9
    See REASON-CODE.
    SRCH-SWITCH-ID PIC X(08) N/A This field is not used.
    FILLER PIC X(02) N/A Spaces. Reserved for future use.
    SRCH-EXT-ID PIC X(10) N/A This field is not used.
    SRCH-TERM-ID PIC X(08) N/A This field is not used.
    SRCH-AGENT-ID PIC X(10) N/A This field is not used.
    CTM-STATUS-FLAG PIC X(10) Out Status of the Call Tracking module.
    Y
    Call Tracking module is running.
    N
    Call Tracking module is not running.
    MIS-STATUS-FLAG PIC X(01) Out Status of the MIS module.
    Y
    The MIS module is running.
    N
    The MIS module is not running.
    COM-STATUS-FLAG PIC X(01) Out This field is set to the same value as CTM-STATUS-FLAG.
    SAVE-CHANGES-FLAG PIC X(01) N/A This field is no longer used.
    REASON-CODE PIC 9(04) Out Indicates the result of the attempted operation. For more information, refer to the System Log.

    0
    Reason code not applicable.

    1
    CallPath/CICS error.

    2
    CallPath/CICS is down but agent was signed on.

    3
    The Switch ID associated with this agent's extension is not defined to CallPath/CICS.

    4
    CallPath/CICS encountered a communication error with the switch.

    5
    A CallPath/CICS error was encountered.

    12
    The Agent ID passed is not valid.

    14
    During the signon process, the entry for this agent was changed by another program. Invoke this API again to resolve this situation.

    16
    The length of the Commarea was specified incorrectly.

    17
    An error was encountered while writing to the Agents VSAM file.

    20
    An error occurred while obtaining addressability to CallCoordinator tables.

    21
    An error occurred while accessing the Agents Table.

    24
    Error signing off another agent from this terminal.

    25
    Error signing off another agent from this switch/extension.

    26
    Error signing off this agent from another terminal or switch/extension
    REASON-CODE (continued) PIC 9(04) Out Indicates the result of the attempted operation. For more information, refer to the System Log.

    29
    This agent's entry has not been activated.

    35
    Switch agent monitor set to Position ID, but no Position ID is defined for this Switch ID/Extension ID on the Extensions file.

    39
    Agent was signed on, but CallCoordinator switch setting indicates that the link is down between the switch and CallPath/CICS, or the switch is down.

    50
    SWITCH-ID not valid. See ERROR-MSG.

    51
    EXT-ID field not valid. See ERROR-MSG.

    52
    AGENT-FUNC field not valid. See ERROR-MSG.

    53
    TERM-STATUS-FLAG field not valid. Valid values are I, Y, P, U, A, or blank.

    54
    XFER-NTFN-IND not valid. Valid values are Y, N, X, C or blank.

    55
    RECOV-NTFN-IND not valid. See ERROR-MSG.

    56
    START-WITH-DATA field not valid. See ERROR-MSG.

    57
    START-WITH-DATA and INIT-TRANS-ID fields are not valid. See ERROR-MSG.

    58
    AGENT-GROUP field not valid. See ERROR-MSG.

    59
    SIGNON-MODE field not valid. Valid values are I, Y, P, or blank. See ERROR-MSG.

    60
    USER-MODE-FLAG field not valid. See ERROR-MSG.

    61
    USER-MODE-FLAG and USER-MODE-TRANS-ID fields not valid. See ERROR-MSG.

    62
    AGENT-LANGUAGE field not valid. See ERROR-MSG.

    63
    PANEL-DISPLAY-FLAG field not valid. See ERROR-MSG.

    64
    ALARM-SOUND-FLAG field not valid. See ERROR-MSG.

    80-99
    API routing error. See the reason codes under "API Router".
    ERROR-MSG PIC X(8) output Message ID identifying edit error encountered with input field.

    EZP0057E
    Switch ID not defined to CallCoordinator.
    Corresponds to reason code 50.

    EZP0009E
    A character in the extension field is not valid.
    Corresponds to reason code 51.

    EZP0059E
    A character in function field is not valid.
    Corresponds to reason code 52.

    EZP0049E
    Recovery notification indicator not valid.
    Corresponds to reason code 55.

    EZP0049E
    Start with data flag not valid.
    Corresponds to reason code 56.

    CAMX020E
    Start with data and initial transaction ID combination not valid.
    Corresponds to reason code 57.

    EZP0059E
    A character in the group field is not valid.
    Corresponds to reason code 58.

    CAMX033E
    User mode flag not valid.
    Corresponds to reason code 60.

    CAMX034E
    User mode Transaction ID not defined and user mode flag set.
    Corresponds to reason code 61.

    CAMX032E
    User mode Transaction ID defined and user mode flag not set.
    Corresponds to reason code 61.

    EZP0055E
    Agent language not defined.
    Corresponds to reason code 62.

    EZP0056E
    Agent language not available.
    Corresponds to reason code 62.

    EZP0049E
    Panel display flag not valid.
    Corresponds to reason code 63.

    EZP0049E
    Alarm sound flag not valid.
    Corresponds to reason code 64.
    FILLER PIC X(26) N/A Spaces. Reserved for future use.
    CALLPATH-COMMAREA PIC X(40) N/A This space is reserved.
    SWITCH-ID PIC X(8) In Switch identification. The switch must be defined in the Switches table. Cannot be set to low values. An entry in this field is optional.
    FILLER PIC X(2) N/A Spaces. Reserved for future use.
    EXT-ID PIC X(10) In Extension identification. A 1 to 10- character field that contains the characters A through Z, 0 through 9, & and *. Cannot be set to low values. An entry in this field is optional.
    TERM-ID PIC X(8) In CallCoordinator agent's CICS terminal identification number. An entry in this field is required only for a sign-on request. Cannot be set to low values.
    AGENT-ID PIC X(10) In This field is required.
    AGENT-FUNC PIC X(10) In The CallCoordinator agent's function code. To change this field to spaces, move low values into this field.
    TERM-STATUS-FLAG PIC X(01) In The status of the CallCoordinator agent's terminal. This field indicates the type of action to be performed. In addition, it indicates the mode the agent will be in when signed on. This is referred to as Agent Mode on the panel.

    I
    Sign on the agent, but do not automatically display the initial panel for an incoming call. This option saves the CallCoordinator panel environment for transfer to another agent. CallCoordinator also displays the panel when it receives a transferred call. Recommended for IVRs.

    P
    Sign on the agent, but do not automatically display any panels. This option saves the panel environment for transfer to another agent. Recommended for agents who use their terminals for non-CallCoordinator work (casual users).

    Y or Blank
    Sign on the agent, and display all panels for incoming calls.

    U
    Update this entry in the Agents VSAM file and Agents Table (if the agent is signed on).

    A
    Add this entry to the Agents VSAM file. When this option is used, the fields CAMC710-AGENT-ID, CAMC710-SWITCH-ID, CAMC710-EXT-ID and CAMC710-SIGNON-MODE are mandatory.
    INIT-TRANS-ID PIC X(08) In Indicates the CICS transaction invoked to display the first panel the agent uses to handle a call. To change this field to spaces, move low values into this field.
    XFER-NTFN-IND PIC X(01) In Indicates whether to notify the CallCoordinator agent when the application panel is successfully transferred to another agent or removed by a save operation. Also indicates whether the panel is to be cleared when the transfer is completed.
    Y
    Notify the agent only.
    X
    Notify the agent and clear the screen.
    C
    Clear the panel only.
    N
    Do not notify the agent or clear the screen.
    Blank
    Process as defined in the CallCoordinator System Setting Panel.

    To change this field to spaces, move low values into this field.

    RECOV-NTFN-IND PIC X(01 In Indicates whether to send a message to the CallCoordinator agent's terminal when the switch has been restarted.

    Y
    Send message.

    N
    Do not send message.

    Blank
    Process as defined in the COR Telephony Settings panel.

    To change this field in the Agents VSAM file and Agents Table to spaces, move low values into this field.

    USER-MODE-TRANS-ID PIC X(08) In Transaction ID of a user-written panel control program to be used for the CallCoordinator agent. To change this field to spaces, move low values into this field.

    Y (yes) in this field indicates use of the Transaction ID in the User transaction field of the COR Telephony Settings panel. This can also be accomplished by leaving this field blank and setting the USER-MODE-FLAG field to Y.

    LINK-DOWN-FLAG PIC X(01) N/A This field is not used.
    LINK-UP-FLAG PIC X(01) N/A This field is not used.
    RESTART-FLAG PIC X(10) N/A This field is not used.
    START-WITH-DATA- FLAG PIC X(01) In Indicates whether CallCoordinator passes the Initiate With Data Interface data block to the initial transaction at start time. See "Initiate With Data Interface (CAMC500)". Valid values are:

    Y
    Send data.

    N
    Do not send data.

    I
    Return immediate without data

    R
    Return immediate with data

    Blank
    Process as defined in the COR Telephony Settings panel. To change this field to spaces, move low values into this field.
    FILLER PIC X(03) N/A Spaces. Reserved for future use.
    POSITION-ID PIC X(08) N/A The position ID that is defined on the switch (if applicable to your switch) that is the alternate address or identifier for the extension ID. Used for call tracking. This field cannot be updated with this API.
    AGENT-CLASS PIC X(01) In A 1-character user defined sort field.

    To change this field to spaces, move low values into this field.

    AGENT-GROUP PIC X(08) In A 1-to 8-character alphanumeric customer defined field to categorize agents.

    To change this field in the Agents VSAM file and Agents Table to spaces, move low values into this field.

    SIGNON-MODE PIC X(01) In Indicates the signon mode of the agent. Referred to as the Agent Mode on panels.

    This field cannot be set to low values.

    The updated value of this field is usually determined from the TERM-STATUS-FLAG field. For example, the value you pass in the SIGNON-MODE field is ignored if the value you pass in the TERM-STATUS-FLAG field is a Y, P, I, or blank. If the value you pass in the TERM-STATUS-FLAG field is a Y, P, I, or blank, the value of the SIGNON-MODE field is set to Y, P, and I respectively. However, if the value you pass in the TERM-STATUS-FLAG field is a U, then the value you pass in the SIGNON-MODE field is used as specified.

    Y
    Normal signon mode.

    P
    Disabled signon mode

    I
    Signon mode where the initial panel is not displayed when a call comes in.
    AGENT-SIGNON- STATUS PIC X(01) N/A Indicates the signon status of the agent. Referred to on panels as Signed On. This field cannot be updated.

    I
    Agent is signed on to CallCoordinator.

    Blank
    Agent is not signed on.
    USER-MODE-FLAG PIC X(01) In Indicates whether panel handling will be performed in User or Auto mode.

    Y
    User mode.

    Blank
    Auto mode.

    To change this field to spaces, move low values into this field.

    AGENT-LANGUAGE PIC X(03) In The NLS language code for this agent. The code used to determine the language to be used when displaying panels and messages. If not entered, the agent language code in the COR General Settings panel will be used (refer to CallPath CallCoordinator/CICS System Management Guide ).
    ENU
    US English

    To change this field to spaces, move low values into this field.

    PANEL-DISPLAY- FLAG PIC X(01) In Indicates whether the panel ID of the panel is to be displayed.

    Y
    Display Panel ID.

    N
    Do not display Panel ID.

    Blank
    Process as defined in the COR General Settings panel.

    To change this field to spaces, move low values into this field.

    ALARM-SOUND-FLAG PIC X(01) In Indicates whether the terminal alarm should be sounded when messages are displayed to the screen.

    Y
    Sound alarm.

    N
    Do not sound alarm.

    Blank
    Process as defined in the COR General Settings panel.

    To change this field to spaces, move low values into this field.

    RECORD-STATUS PIC X(01) N/A Indicates the status of this entry in the Agents VSAM file. This field cannot be updated with this API.

    N
    Agent entry not activated.

    Y
    Agent entry active.
    CALL-V795-FLAG PIC X(01) IN Indicates whether V795 transaction is to be called during sign-on.

    Y
    V795 called.

    -
    V795 called.

    N
    V795 not called.
    TOR-SYSID PIC X(4) N/A The CICS SYSID of the TOR where the agent is signed on.
    COR-SYSID PIC X(4) N/A The CICS SYSID of the COR where the agent is signed on.
    USER-AREA PIC X(100) IN User area.
    FILLER PIC X(673) N/A Spaces. Reserved for future use.

  2. Collect and validate the input data for the API. See the Agent Sign-on panel in CallPath CallCoordinator/CICS System Management Guide to determine the edits you need to perform.  

  3. Move the input data to the input fields of the CICS communication data area created for this API.

  4. Code the following CICS command into your application program:
          EXEC CICS LINK PROGRAM('CAMI710C')
                         COMMAREA(CAMC710-COMMAREA)
                         LENGTH(CAMC710-COMMAREA-LEN)
                         END-EXEC.
    

  5. Test the value returned in the return code field in the CICS communication data area to determine if operation of the API was successful. (The reason code field provides additional information about the results of the operation.)

  6. If operation of the API was not successful, take action applicable to the error indicated by the return code and reason code.

If operation of the API is successful, the signon request is completed and the Agents Table is updated.

SignOn Validation

       

You can use the Inquire Agents API to validate an agent's signon request. For more information, see "Inquire Agents API (CAMI720C)".


Sign Off API (CAMI715C)

           

What This API Does

This API instructs CallCoordinator to sign off an agent. This removes the agent's entry from the Agents Table and ends automatic terminal display for incoming calls. The sign-off request must specify the terminal ID (SRCH-TERM-ID) of the agent. See Table 12 for a list of input data for this API.  

When to Use This API

CallCoordinator provides a Sign On/Off panel that agents can use to sign on to and off of CallCoordinator. It is invoked by Transaction ID (V810). Refer to CallPath CallCoordinator/CICS System Management Guide for more information about this panel.

You can use this API, in combination with the Sign On API, to replace the CallCoordinator-supplied sign on/off function. There are two ways to do this:

In either case, your application program uses this API to send the agent sign off request to CallCoordinator.  

How to Use This API

To use the Sign Off API in your application program, do the following:

  1. Create a CICS communication data area in working storage of this program by copying the communication data area for this API.     The fields for this data area are described in Table 12. A layout for this data area is provided in the CallCoordinator SEZPCOPY target library, member name CAMC715. Refer to the library member for the actual field names.

    If calling the API from COBOL II or later, INITIALIZE the Communication data area (CAMC715-COMMAREA-DATA) before setting any of the fields.


    Table 12. CICS Communication Data Area for the SignOff API (CAMC715)
    Field Attributes In/out Description
    COMMAREA N/A N/A 01 level name.
    COMMAREA-LEN PIC S9(04) COMP VALUE +1024 N/A Length in bytes of the CICS communication data area.
    COMMAREA-DATA N/A N/A 03 level name.
    FROM-PROGRAM-NAME PIC X(08) In The name of the program invoking this API.
    TO-PROGRAM-NAME PIC X(08) In The name of this API (CAMI715C).
    RETURN-CODE PIC 9(4) Out Indicates the result of the attempted operation. In some cases, RETURN-CODE and REASON-CODE together indicate the cause of a problem.

    0
    No errors detected. The agent has been successfully signed off CallCoordinator.

    1
    The terminal ID was not found on the Agents Table. The agent is not signed on.

    8
    API routing error. See the reason codes under "API Router".

    9
    See REASON-CODE.
    FILLER PIC X(18) N/A Spaces. Reserved for future use.
    SRCH-TERM-ID PIC X(8) In The CICS ID of the CallCoordinator agent's terminal to be signed off.
    REASON-CODE PIC 9(4) Out This code is used in conjunction with the return code. It further defines the results of the operation.

    0
    Reason code is not applicable.

    14
    The date and time do not match the existing entry in the Agents Table. (The module that updates the Agents Table compares the date and time in the communication data area with that of the entry in the table. If the two don't match, it means that another module has updated this entry between the reading and writing of this entry. This API should be used again to resolve this problem.)

    16
    The length of the Commarea was specified incorrectly.

    17
    An error occurred when writing to the Agents VSAM file. See the System Log for more information.

    20
    An error occurred obtaining addressability to CallCoordinator tables. See the System Log for more information.

    21
    An error occurred while accessing the Agents Table. See the System Log for more information.

    35
    Switch agent monitor set to Position ID, but no Position ID exists for this switch ID/Extension ID.

    80-99
    API routing error. See the reason codes under "API Router".
    FILLER PIC X(48) N/A Spaces. Reserved for future use.
    CALLPATH-COMMAREA PIC X(40) N/A This field is reserved.
    FILLER PIC X(884) N/A Spaces. Reserved for future use.
     

  2. Collect the input data for the API. Required input is the agent's terminal ID. See Table 12 for descriptions of the input fields for the data area of the API.

  3. Move the data to the input fields of the CICS communication data area.

  4. Code the following CICS command into your application program:
          EXEC CICS LINK PROGRAM('CAMI715C')
                         COMMAREA(CAMC715-COMMAREA)
                         LENGTH(CAMC715-COMMAREA-LEN)
                         END-EXEC.
    

  5. Test the value returned in the return code field in the CICS communication data area to determine if the operation of the API was successful. (The reason code field provides additional information about the results of the operation.)

  6. If operation of the API was not successful, take action applicable to the error indicated by the return code and reason code.

If operation of the API was successful, the specified agent is signed off of CallCoordinator.


Inquire Agents API (CAMI720C)

         

What This API Does

 

This API retrieves an agent's entry from the CallCoordinator Agents Table or the Agents VSAM file.       The Agents VSAM file contains all agents defined to CallCoordinator. Only signed on agents are in the Agents Table. Both contain the same information for a signed on agent except for the terminal ID and agent sign-on status (they are set to blank in the Agents VSAM file). Your application program finds the entry using one or more of the following search fields:

See Table 13 for a complete list of input data for this API.

Your application program can use this API to get data such as the following:

Besides retrieving information for an agent using specific search criteria, this API can also retrieve entries from the Agent Table (Switch ID/Extension ID sequence) or Agents VSAM file (agent ID sequence) sequentially. The file is searched sequentially beginning with the first entry. The sequential retrieval is not restricted to agents defined to CallCoordinator only.

The output data provided by this API is described in Table 13.  

When to Use This API

The Agents Table has data for all signed on agents that CallCoordinator needs to coordinate terminal displays with incoming calls. Your program can update this data by first using this API to retrieve an entry, and then using the Sign On API to update it. Much of this data is provided during CallCoordinator installation. Refer to CallPath CallCoordinator/CICS System Management Guide for more information.

An entry is placed in the Agents Table when an agent signs on. This enables CallCoordinator to determine which agents currently can receive calls.          

In systems where agents use different extensions each day or where CICS assigns terminals a new terminal ID at sign on (auto install), the Agents Table is updated for the time the agent is signed on. This API can retrieve the latest information indicating which terminal is assigned to which extension and agent.        

Another use of this API is to enable your screen control program to do either of the following:      

See Chapter 5, "Screen Control" for more information about writing user screen control programs.  

How to Use This API

To retrieve entries from the Agents Table (contains signed on CallCoordinator agents only), the requirements are: To retrieve entries from the Agents VSAM file the requirements are:

To use the Inquire Agents API in your application program, do the following:

  1. Create a CICS communication data area in working storage by copying the communication data area for this API.     The fields for this data area are described in Table 13. This layout is provided in the CallCoordinator SEZPCOPY target library, member name CAMC720. Refer to the library member for the actual field names.

    If calling the API from COBOL II or later, INITIALIZE the Communication data area (CAMC720-COMMAREA-DATA) before setting any of the fields.

    Table 13. CICS Communication Data Area for the Inquire Agents API (CAMC720)
    Field Attributes In/out Description
    COMMAREA N/A N/A 01 level name.
    COMMAREA-LEN PIC S9(04) COMP VALUE +1024 N/A Length in bytes of the CICS communication data area.
    COMMAREA-DATA N/A N/A 03 level name.
    FROM-PROGRAM-NAME PIC X(08) In The name of the program invoking this API.
    TO-PROGRAM-NAME PIC X(08) In The name of this API (CAMI720C).
    RETURN-CODE PIC 9(04) Out Indicates the result of the attempted operation. In some situations, it is necessary to examine the reason code as well as the return code to determine the specific cause of the problem.

    0
    No errors detected. The entry was successfully retrieved.

    1
    No entry was found using the search criteria for a Get-next entry. Either the Switch ID and Extension ID, Terminal ID or Agent ID was not found in the Agents Table.

    8
    API routing error. See the reason codes under "API Router".

    9
    See REASON-CODE.
    SRCH-SWITCH-ID PIC X(08) In Switch identification number. Switch and Extension ID combination is the first search field.
    FILLER PIC X(02) N/A Accounts for change in Switch ID field size in previous product.
    SRCH-EXT-ID PIC X(10) In Extension identification number. Required when the switch ID is specified.
    SRCH-TERM-ID PIC (08) In Agent's terminal identification number.
    SRCH-AGENT-ID PIC X(10) In Agent's identification number.
    REASON-CODE PIC 9(04) Out Further defines the return codes that contain more than one error condition.

    16
    The length of the Commarea was specified incorrectly.

    19
    The table token used to find entries in the table has been changed.

    20
    An error occurred while addressing the CallCoordinator tables. See the System Log for more information.

    21
    An error occurred while accessing the Agents Table. See the System Log for more information.

    31
    Extension ID was not passed as a search parameter.

    32
    Switch ID was not passed as a search parameter.

    36
    The wrong search criteria was used for the type of inquiry (see REQUEST-TYPE).

    80-99
    API routing error. See the reason codes under "API Router".
    REQUEST-TYPE PIC X(01) In Indicates the type of inquiry as follows:

    Blank
    Inquire from the Agents Table.

    A
    Inquire from the Agents VSAM file.
    SRCH-SYSID PIC X(4) IN The CICS SysID of the COR in which you wish to invoke the API.
    FILLER PIC X(33) N/A Spaces. Reserved for future use.
    FILLER PIC X(18) N/A This space is reserved for CallCoordinator processing. Do not change it.
    TABLE-TOKEN-9 PIC S9(08) COMP N/A CallCoordinator processing uses this field to keep track of the position in the table. It is for CallCoordinator use only.
    TABLE-TOKEN-AGSW PIC X(08) N/A CallCoordinator processing uses this field to keep track of the position in the table. It is for CallCoordinator use only.
    TABLE-TOKEN-AGENT PIC X(10) N/A CallCoordinator processing uses this field to keep track of the position in the table. It is for CallCoordinator use only.
    SWITCH-ID PIC X(08) Out Switch identification number. In the previous product, this field was named CBX-ID. It was PIC X(10).
    FILLER PIC X(02) N/A Accounts for the change in the Switch ID field size from the previous product.
    EXT-ID PIC X(10) Out Extension identification number
    TERM-ID PIC X(08) Out The agent's terminal identification number
    AGENT-ID PIC X(10) Out The CallCoordinator agent's identification number
    AGENT-FUNC PIC X(10) Out The CallCoordinator agent's function code
    TERM-STATUS-FLAG PIC X(01) Out The status of the CallCoordinator agent's terminal. This value is based on the value of SIGNON-MODE (referred to as the Agent Mode on panels), and the AGENT-SIGNON-STATUS. If SIGNON-STATUS is I, then this field is set to the value of SIGNON-MODE. If SIGNON-STATUS is not equal to I, this field is set to blank.

    Blank
    The terminal is signed off.

    I
    The agent is signed on, but no initial screen is displayed with a telephone call.

    Y
    The CallCoordinator agent is signed on. All screens are displayed.

    P
    The CallCoordinator agent is signed on. The agent's terminal is disabled. No screens are displayed.
    INIT-TRANS-ID PIC (08) Out The CICS transaction invoked to display the first screen.
    XFER-NTFN-IND PIC X(01) Out Whether to notify the CallCoordinator agent when the application screen has been successfully transferred to another agent or removed by a save. Also indicates whether the screen is cleared when the transfer has been completed.

    Y
    Notify the agent.

    X
    Notify the agent, and clear the screen.

    C
    Clear the screen only.

    N
    Do not notify the agent or clear the screen.
    RECOV-NTFN-IND PIC X(01) Out Whether to send a message to the CallCoordinator agent's terminal when the switch has been restarted.

    Y
    Send a message to the CallCoordinator agent's terminal.

    N
    Do not send a message.

    Blank
    Process as defined in the COR Telephony Settings panel.
    USER-MODE-TRANS-ID PIC X(08) Out The application transaction specified to handle screen processing when the CallCoordinator agent is in user mode.

    This value is based on the value of USER-MODE-FLAG and USER- TRANS-ID in the Agents Table. For example:

      • If USER-TRANS-ID is defined for this agent entry, the same value is used in this field.

      • If USER-TRANS-ID is blank for this agent entry, and the USER-MODE-FLAG is Y, then a Y will be put in this field.

      • If both of these values are blank for this agent entry, then this field is set to blank.
    LINK-DOWN-FLAG PIC X(01) Out Valid values are:

    Y
    A link-down message has been sent to this terminal.

    N
    No message has been sent.
    LINK-UP-FLAG PIC X(01) Out Valid values are:

    Y
    A link-up message has been sent to this terminal.

    N
    No message has been sent.
    SWITCH-RESTART- FLAG PIC X(01) Out Valid values are:

    Y
    A restart message has been sent to this terminal.

    N
    No message has been sent.

    In the previous product, this field was called CBX-RESTART-FLAG.

    SPM-START-DATA- FLAG PIC X(01) Out Indicates whether the system passes data (including the caller number, target number, control number, and other data) when the CallCoordinator Screen Control Module starts the initial transaction. Valid values are:

    Y
    Send data.

    N
    Do not send data.

    Blank
    Process as defined in the COR Telephony Settings panel.

    I
    Return immediate without data

    R
    Return immediate with data
    FILLER PIC X(03) N/A Spaces. Reserved for future use.
    POSITION-ID PIC X(08) Out The Position ID that is defined on the switch (if applicable to your switch) that is the alternate address or identifier for the extension ID.
    AGENT-CLASS PIC X(01) Out User-defined class of the specified CallCoordinator agent. Used to sort records.
    AGENT-GROUP PIC X(08) Out A customer defined field used to group agents.
    SIGNON-MODE PIC X(01) Out Indicates the sign-on mode of the agent (referred to as Agent Mode on the panels).

    Y
    Normal sign on mode (all screens displayed for incoming calls).

    P
    Disabled sign on mode (no screens displayed automatically for incoming calls).

    I
    The initial screen is not displayed for an incoming call. The screen is displayed when receiving a transferred call.
    AGENT-SIGNON- STATUS PIC X(01) Out Indicates the signon status of the agent.

    I
    Signed on to CallCoordinator.

    Blank
    Not signed on.
    USER-MODE-FLAG PIC X(01) Out Indicates whether screen handling will be performed in User or Auto mode.

    Y
    Screen handling will be performed in User mode.

    Blank
    Screen handling will be performed in Auto mode.
    AGENT-LANGUAGE PIC X(03) Out The NLS language code for this agent. The code used to determine the language to be used when displaying panels and messages. If not entered, the agent language code in the COR General Settings panel will be used, (refer to CallPath CallCoordinator/CICS System Management Guide ).
    ENU
    US English
    PANEL-DISPLAY- FLAG PIC X(01) Out Indicates whether the panel ID is to be displayed.

    Y
    Display panel ID.

    N
    Do not display panel ID.

    Blank
    Process as defined in the COR General Settings panel.
    ALARM-SOUND-FLAG PIC X(01) Out Indicates whether the terminal alarm should be sounded when messages are displayed to the screen.

    Y
    Sound alarm.

    N
    Do not sound alarm.

    Blank
    Process as defined in the COR General Settings panel.
    RECORD-STATUS PIC X(01) Out The status of this entry.

    Y
    This entry is fully defined.

    N
    This entry is not fully defined.
    USER-AREA PIC X(100) Out User area
    TOR-SYSID PIC X(4) Out The CICS SYSID of the TOR where the agent is signed on.
    COR-SYSID PIC X(4) Out The CICS SYSID of the COR where the agent is signed on.
    AGENT-STATUS PIC X(2) Out This is the current status of the agent. Possible values are:
    'AL'  Agent Logged In                                                                
    'AF'  Agent Logged Off                                                               
    'RY'  Agent Ready                                                                    
    'NR'  Agent Not Ready                                                                
    'RE'  Agent Ready Explicit                                                           
    'RI'  Agent Ready Implicit                                                           
    'BY'  Agent Busy                                                                     
    'BC'  Agent Busy with Call                                                           
    'BF'  Agent Busy with Follow Up                                                      
    
    For more information on ACD status, see the section on "Feature Invoked" in CallPath/CICS for OS/390 Application Programming Guide, SC34-5393.
    ACD-GROUP PIC X(6)
    Out The ACD Group into which the agent is logged on.
    FILLER PIC X(666)
    N/A Spaces. Reserved for future use.
     

  2. Collect the input data for the API.

  3. Move the data to the input fields of the CICS communication data area.

  4. Code the following CICS command into your application program:
          EXEC CICS LINK PROGRAM('CAMI720C')
                         COMMAREA(CAMC720-COMMAREA)
                         LENGTH(CAMC720-COMMAREA-LEN)
                         END-EXEC.
    

  5. Test the value returned in the return code field in the CICS communication data area to determine if operation of the API was successful. (The reason code field provides additional information about the results of the operation.)

  6. If operation of the API was not successful, take action applicable to the error indicated by the return code and reason code.

If operation of the API is successful, the output fields in the CICS communication data area contain the data from the requested entry.    


Set Agent Mode API (CAMI745C)

           

What This API Does

This API allows an application program to update the Agent Mode field of an entry in the Agents Table and Agents VSAM file.       This turns CallCoordinator automatic panel activity on or off for the requesting agent for all subsequent calls. For example, when Agent Mode in the Agents Table is Y (all panels displayed) this API can change it to P (no panels displayed).

If the agent is participating in an active call and is controlling the screen, the agent can disable the screen activity for the current call by setting the REQUEST-TYPE to C (current call only), or B (both current call and subsequent calls). See Table 14 for description of the input data for this API.    

When to Use This API

A CallCoordinator agent might sometimes need to use a non-CallCoordinator panel display and still be available to receive CallCoordinator calls. To do this, the agent can disable automatic panel display by CallCoordinator. This prevents interruption by CallCoordinator panel display when there is an incoming CallCoordinator call. When the agent is ready to resume CallCoordinator work, the agent can use this API to re-enable CallCoordinator automatic panel activity.

CallCoordinator provides an Agent Utility menu that agents can use to enable and disable terminals for CallCoordinator automatic display.     It is invoked by Transaction ID (V870). Refer to CallPath CallCoordinator/CICS System Management Guide for more information about this menu. Application programs can use this API to replace the CallCoordinator-supplied function for terminal enabling/disabling.

A CallCoordinator agent can also re-enable CallCoordinator automatic panel activity for a single call rather than for all subsequent calls. This requires using the Agent Utility menu or the Casual User Restore API. See "Casual User Restore API (CAMI760C)".  

How to Use This API

To use the Set Agent Mode API in your application program, do the following:

  1. Create a CICS communication data area in working storage by copying the CallCoordinator-supplied communication data area for this API.   The fields for this data area are described in Table 14. This layout is provided in the CallCoordinator SEZPCOPY target library, member name CAMC745. Refer to the library member for the actual field names.

    If calling the API from COBOL II or later, INITIALIZE the Communication data area (CAMC745-COMMAREA-DATA) before setting any of the fields.

     

    Table 14. CICS Communication Data Area for the Set Agent Mode API (CAMC745)
    Field Attributes In/out Description
    COMMAREA N/A N/A 01 level name.
    COMMAREA-LEN PIC S9(04) COMP VALUE +1024 N/A Length in bytes of the CICS Communication data area.
    COMMAREA-DATA N/A N/A 03 level name.
    FROM-PROGRAM-NAME PIC X(08) In The name of the program invoking this API.
    TO-PROGRAM-NAME PIC X(08) In The name of this API (CAMI745C).
    RETURN-CODE PIC 9(04) Out Indicates the result of the attempted operation. In some cases, RETURN-CODE and REASON-CODE together indicate the cause of a problem.

    0
    AGENT-MODE was updated successfully.

    1
    The CallCoordinator agent's terminal identification number was not found in the Agents Table (reason code 11).

    2
    One of the following errors was detected in the parameters that were passed in the CICS communication data area.

    • Invalid values were assigned to the individual parameters (reason code 33).

    • An invalid combination of parameters was passed (reason code 34).

    3
    The CallCoordinator agent is not currently signed on.

    8
    API routing error. See the reason codes under "API Router".

    9
    See REASON-CODE.
    RETURN-CODE
    (continued)
    PIC 9(04) Out

    10
    This is a warning return code. The requesting agent is not participating in a call or is not controlling the screen.

    The AGENT-MODE is changed. The screen transfer enable/disable request is not completed.

    11
    This is a warning return code. The agent is requesting screen transfer enable but is not in disable status.

    The AGENT-MODE is enabled. The screen transfer enable request is not completed.

    12
    This is a warning return code. The agent is requesting screen transfer enable but the screen is currently saved.

    The AGENT-MODE is changed. The screen transfer enable request is not completed.


    AGENT-MODE PIC X(01) In Indicates the desired signon mode of the CallCoordinator agent and the agent's terminal. Used with the REQUEST-TYPE field.

    I
    Enable the agent's terminal, but do not automatically display the initial panel for an incoming call. This option saves and provides the CallCoordinator panel environment for transfer to another agent. This option also displays the panel when the agent receives a transferred call. Recommended for IVRs.

    P
    Disable the agent's terminal. Do not display any panels as a result of CallCoordinator automatically. The agent still receives CallCoordinator calls, but has manual control of panel activity. This option saves and provides the panel environment for transfer to another agent. Recommended for agents who use their terminals for non-CallCoordinator work (casual users).

    Y
    Enable the agent's terminal. Display all panels for incoming calls.
    REQUEST-TYPE PIC X(01) In Indicates desired change in Agent Mode for signon.

    T
    Change the AGENT-MODE for subsequent calls.

    C
    Change the AGENT-MODE in the current call only (when the requested AGENT-MODE is P only).

    B
    Change the AGENT-MODE both for subsequent calls and current calls. If the requested AGENT-MODE is I or Y, only subsequent calls are changed.
    WORK-TERM-ID PIC X(8) N/A The agent's CICS terminal ID.
    REASON-CODE PIC 9(04) Out Code returned from the API that further defines the return code. For more information, see the System Log.

    0
    Reason code is not applicable.

    11
    No entry was found in the Agents Table for the Term ID specified.

    14
    The date and time do not match that of the existing Agent entry. (The module that updates the Agents Table compares the date and time in the communication data area with that of the entry in the table. If the two don't match it means that another module has updated this entry between the reading and writing of this entry. This API should be used again to resolve this.)

    16
    The length of the Commarea was specified incorrectly.

    17
    An error occurred while reading or writing to the Agent file.

    20
    An error occurred obtaining addressability to the CallCoordinator tables.

    21
    An error occurred with the module that accesses the Agents Table.

    33
    Invalid values were assigned to individual parameters.

    34
    An invalid combination of parameters were passed.

    80-99
    API routing error. See the reason codes under "API Router".
    FILLER PIC X(104) N/A Spaces. Reserved for future use.
    FILLER PIC X(884) N/A Spaces. Reserved for future use.
     

  2. Collect the input data for the API. The required input data is CAMC745-REQUEST-TYPE and CAMC745-TERM-STATUS-FLAG. See Table 14 for a description of the input fields for this API.

  3. Move the data to the input fields of the CICS communication data area.

  4. Code the following CICS command into your application program:
          EXEC CICS LINK PROGRAM('CAMI745C')
                         COMMAREA(CAMC745-COMMAREA)
                         LENGTH(CAMC745-COMMAREA-LEN)
                         END-EXEC.
    

  5. Test the value returned in the return code field in the CICS communication data area to determine if operation of the API was successful. (The reason code field provides additional information about the results of the operation.)

  6. If operation of the API was not successful, take action applicable to the error indicated by the return code and reason code.

If operation of the API was successful, the agent's terminal is set to the requested mode.


Set Telephony Feature API (CAMI740C)

         

What This API Does

This API enables agents to change the state of their telephone from their terminals rather than from their telephones, using the features described here (see "Set Telephony Feature API Features"). This ability is known as hands-free telephony. The API also allows the Logon and Logoff of logical agents to ACD Groups or Skills which could be interrogated by logic within the switch to change its course of action. The data provided is validated and is sent to CallPath/CICS for OS/390, which verifies the syntax. If insufficient data is supplied or CallPath/CICS for OS/390, CallCoordinator or the requested switch is not active, a non-zero Return_Code will result. The API will wait up to 10 seconds for a response to the request from CallPath/CICS for OS/390. A negative response will result in a non-zero Return_Code, as will no response at all.

The request types for this API and fields required for each request are described in Table 15.

When to Use the Set Telephony Feature API

You would use this API anytime the state of a telephone needs to be changed according to logic in an application program as opposed to an agent deciding to manually change the state. A front-end application may also be developed which would allow the agent to set the state via the terminal instead of using the telephone.

How to Use the Set Telephony Feature API

To use the Set Telephony Feature API in your application program, do the following:

  1. Create a CICS communication data area in working storage of the program by copying CAMC740. The fields for this API are described in Table 15 (note that the field names in the figure are missing the CAMC740 prefix for the sake of brevity). A layout for this data area is provided in the CallCoordinator SEZPCOPY target library, member name CAMC740. Refer to the library member for the actual field names. The *Required codes are shown after the end of Table 15.

    If calling the API from COBOL II or later, INITIALIZE the Communication data area (CAMC740-COMMAREA-DATA) before setting any of the fields.

    Table 15. CICS Communication Data Area for Set Telephony Feature API (CAMC740)
    Field Attributes In/Out Required* Description
    COMMAREA N/A N/A N/A 01 level name.
    COMMAREA-LEN PIC S9(04) COMP VALUE +1024 N/A A Length in bytes of this communications data area.
    COMMAREA-DATA N/A N/A N/A 03 level name.
    FROM-PROGRAM-NAME PIC X(08) In A The name of the program that is linking to this API.
    TO-PROGRAM-NAME PIC X(08) In A The name of this API (CAMI740C).
    RETURN-CODE PIC S9(09) COMP Out N/A The return code can have the following values:

    0000
    No errors.
    CAMI740C did not detect any errors with the user input to the API. Receipt of this return code should be followed by successful telephony actions which produce expected result. It is possible that despite the user input being correct, the telephony subsystem is unable to honor the request, because this API does not check the Response Code issued by CallPath/CICS for OS/390.

    0001
    Switch not defined.
    The Switch-ID specified in the Commarea is not defined in the CallCoordinator Switch table.

    0002
    CallCoordinator not active

    0003
    Feature Data not valid - Activity code not valid or non-numeric data in numeric field. This API does not check for every valid value in these fields and they may be rejected by CallPath/CICS for OS/390 resulting in a CallPath/CICS for OS/390 Return Code of 5.

    0004
    CallPath/CICS for OS/390 error.
    A non-zero return code was returned from CallPath/CICS for OS/390. The CallPath/CICS for OS/390 return code is placed in the CPCICS_RETURN_CODE field in the Commarea and the program call which caused the error is placed in CPCALL.
    RETURN-CODE (continued) PIC S9(09) COMP Out N/A The return code can have the following values:

    0005
    Switch not active.
    The Switch-ID specified in the Commarea is not active.

    0006
    Feature Code not valid.

    0007
    Negative Response - see Sense-Code
    The Sense-code is placed in the SENSE-CODE field in the commarea and the Sense-code-qualifier is placed in the SENSE-QUALIFIER field in the Commarea, preceded by its length.

    0008
    API routing error. See the reason codes under "API Router".

    0009
    See REASON-CODE.

    0010
    Agent not signed on to CPCC
    SWITCH-ID PIC X(08) In A The switch upon which the API is to operate.
    AGENT-ID PIC X(20) In 1 The Agent for whom the feature is invoked.
    DIR-NUMBER PIC X(32) In A The directory number of the phone involved.
    GROUP-ID PIC X(32) In O Not currently supported by any switch.
    POOL-ID PIC X(20) In 1 The ACD Group or Skill.
    CP-PROGRAM-ID PIC X(08) Out N/A The program identifier for CallPath/CICS for OS/390 - unique to this execution of API
    CALL-PROFILE PIC X(08) Out N/A The Profile defined to CallPath/CICS for OS/390 by this API for this switch
    FEATURE-CODE PIC X(04) In A The following Feature codes are available:

    0000
    Do Not Disturb

    0001
    Forward

    0002
    Agent Activity

    0003
    Account Code

    0004
    Speaker

    0005
    Mute

    0006
    Camp for Callback

    0008
    Call Waiting

    0010
    Advanced Agent Activity
    AGENT-ACTIVITY PIC X(04) In 1 The following Activity codes are available:

    0000
    Logon

    0001
    Logoff

    0002
    Ready

    0003
    Busy

    0004
    Busy With Call

    0005
    Busy with Follow-Up

    0006
    Not Ready

    0007
    Ready Explicitly

    0008
    Ready Implicitly
    MODE PIC X(04) In 2,3 Values are:

    0000
    Start

    0001
    Stop
    TYPE PIC X(04) In 3 Values are:

    0000
    Busy

    0001
    No Answer

    0001
    Unconditional
    FWD-DIRECTORY- NUMBER PIC X(32) In 3 The target number of the Forwarding feature.
    ACCOUNT-CODE PIC X(32) In 4 Account code for current call.
    PASSWORD PIC X(20) In O Used with Advanced Agent Activity
    SENSE-CODE PIC X(04) Out N/A Returned from sub-system if Negative Response.
    CP-CALL PIC X(08) Out N/A Last CallPath/CICS for OS/390 call issued. If RC=CPCICS error, the error was a result of this call.
    AGENT-STATUS PIC X(1). In O Values are:

    Y
    Agent must be signed on

    N
    Agent need not be signed on
    Filler PIC X(99). N/A N/A Future expansion.
    CP-RETURN-CODE PIC X(04) Out N/A The Return-Code issued from CallPath/CICS for OS/390
    REASON-CODE PIC X(04) Out N/A The reason code if Return-code = 9 (other)

    0000
    No errors.

    0009
    Connect Table error.
    Error initializing the CallCoordinator Connect Table for MRO invocation of the API. Check that a Connect Table has been defined and contains the correct information regarding the region that contains CallCoordinator.

    0016
    Commarea length not valid.
    The Commarea is not the correct length (1024).

    0020
    Connect Table Access error.
    Access to CallCoordinator tables has failed. This indicates a catastrophic error requiring that CallCoordinator be restarted after a Table reload using transaction V889.

    0080-
    0099
    See the reason codes under "API Router".
    SENSE-QUAL-LENGTH PIC X(04) Out N/A Length of Sense-Qualifier, if Negative Response.
    SENSE-QUALIFIER PIC X(200) Out N/A Sense-qualifier if Negative Response.
    Filler PIC X(450). N/A N/A Reserved for future use.

    *Required codes for various Features:

    A
    Required for all Features
    O
    Optional
    1
    Required for Agent Activity and Advanced Agent Activity
    2
    Required for Do Not Disturb
    3
    Required for Call Forwarding
    4
    Required for Account Code

  2. Collect the input data for the API. The required data is shown in the table above.

  3. Move the data to the input fields of the CICS communication data area.

  4. Code the following CICS command in your application program:
    Example for COBOL:
     
          EXEC CICS LINK PROGRAM('CAMI740C')
                         COMMAREA(CAMC740-COMMAREA)
                         LENGTH(CAMC740-COMMAREA-LEN)
          END-EXEC.
    

  5. Test the value returned in the return code field in the CICS communication data area to determine if the operation of the API was successful.

  6. If the operation of the API was not successful, take action applicable to the error indicated by the return code.

  7. If the result of the API was Negative Response, check the Sense-Code and Sense-Qualifier fields. Meanings of these fields are in the CallPath/CICS for OS/390 Application Programming Guide or the CallPath Services manual for the specific switch.

  8. If the result of the API was CPCICS error, check the CPCICS Return Code and CP-Call fields. CP return codes may be found in the CallPath/CICS for OS/390 Application Programming Guide
If the operation of the API was successful, the switch will have been requested to perform the appropriate telephony functions.

Set Telephony Feature API Features

Do Not Disturb (0000)

Sets the Do Not Disturb feature on or off for agent's telephone

Mandatory Input:

From program name
To program name
Feature code
Switch ID
Directory number
Mode (set on or off)

Call Forwarding (0001)

Places the telephone in a state to forward calls to the number specified in Forward-directory-number based on the condition specified in Type field (busy, no answer or unconditional).

Mandatory Input:

From program name
To program name
Feature code
Switch ID
Directory number
Mode (set on or off)
Forward directory number
Type (condition)

Agent Activity (0002)

Note: Some switches do not support Advanced Agent Activity, although they do support Agent Activity (see "Agent Activity (0002)"). On switches that support both, either may be used, but Advanced also allows use of Password. This feature allows for the following activities:

Agent Logon:
Logs agent on to ACD Group or Skill. The agent may or may not be ready to receive calls.

Agent Logoff:
Logs agent off of ACD Group or Skill

Agent Ready:
Makes agent ready to receive calls

Agent Ready Explicitly:
Makes agent ready to receive calls and places the agent in a busy with follow up work period at the completion of the call. To leave the busy with follow up work period, the agent must explicitly indicate readiness for a new call by either using this API or invoking the feature on the telephone.

Agent Ready Implicitly:
Makes agent ready to receive calls and is automatically ready for another call upon completion of the current call.

Agent Busy:
Puts agent in busy status, not ready to handle calls, even if the connection is idle. The agent remains logged on.

Agent Busy With Call:
Puts agent in busy with call status. The agent remains logged on

Agent Busy With Follow-up
Indicates agent is not on a call, but is engaged in work resulting from a previous call. Agent remains logged on.

Agent Not Ready:
Indicates agent is not ready to handle calls, even though agent is not on a call or engaged in follow up work. Agent may be on a break. Agent remains logged on.

Mandatory Input:

From program name
To program name
Feature code
Activity code
Switch ID
Directory number
Pool Id (ACD Group or Skill)
Agent ID

Account Code (0003)

Establishes an account code to be associated with current call

Mandatory Input:

From program name
To program name
Feature code
Switch ID
Directory number
Account Code

Speaker (0004)

Turns telephone's speaker on or off

Mandatory Input:

From program name
To program name
Feature code
Switch ID
Directory number
Mode (start or stop)

Mute (0005)

Sets telephone's Mute feature on or off

Mandatory Input:

From program name
To program name
Feature code
Switch ID
Directory number
Mode (start or stop)

Camp for Callback (0006)

Sets Camp for Callback feature on or off

Mandatory Input:

From program name
To program name
Feature code
Switch ID
Directory number
Mode (start or stop)

Call Waiting (0008)

Sets Call Waiting feature on agent's telephone

Mandatory Input:

From program name
To program name
Feature code
Switch ID
Directory number
Mode (start or stop)

Advanced Agent Activity (0010)

This feature allows for the following activities:

Agent Logon:
Logs agent on to ACD Group or Skill. The agent may or may not be ready to receive calls.

Agent Logoff:
Logs agent off of ACD Group or Skill

Agent Ready:
Makes agent ready to receive calls

Agent Ready Explicitly:
Makes agent ready to receive calls and places the agent in a busy with follow up work period at the completion of the call. To leave the busy with follow up work period, the agent must explicitly indicate readiness for a new call by either using this API or invoking the feature on the telephone.

Agent Ready Implicitly:
Makes agent ready to receive calls and is automatically ready for another call upon completion of the current call.

Agent Busy:
Puts agent in busy status, not ready to handle calls, even if the connection is idle. The agent remains logged on.

Agent Busy With Call:
Puts agent in busy with call status. The agent remains logged on

Agent Busy With Follow-up
Indicates agent is not on a call, but is engaged in work resulting from a previous call. Agent remains logged on.

Agent Not Ready:
Indicates agent is not ready to handle calls, even though agent is not on a call or engaged in follow up work. Agent may be on a break. Agent remains logged on.

Mandatory Input:

From program name
To program name
Feature code
Activity code
Switch ID
Directory number
Pool Id (ACD Group or Skill)
Agent ID

Optional Input:

Group ID (not currently supported by any switch)
Password

Values for the following fields are contained in COBOL 01 levels following the Commarea definition. These may be moved to the corresponding fields in the Commarea. It is recommended that these fields be used in place of literals in case the values change in the future.

Feature Code
Activity Code
Mode
Forward Type


Casual User Restore API (CAMI760C)

               

What This API Does

Agents who use non-CallCoordinator panel displays can disable automatic panel display by CallCoordinator. This prevents interruption by CallCoordinator when there is an incoming CallCoordinator call. See "Set Agent Mode API (CAMI745C)" for more information about terminal enabling/disabling for CallCoordinator panel activity.      

The Casual User Restore API is for agents working with CallCoordinator automatic panel display disabled. It allows the agent to complete any non-CallCoordinator work and then display the proper panel for a single incoming CallCoordinator call. This API gets the operating environment and the application panel intended for that call. It restores the terminal environment so the agent can handle this one call. The restored environment includes the Execute Interface Block (EIB), screen buffer, communication data area, and any temporary storage queues (TSQs).

In this case, the agent would handle an incoming CallCoordinator call as follows:

  1. Answer the telephone and ask the caller to hold.

  2. Finish the non-CallCoordinator work.

  3. Initiate this API to restore the CallCoordinator application panel and panel environment for the call.

This restores CallCoordinator panel processing to the agent terminal for this one call only. If the agent wants to restore CallCoordinator automatic panel display for all subsequent calls, the agent must re-enable the terminal. See "Set Agent Mode API (CAMI745C)" for more information about terminal enabling/disabling for CallCoordinator panel activity.

This API functions correctly whether the casual user is signed on in Automatic mode or User mode. In order for Casual User Restore to work correctly, invoking agents terminals must be permanently disabled (P), and must be participating in a call.

During a conference call, the Casual User Restore must be invoked immediately after the first agent invokes a conference with intent to transfer the call and then dial the next agent's telephone number. The agent will then get the initial screen. If Casual User Restore is invoked after the conference button is pressed, the agent will not be able to restore anything, and will get a return code 03.

The Casual User Restore API can only be effective if CallCoordinator has received event messages from the switch that indicate that a transfer is in progress, or has been completed. The earliest possible indication is in a Call-Routed or Call-Alerting message that contains an "intent-to-transfer" indication (call-extension-indicator set to STL-CALL-EXTENSION-TO-TRANSFER), sent when the agent's telephone is alerted. The latest indication is receipt of the Call-Transferred message. Early transfer can only occur if the "intent-to-transfer" indication is provided by the switch, and the switch generates a Call-Alerting or Call_Routed event message for the casual user agent at the time