Home > Lucent Technologies > Communications System > Lucent Technologies DEFINITY Enterprise Communications Server Release 6 CallVisor PC ASAI Instructions Manual

Lucent Technologies DEFINITY Enterprise Communications Server Release 6 CallVisor PC ASAI Instructions Manual

Here you can view all the pages of manual Lucent Technologies DEFINITY Enterprise Communications Server Release 6 CallVisor PC ASAI Instructions Manual. The Lucent Technologies manuals for Communications System are available online for free. You can easily download all the documents as PDF.

Page 201

CV/LAN Programming
Issue  3  May 1998
6-9
 For further information see‘‘asai_send( )’’ on page 4-10 in Chapter 4 and 
‘‘asai_send (3ASAI)’’ on page 9-15 in Chapter 9, ‘‘Programming Manual Pages.’’
asai_rcv() 
 Description 
asai_rcv() allows the user to receive indication primitives. Indications may take 
either the form of requests, or positive, or negative acknowledgments.
Prototype
long asai_rcv (int socketfd, asai_info_t * buf, long length)  
Arguments
The first argument is the descriptor that...

Page 202

CV/LAN Programming
6-10Issue  3  May 1998 
asai_close() 
Description
Close a socket to the CV/LAN Server.
Prototype
long asai_close(int socketfd)
Argument
File descriptor of the socket connection to the CV/LAN server.
Return Value
If the socket was closed successfully, the return value is 0 but if there is an error it 
is -1.
Example
close_routine()
{
  extern int fd; 
if (asai_close(fd) < 0)
{ 
asai_errval(“error closing communication   
path”);
}
return; 
}
.
.
.
For further information see...

Page 203

Issue  3  May 19987-1
7
Error Messages
Library Error Messages
Library error messages are listed alphabetically below with a brief explanation of 
the probable cause of each error. The header file in which these library error 
messages are found is asai_err.h. 
 C_NOENTNo such file or directory. This value is set when the file 
passed to asai_open() does not exist. This will also 
be returned by CV/LAN, when the machine name 
cannot be found.
 C_BADCHARUnknown or improper context for a characteristic....

Page 204

Error Messages
7-2Issue  3  May 1998 
 C_BADFLOWCommunications are flow controlled. This value is set in 
asai_rcv() if there was no message pending when it 
was called and the stream was opened in no-delay 
mode. Also, asai_send() will set this value when it 
cannot send a message.
 C_BADFLAGAn invalid value was given for the asai_open() flags.
 C_SYSERASAI service error. This error is set in asai_close(), 
asai_rcv(), and in asai_errval() whenever an 
error is detected in the operation of the ASAI...

Page 205

Error Messages
Issue  3  May 1998
7-3
 C_BADPMATCHThe request has a missing or invalid matching 
parameter. This error is set in asai_send() and 
asai_rcv() whenever a mandatory parameter is 
missing or when two parameters are used 
inconsistently. For example, the values in the capability 
and primitive type parameters must match; an initiating 
capability with an acknowledgment type is an error. 
When returned by asai_rcv(), this error indicates 
that a message has been lost.
 C_BADVALUEThe request has...

Page 206

Error Messages
7-4Issue  3  May 1998  

Page 207

Issue  3  May 19988-1
8
ASAI Capability Primitives
The capabilities available to the ASAI library functions manage the 
communications process. This section provides information on data structures 
common to most or all of the capabilities.
Beginning with G3V2, the server provides additional information for certain 
capabilities and messages. In order to provide this information to the application, 
new fields in certain structures have been provided, and in some cases, new 
structures have been defined....

Page 208

ASAI Capability Primitives
8-2Issue  3  May 1998 
Many messages contain two or more of the affected IEs: redirecting, calling, 
called, and connected number. To avoid confusing these IEs, it is desirable that 
the Type of Address and Numbering Plan fields be closely associated to the string 
of ASCII digits which they are intended to describe.
These redirecting, calling, called, and connected number fields are immediately 
followed with a structure (of type plan_type_t) that contains the Type of 
Address...

Page 209

ASAI Capability Primitives
Issue  3  May 1998
8-3
asai_common
The structure asai_common defined by typedef asai_common_t is part of the 
data included for each capability. As its name implies, this structure contains 
information common to all capabilities. This common information is defined as 
follows:
typedef struct{
        capability_t        capability;
        primitive_t         primitive_type;
        long                sao_id;
        long                reserved;
}asai_common_t;
Within...

Page 210

ASAI Capability Primitives
8-4Issue  3  May 1998 
C_3PSH,
C_3PSH_CONF,
C_3PSL_DISC
C_3PSL_DISC_ACk,
C_3PSL_RECONN
C_3PSL_RECONN_ACK,
C_3PSSC_REQ
C_3PSSC_CONF
                          C_3PTC_CONF
           C_3PTC_REQ
C_ABORT,
C_EN_CAN,
C_EN_CAN_CONF,
C_EN_CONF,
C_EN_END,
C_EN_REP,
C_EN_REQ,
C_HB_CONF,
C_HB_REQ,
C_RF_CONF,
C_RF_REQ,
C_RT_END,
C_RT_REQ,
C_RT_SEL,
C_SV_CONF,
C_SV_REQ,
C_VQ_CONF,
C_VQ_REQ,
C_VQ_RESP,
C_EN_SCN,
C_EN_SCN_CONF,
C_RM_REQ,
C_RM_CONF,
C_SM_REQ,
C_SM_CONF,
} capability_t;
The type...
Start reading Lucent Technologies DEFINITY Enterprise Communications Server Release 6 CallVisor PC ASAI Instructions Manual

Related Manuals for Lucent Technologies DEFINITY Enterprise Communications Server Release 6 CallVisor PC ASAI Instructions Manual

All Lucent Technologies manuals