SR_RET_ERR |
error occured, call error handler for details |
SR_RET_REMAIN_WIN_TOO_SMALL |
can't send, because not enough octets left in RFC3081 window --> wait for SEQ |
SR_RET_INVALID_HANDLE |
caller provided an invalid handle, e.g
NULL pointer or pointer to wrong object. This is only checked on the API layer. Internally, all functions check this via assert(), so protection is only available during debugging. This is a performance decision. |
SR_RET_INVALID_DESTRUCTOR |
used, when the caller must provide a pointer to a destructor function but does not |
SR_RET_NOT_FOUND |
a requested element was not found
May not be an error depending on what operation was to be carried out... |
SR_RET_OUT_OF_MEMORY |
memory allocation failed |
SR_RET_XML_INVALID_PARAMTAG |
malformed tag parameter, most probably quotes are missing before value or intervening space |
SR_RET_XML_INVALID_TERMINATOR |
missing terminator sequence, e.g
a "param='no_terminator" - notice the missing closing quote |
SR_RET_XML_MALFORMED |
the XML is malformed (no specific reason given) |
SR_RET_MISSING_CLOSE_BRACE |
closing brace in <tag /> missing |
SR_RET_XML_MISSING_CLOSETAG |
close tag is missing or syntax invalid ... |
SR_RET_XML_MISSING_OPENTAG |
open tag is missing, e.g <tag />othertag> |
SR_RET_XML_TAG_MISMATCH |
start and close tag name do not match (...) |
SR_RET_XML_INVALID_CDATA_HDR |
invalid start of CDATA, e.g
<![CDTA... |
SR_RET_XML_INVALID_CDATA_TRAIL |
invalid CDATA trailer, , e.g
"<![CDATA[test]>" (one ] missing) |
SR_RET_PEER_NONOK_RESPONSE |
was waiting for a BEEP peer to respond "ok", but received other response |
SR_RET_PEER_INVALID_PROFILE |
BEEP Peer did either not support the profile or did not return the correct on in response to a start message. |
SR_RET_PEER_NO_URI |
BEEP peer did not inclulde a mandatory URI element in its xml response. |
SR_RET_PEER_NO_PROFILE |
BEEP peer did not include a mandatory PROFILE element in its XML reponse. |
SR_RET_PEER_NO_GREETING |
BEEP peer did not send a (correctly formatted) greeting message. |
SR_RET_PEER_DOESNT_SUPPORT_PROFILE |
the reqeusted profile is not part of the peers profile set (from greeting message) |
SR_RET_INVALID_FRAME_STATE |
a frame object has an invalid frame state (pFram->iState) |
SR_RET_PROFILE_ALREADY_SET |
a profile should be assgined to a channel which already has one |
SR_RET_INVALID_CHAN_STATE |
a channel object has an invalid or unexpected (at this point) channel state |
SR_RET_INVALID_GREETING |
greeting message is (somehow) invalid, e.g
does not start with RPY) |
SR_RET_INVALID_CHAN0_MESG |
channel 0 received an invalid or out-of-sequence message |
SR_RET_START_MISSING_NUMBER |
a start message is missing the "number=" parameter |
SR_RET_START_INVALID_NUMBER |
a start message's "number=" parameter specifies an invalid number |
SR_RET_START_EXISTING_NUMBER |
a start message's "number=" parameter specifies a channel number which already exisits! |
SR_RET_NO_VALUE |
a linked list was asked to provide an uValue, but there was none
Not necessarily an error, depends on caller's needs. |
SR_RET_START_EVEN_NUMBER |
an initiator sent a even-numbered start number, which is invalid as of rfc 3080 2.3.1.2 |
SR_RET_NO_PROFILE_RQSTD |
no profile at all was requested in a start message (may be caused by invalid format) |
SR_RET_WARNING_START_NO_PROFMATCH |
WARNING only (no error) - during a start, no matching profile was found and the beep peer has been sent such an ERR frame. |
SR_RET_ERR_EVENT_HANDLER_MISSING |
a required (profile) event handler is missing |
SR_RET_ACKNO_ZERO |
caller-provided ackno is zero
This can not be by design. |
SR_RET_CHAN_DOESNT_EXIST |
a chanel specified does not exist |
SR_RET_ALREADY_LISTENING |
caller tried to start an listener on the API object, but it is already one running |
SR_RET_INVALID_OPTVAL |
invalid option value was provided to srAPISetOption() (param 2) |
SR_RET_INVALID_LIB_OPTION |
invalid option was provided to srAPISetOption() (param 1) |
SR_RET_NULL_POINTER_PROVIDED |
the caller has provided a NULL-Pointer where none were expected/allowed |
SR_RET_PROPERTY_NOT_AVAILABLE |
a property asked for is not available, e.g
the TIMESTAMP in a not-wellformed message |
SR_RET_UNSUPPORTED_FORMAT |
a non-supported format was requested by the caller |
SR_RET_UNALLOCATABLE_BUFFER |
the operation can not be completed because a buffer that is under user control would need to be deallocated |
SR_RET_PRIO_OUT_OF_RANGE |
a priority value is outside the allowed range |
SR_RET_FACIL_OUT_OF_RANGE |
a facility value is outside the allowed range |
SR_RET_INVALID_TAG |
a syslog TAG value (string) provided was invalid, e.g
over 32 chars or included invalid chars |
SR_RET_NULL_MSG_PROVIDED |
caller provided a NULL pointer where a pointer to a MSG was expected |
SR_RET_ERR_RECEIVE |
an error occured during message receive
no more detail is available |
SR_RET_UNEXPECTED_HDRCMD |
an invalid HDR Command was received (e.g
an "MSG" in response to another "MSG") |
SR_RET_PEER_INDICATED_ERROR |
the PEER send an error response |
SR_RET_PROVIDED_BUFFER_TOO_SMALL |
the caller provided a buffer, but the called function sees the size of this buffer is too small - operation not carried out |
SR_RET_INVALID_PARAM |
an invalid parameter was provided to a method |
SR_RET_SOCKET_ERR |
generic error generated by socket subsystem |
SR_RET_CANT_BIND_SOCKET |
socket bind() operation failed |
SR_RET_INVALID_SOCKET |
invalid socket |
SR_RET_CONNECTION_CLOSED |
the remote peer closed the connection |
SR_RET_INVALID_OS_SOCKETS_VERSION |
the operating system socket subsystem version is inappropriate (this error will most probably occur under Win32, only) |
SR_RET_CAN_NOT_INIT_SOCKET |
socket() failed for whatever reason.. |
SR_RET_UXDOMSOCK_CHMOD_ERR |
chmod() failed on Unix Domain Socket |
SR_RET_INVALID_HDRCMD |
invalid HDRCMD (e.g
"MSG", "RPY",...) |
SR_RET_INVALID_WAITING_SP_CHAN |
invalid SP before channo |
SR_RET_INVALID_CHANNO |
invalid channo |
SR_RET_INVALID_WAITING_SP_MSGNO |
now the space before the next header |
SR_RET_INVALID_IN_MSGNO |
and the next (numeric) header |
SR_RET_INVALID_WAITING_SP_MORE |
now the space before the next header |
SR_RET_INVALID_IN_MORE |
and the next (char) header |
SR_RET_INVALID_WAITING_SP_SEQNO |
now the space before the next header |
SR_RET_INVALID_IN_SEQNO |
and the next (numeric) header |
SR_RET_INVALID_WAITING_SP_SIZE |
now the space before the next header |
SR_RET_INVALID_IN_SIZE |
and the next (numeric) header |
SR_RET_INVALID_WAITING_SP_ANSNO |
now the space before the next header |
SR_RET_INVALID_IN_ANSNO |
and the next (numeric) header |
SR_RET_INVALID_WAITING_HDRCR |
awaiting the HDR's CR |
SR_RET_INVALID_WAITING_HDRLF |
awaiting the HDR's LF |
SR_RET_INVALID_IN_PAYLOAD |
reading payload area |
SR_RET_INVALID_WAITING_END1 |
waiting for the 1st HDR character |
SR_RET_INVALID_WAITING_END2 |
waiting for the 2nd HDR character |
SR_RET_INVALID_WAITING_END3 |
waiting for the 3rd HDR character |
SR_RET_INVALID_WAITING_END4 |
waiting for the 4th HDR character |
SR_RET_INVALID_WAITING_END5 |
waiting for the 5th HDR character |
SR_RET_INVALID_WAITING_SP_ACKNO |
now the space before the next header |
SR_RET_INVALID_WAITING_SP_WINDOW |
now the space before the next header |
SR_RET_INAPROPRIATE_HDRCMD |
the beep header was syntactically correct, but could not be used semantically |
SR_RET_OVERSIZED_FRAME |
the frame's "size" field specifies a size that does not fit into the current windows
Eventually malicous. |
SR_RET_OK |
operation successful |