Home --> Documentations --> PJLIB-UTIL Reference
CLI command entered by user match with more than one command/argument specification.
CLI command with the specified id already exist.
CLI command with the specified name already exist.
Invalid XML format for CLI command specification.
End the current session. This is a special error code returned by pj_cli_sess_exec() to indicate that "exit" or equivalent command has been called to end the current session.
Invalid CLI argument. Typically this is caused by extra characters specified in the command line which does not match any arguments.
A required CLI argument is not specified.
(rcode==0 ? PJ_SUCCESS : \
Map DNS RCODE status into pj_status_t.
Start of error code mapped from DNS RCODE
Format error - The name server was unable to interpret the query. This corresponds to DNS RCODE 1.
The requestor is not authorized to perform this operation. This corresponds to DNS RCODE 9.
Not Implemented - The name server does not support the requested kind of query. This corresponds to DNS RCODE 4.
The zone specified is not a zone. This corresponds to DNS RCODE 10.
Name Error - Meaningful only for responses from an authoritative name server, this code signifies that the domain name referenced in the query does not exist. This corresponds to DNS RCODE 3.
The RRset (name, type) does not exist. This corresponds to DNS RCODE 8.
Refused - The name server refuses to perform the specified operation for policy reasons. This corresponds to DNS RCODE 5.
Server failure - The name server was unable to process this query due to a problem with the name server. This corresponds to DNS RCODE 2.
The name exists. This corresponds to DNS RCODE 6.
The RRset (name, type) exists. This corresponds to DNS RCODE 7.
Invalid DNS answer. This error is raised for example when the DNS answer does not have a query section, or the type of RR in the answer doesn't match the query.
Invalid DNS class. This error occurs when the received DNS response contains network class other than IN (Internet).
Invalid DNS name pointer. This error occurs when parsing the compressed names inside DNS response packet, when the name pointer points to an invalid address or the parsing has triggerred too much recursion.
Invalid DNS nameserver address. If hostname was specified for nameserver address, this error means that the function was unable to resolve the nameserver hostname.
Invalid DNS packet length. This error occurs when the received DNS response packet does not match all the fields length.
No answer record in the DNS response.
No nameserver is in DNS resolver. No nameserver is configured in the resolver.
No working DNS nameserver. All nameservers have been queried, but none was able to serve any DNS requests. These "bad" nameservers will be re-tested again for "goodness" after some period.
DNS query packet buffer is too small. This error occurs when the user supplied buffer for creating DNS query (pj_dns_make_query() function) is too small.
Incomplete headers received
General invalid JSON message.
General invalid XML message.
Start of error code relative to PJ_ERRNO_START_USER. This value is 320000.
Found duplicate STUN attribute.
Found attribute after FINGERPRINT. This is not valid since FINGERPRINT MUST be the last attribute in the message.
Invalid STUN fingerprint value
Invalid STUN socket address length.
Invalid STUN attribute length
Invalid STUN attribute type
Invalid STUN server/socket index
Invalid STUN message length
Unknown STUN message type.
STUN transaction ID mismatch.
STUN IPv6 attribute not supported
Missing/invalidSTUN MESSAGE-INTEGRITY attribute.
Found non-FINGERPRINT attribute after MESSAGE-INTEGRITY. This is not valid since MESSAGE-INTEGRITY MUST be the last attribute or the attribute right before FINGERPRINT before the message.
No STUN binding response in the message
Unable to find handler for the request.
No STUN mapped address attribute
Missing/stale STUN NONCE attribute value.
Missing STUN REALM attribute.
Received no response from STUN server
Expecting STUN response message.
Missing STUN USERNAME attribute. When credential is included in the STUN message (MESSAGE-INTEGRITY is present), the USERNAME attribute must be present in the message.
Received STUN error attribute
Unable to resolve STUN server
Symetric NAT detected by STUN
Too many STUN attributes.
STUN transaction terminates with failure.
Unknown STUN attribute. This error happens when the decoder encounters mandatory attribute type which it doesn't understand.
Unknown STUN username/credential.
PJLIB-UTIL Open Source, small footprint, and portable asynchronous/caching DNS resolver, text scanner, STUN client, and XML library
Copyright (C) 2006-2009 Teluu Inc.