PJNATH specific error code constants. More...
Macro Definition Documentation
Map STUN error code (300-699) into pj_status_t error space.
This error indicates that ICE connectivity check has failed, because there is at least one ICE component that does not have a valid check. Normally this happens because the network topology had caused the connectivity check to fail (e.g. no route between the two agents), however other reasons may include software incompatibility between the two agents, or incomplete candidates gathered by the agent(s).
Invalid ICE candidate ID
Invalid SDP "candidate" attribute
Invalid ICE component ID
ICE check is in progress
Source address mismatch. This error occurs if the source address of the response for ICE connectivity check is different than the destination address of the request.
Default destination does not match any ICE candidates
Missing ICE SDP attribute
No host candidate associated with srflx. This error occurs when a server reflexive candidate is added without the matching host candidate.
Controlled agent timed-out in waiting for the controlling agent to send nominated check after all connectivity checks have completed.
Invalid STUN message
Invalid STUN message length.
Invalid or unexpected STUN message type
Invalid address family value in STUN message.
ICE session not available
Start of error code relative to PJ_ERRNO_START_USER. This value is 370000.
STUN object has been destoyed.
Found duplicate STUN attribute.
Invalid STUN attribute after FINGERPRINT.
STUN FINGERPRINT verification failed
Invalid STUN attribute length.
Invalid STUN server or server not configured.
STUN IPv6 attribute not supported
Invalid STUN attribute after MESSAGE-INTEGRITY.
STUN (XOR-)MAPPED-ADDRESS attribute not found
STUN transaction has timed out
Too many STUN attributes.
Invalid or unsupported TURN transport.