Group PJLIB_UTIL_ERROR¶
-
group
PJLIB_UTIL_ERROR
Defines
-
PJLIB_UTIL_ERRNO_START
¶ Start of error code relative to PJ_ERRNO_START_USER. This value is 320000.
-
PJLIB_UTIL_ESTUNRESOLVE
¶ Unable to resolve STUN server
-
PJLIB_UTIL_ESTUNINMSGTYPE
¶ Unknown STUN message type.
-
PJLIB_UTIL_ESTUNINMSGLEN
¶ Invalid STUN message length
-
PJLIB_UTIL_ESTUNINATTRLEN
¶ Invalid STUN attribute length
-
PJLIB_UTIL_ESTUNINATTRTYPE
¶ Invalid STUN attribute type
-
PJLIB_UTIL_ESTUNININDEX
¶ Invalid STUN server/socket index
-
PJLIB_UTIL_ESTUNNOBINDRES
¶ No STUN binding response in the message
-
PJLIB_UTIL_ESTUNRECVERRATTR
¶ Received STUN error attribute
-
PJLIB_UTIL_ESTUNNOMAP
¶ No STUN mapped address attribute
-
PJLIB_UTIL_ESTUNNOTRESPOND
¶ Received no response from STUN server
-
PJLIB_UTIL_ESTUNSYMMETRIC
¶ Symetric NAT detected by STUN
-
PJLIB_UTIL_ESTUNNOTMAGIC
¶ Invalid STUN magic value
-
PJLIB_UTIL_ESTUNFINGERPRINT
¶ Invalid STUN fingerprint value
-
PJLIB_UTIL_EINXML
¶ General invalid XML message.
-
PJLIB_UTIL_EDNSQRYTOOSMALL
¶ 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.
-
PJLIB_UTIL_EDNSINSIZE
¶ Invalid DNS packet length. This error occurs when the received DNS response packet does not match all the fields length.
-
PJLIB_UTIL_EDNSINCLASS
¶ Invalid DNS class. This error occurs when the received DNS response contains network class other than IN (Internet).
-
PJLIB_UTIL_EDNSINNAMEPTR
¶ 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.
-
PJLIB_UTIL_EDNSINNSADDR
¶ Invalid DNS nameserver address. If hostname was specified for nameserver address, this error means that the function was unable to resolve the nameserver hostname.
-
PJLIB_UTIL_EDNSNONS
¶ No nameserver is in DNS resolver. No nameserver is configured in the resolver.
-
PJLIB_UTIL_EDNSNOWORKINGNS
¶ 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.
-
PJLIB_UTIL_EDNSNOANSWERREC
¶ No answer record in the DNS response.
-
PJLIB_UTIL_EDNSINANSWER
¶ 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.
-
PJLIB_UTIL_DNS_RCODE_START
¶ Start of error code mapped from DNS RCODE
-
PJ_STATUS_FROM_DNS_RCODE
(rcode)¶ Map DNS RCODE status into pj_status_t.
-
PJLIB_UTIL_EDNS_FORMERR
¶ Format error - The name server was unable to interpret the query. This corresponds to DNS RCODE 1.
-
PJLIB_UTIL_EDNS_SERVFAIL
¶ 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.
-
PJLIB_UTIL_EDNS_NXDOMAIN
¶ 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.
-
PJLIB_UTIL_EDNS_NOTIMPL
¶ Not Implemented - The name server does not support the requested kind of query. This corresponds to DNS RCODE 4.
-
PJLIB_UTIL_EDNS_REFUSED
¶ Refused - The name server refuses to perform the specified operation for policy reasons. This corresponds to DNS RCODE 5.
-
PJLIB_UTIL_EDNS_YXDOMAIN
¶ The name exists. This corresponds to DNS RCODE 6.
-
PJLIB_UTIL_EDNS_YXRRSET
¶ The RRset (name, type) exists. This corresponds to DNS RCODE 7.
-
PJLIB_UTIL_EDNS_NXRRSET
¶ The RRset (name, type) does not exist. This corresponds to DNS RCODE 8.
-
PJLIB_UTIL_EDNS_NOTAUTH
¶ The requestor is not authorized to perform this operation. This corresponds to DNS RCODE 9.
-
PJLIB_UTIL_EDNS_NOTZONE
¶ The zone specified is not a zone. This corresponds to DNS RCODE 10.
-
PJLIB_UTIL_ESTUNTOOMANYATTR
¶ Too many STUN attributes.
-
PJLIB_UTIL_ESTUNUNKNOWNATTR
¶ Unknown STUN attribute. This error happens when the decoder encounters mandatory attribute type which it doesn’t understand.
-
PJLIB_UTIL_ESTUNINADDRLEN
¶ Invalid STUN socket address length.
-
PJLIB_UTIL_ESTUNIPV6NOTSUPP
¶ STUN IPv6 attribute not supported
-
PJLIB_UTIL_ESTUNNOTRESPONSE
¶ Expecting STUN response message.
-
PJLIB_UTIL_ESTUNINVALIDID
¶ STUN transaction ID mismatch.
-
PJLIB_UTIL_ESTUNNOHANDLER
¶ Unable to find handler for the request.
-
PJLIB_UTIL_ESTUNMSGINTPOS
¶ 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.
-
PJLIB_UTIL_ESTUNFINGERPOS
¶ Found attribute after FINGERPRINT. This is not valid since FINGERPRINT MUST be the last attribute in the message.
-
PJLIB_UTIL_ESTUNNOUSERNAME
¶ 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.
-
PJLIB_UTIL_ESTUNUSERNAME
¶ Unknown STUN username/credential.
-
PJLIB_UTIL_ESTUNMSGINT
¶ Missing/invalidSTUN MESSAGE-INTEGRITY attribute.
-
PJLIB_UTIL_ESTUNDUPATTR
¶ Found duplicate STUN attribute.
-
PJLIB_UTIL_ESTUNNOREALM
¶ Missing STUN REALM attribute.
-
PJLIB_UTIL_ESTUNNONCE
¶ Missing/stale STUN NONCE attribute value.
-
PJLIB_UTIL_ESTUNTSXFAILED
¶ STUN transaction terminates with failure.
-
PJLIB_UTIL_EHTTPINURL
¶ Invalid URL format
-
PJLIB_UTIL_EHTTPINPORT
¶ Invalid port number
-
PJLIB_UTIL_EHTTPINCHDR
¶ Incomplete headers received
-
PJLIB_UTIL_EHTTPINSBUF
¶ Insufficient buffer
-
PJLIB_UTIL_EHTTPLOST
¶ Connection lost
-