Object Hierarchy

GEnum
╰── TpError

Includes

#include <telepathy-glib/telepathy-glib.h>

Description

This header provides the Telepathy D-Bus errors, in the form of a
GLib error domain. For D-Bus methods which fail with one of these errors,
dbus-glib will generate a reply message with the appropriate error.

It also provides utility functions used by functions which return an error.

Functions

TP_ERROR

#define TP_ERROR (tp_error_quark ())

The error domain for the D-Bus errors described in the Telepathy
specification. Error codes in this domain come from the TpError
enumeration.

This macro expands to a call to a function returning the Telepathy error
domain. Since 0.99.10, this function automatically registers the
domain with GIO (using g_dbus_error_register_error()) when
called.

Parameters

Returns

Types and Values

TP_ERROR_PREFIX

The common prefix of Telepathy errors, as a string constant, without
the trailing '.' character.

Since 0.7.1

enum TpError

Enumerated type representing the Telepathy D-Bus errors.

Members

TP_ERROR_NETWORK_ERROR

im.telepathy.v1.Error.NetworkError:
Raised when there is an error reading from or writing to the network.

TP_ERROR_NOT_IMPLEMENTED

im.telepathy.v1.Error.NotImplemented:
Raised when the requested method, channel, etc is not available on this
connection.

TP_ERROR_INVALID_ARGUMENT

im.telepathy.v1.Error.InvalidArgument:
Raised when one of the provided arguments is invalid.

TP_ERROR_NOT_AVAILABLE

im.telepathy.v1.Error.NotAvailable:
Raised when the requested functionality is temporarily unavailable.

TP_ERROR_PERMISSION_DENIED

im.telepathy.v1.Error.PermissionDenied:
The user is not permitted to perform the requested operation.

TP_ERROR_DISCONNECTED

im.telepathy.v1.Error.Disconnected:
The connection is not currently connected and cannot be used.
This error may also be raised when operations are performed on a
Connection for which StatusChanged has signalled status Disconnected
for reason None.

TP_ERROR_INVALID_HANDLE

im.telepathy.v1.Error.InvalidHandle:
An identifier being converted to a handle was syntactically invalid,
or an invalid handle was used.

TP_ERROR_CHANNEL_BANNED

im.telepathy.v1.Error.Channel.Banned:
You are banned from the channel.

TP_ERROR_CHANNEL_FULL

im.telepathy.v1.Error.Channel.Full:
The channel is full.

TP_ERROR_CHANNEL_INVITE_ONLY

im.telepathy.v1.Error.Channel.InviteOnly:
The requested channel is invite-only.

TP_ERROR_NOT_YOURS

im.telepathy.v1.Error.NotYours:
The requested channel or other resource already exists, and another
client is responsible for it

TP_ERROR_CANCELLED

im.telepathy.v1.Error.Cancelled:
Raised by an ongoing request if it is cancelled by user request before
it has completed, or when operations are performed on an object which
the user has asked to close (for instance, a Connection where the user
has called Disconnect, or a Channel where the user has called Close).

TP_ERROR_AUTHENTICATION_FAILED

im.telepathy.v1.Error.AuthenticationFailed:
Raised when authentication with a service was unsuccessful.

TP_ERROR_ENCRYPTION_NOT_AVAILABLE

im.telepathy.v1.Error.EncryptionNotAvailable:
Raised if a user request insisted that encryption should be used,
but encryption was not actually available.

TP_ERROR_ENCRYPTION_ERROR

im.telepathy.v1.Error.EncryptionError:
Raised if encryption appears to be available, but could not actually be
used (for instance if SSL/TLS negotiation fails).

TP_ERROR_CERT_NOT_PROVIDED

im.telepathy.v1.Error.Cert.NotProvided:
Raised if the server did not provide a SSL/TLS certificate.

TP_ERROR_CERT_UNTRUSTED

im.telepathy.v1.Error.Cert.Untrusted:
Raised if the server provided a SSL/TLS certificate signed by an
untrusted certifying authority.

TP_ERROR_CERT_EXPIRED

im.telepathy.v1.Error.Cert.Expired:
Raised if the server provided an expired SSL/TLS certificate.

TP_ERROR_CERT_NOT_ACTIVATED

im.telepathy.v1.Error.Cert.NotActivated:
Raised if the server provided an SSL/TLS certificate that will become
valid at some point in the future.

TP_ERROR_CERT_FINGERPRINT_MISMATCH

im.telepathy.v1.Error.Cert.FingerprintMismatch:
Raised if the server provided an SSL/TLS certificate that did not have
the expected fingerprint.

TP_ERROR_CERT_HOSTNAME_MISMATCH

im.telepathy.v1.Error.Cert.HostnameMismatch:
Raised if the server provided an SSL/TLS certificate that did not
match its hostname.

TP_ERROR_CERT_SELF_SIGNED

im.telepathy.v1.Error.Cert.SelfSigned:
Raised if the server provided an SSL/TLS certificate that is
self-signed and untrusted.

TP_ERROR_CERT_INVALID

im.telepathy.v1.Error.Cert.Invalid:
Raised if the server provided an SSL/TLS certificate that is
unacceptable in some way that does not have a more specific error.

TP_ERROR_NOT_CAPABLE

im.telepathy.v1.Error.NotCapable:
Raised when requested functionality is unavailable due to a contact
not having the required capabilities.

TP_ERROR_OFFLINE

im.telepathy.v1.Error.Offline:
Raised when requested functionality is unavailable because a contact is
offline.

TP_ERROR_CHANNEL_KICKED

im.telepathy.v1.Error.Channel.Kicked:
Used to represent a user being ejected from a channel by another user,
for instance being kicked from a chatroom.

TP_ERROR_BUSY

im.telepathy.v1.Error.Busy:
Used to represent a user being removed from a channel because of a
"busy" indication.

TP_ERROR_NO_ANSWER

im.telepathy.v1.Error.NoAnswer:
Used to represent a user being removed from a channel because they did
not respond, e.g. to a StreamedMedia call.

TP_ERROR_DOES_NOT_EXIST

im.telepathy.v1.Error.DoesNotExist:
Raised when the requested user does not, in fact, exist.

TP_ERROR_TERMINATED

im.telepathy.v1.Error.Terminated:
Raised when a channel is terminated for an unspecified reason. In
particular, this error SHOULD be used whenever normal termination of a
1-1 StreamedMedia call by the remote user is represented as a D-Bus
error name.

TP_ERROR_CONNECTION_REFUSED

im.telepathy.v1.Error.ConnectionRefused:
Raised when a connection is refused.

TP_ERROR_CONNECTION_FAILED

im.telepathy.v1.Error.ConnectionFailed:
Raised when a connection can't be established.

TP_ERROR_CONNECTION_LOST

im.telepathy.v1.Error.ConnectionLost:
Raised when a connection is broken.

TP_ERROR_ALREADY_CONNECTED

im.telepathy.v1.Error.AlreadyConnected:
Raised on attempts to connect again to an account that is already
connected, if the protocol or server does not allow this.
Since 0.7.34

TP_ERROR_CONNECTION_REPLACED

im.telepathy.v1.Error.ConnectionReplaced:
Used as disconnection reason for an existing connection if it is
disconnected because a second connection to the same account is made.
Since 0.7.34

TP_ERROR_REGISTRATION_EXISTS

im.telepathy.v1.Error.RegistrationExists:
Raised on attempts to register an account on a server when the account
already exists.
Since 0.7.34

TP_ERROR_SERVICE_BUSY

im.telepathy.v1.Error.ServiceBusy:
Raised when a server or other infrastructure rejects a request because
it is too busy.
Since 0.7.34

TP_ERROR_RESOURCE_UNAVAILABLE

im.telepathy.v1.Error.ResourceUnavailable:
Raised when a local process rejects a request because it does not have
enough of a resource, such as memory.
Since 0.7.34

TP_ERROR_WOULD_BREAK_ANONYMITY

im.telepathy.v1.Error.WouldBreakAnonymity:
Raised when a request cannot be satisfied without violating an
earlier request for anonymity, and the earlier request specified
that raising an error is preferable to disclosing the user's
identity
Since 0.11.7

TP_ERROR_CERT_REVOKED

im.telepathy.v1.Error.Cert.Revoked:
Raised if the server provided an SSL/TLS certificate that has been
revoked.
Since 0.11.12

TP_ERROR_CERT_INSECURE

im.telepathy.v1.Error.Cert.Insecure:
Raised if the server provided an SSL/TLS certificate that uses an
insecure cipher algorithm or is cryptographically weak.
Since 0.11.12

TP_ERROR_CERT_LIMIT_EXCEEDED

im.telepathy.v1.Error.Cert.LimitExceeded:
Raised if the length in bytes of the server certificate, or the depth
of the server certificate chain, exceed the limits imposed by the
crypto library.
Since 0.11.12

TP_ERROR_NOT_YET

im.telepathy.v1.Error.NotYet:
Raised when the requested functionality is not yet available, but is
likely to become available after some time has passed.
Since 0.11.15

TP_ERROR_REJECTED

im.telepathy.v1.Error.Rejected:
Raised when an incoming or outgoing call is rejected by the receiving
contact.
Since 0.13.2

TP_ERROR_PICKED_UP_ELSEWHERE

im.telepathy.v1.Error.PickedUpElsewhere:
Raised when a call was terminated as a result of the local user
picking up the call on a different resource.
Since 0.13.3

TP_ERROR_CONFUSED

im.telepathy.v1.Error.Confused:
Raised if a server rejects protocol messages from a connection manager
claiming that they do not make sense, two local processes fail to
understand each other, or an apparently impossible situation is
reached. This has a similar meaning to TP_DBUS_ERROR_INCONSISTENT but
can be passed between processes via D-Bus.
Since 0.13.7

TP_ERROR_SERVICE_CONFUSED

im.telepathy.v1.Error.ServiceConfused:
Raised when a server or other piece of infrastructure indicates an
internal error, or when a message that makes no sense is received from
a server or other piece of infrastructure.
Since 0.13.7

TP_ERROR_EMERGENCY_CALLS_NOT_SUPPORTED

im.telepathy.v1.Error.EmergencyCallsNotSupported:
Raised when a client attempts to dial a number that is recognized as an
emergency number (e.g. '911' in the USA), but the Connection
Manager or provider does not support dialling emergency numbers.

TP_ERROR_SOFTWARE_UPGRADE_REQUIRED

im.telepathy.v1.Error.SoftwareUpgradeRequired:
Raised when a Connection cannot be established because either the
Connection Manager or its support library (e.g. wocky, papyon, sofiasip)
requires upgrading to support a newer protocol version.

TP_ERROR_INSUFFICIENT_BALANCE

im.telepathy.v1.Error.InsufficientBalance:

Raised if the user has insufficient balance to place a call. The key
'balance-required' MAY be included in CallStateDetails on a Call channel
(with the same units and scale as AccountBalance) to indicate how much
credit is required to make this call.

TP_ERROR_MEDIA_CODECS_INCOMPATIBLE

im.telepathy.v1.Error.Media.CodecsIncompatible:

Raised when the local streaming implementation has no codecs in common
with the remote side.
Since 0.15.6

TP_ERROR_MEDIA_UNSUPPORTED_TYPE

im.telepathy.v1.Error.Media.UnsupportedType:

The media stream type requested is not supported by either the local or
remote side.
Since 0.15.6

TP_ERROR_MEDIA_STREAMING_ERROR

im.telepathy.v1.Error.Media.StreamingError:

Raised when the call's streaming implementation has some kind of internal
error.
Since 0.15.6

TP_ERROR_CAPTCHA_NOT_SUPPORTED

im.telepathy.v1.Error.Media.CaptchaNotSupported:

Raised if no UI is available to present captchas, or if one is
available but it is unable to answer any of the captchas given.

TP_ERROR_STR_DISCONNECTED

The connection is not currently connected and cannot be used. This error may also be raised when operations are performed on a Connection for which <tp:dbus-ref namespace="im.telepathy.v1.Connection">StatusChanged</tp:dbus-ref> has signalled status Disconnected for reason None. <tp:rationale> The second usage corresponds to None in the <tp:type>Connection_Status_Reason</tp:type> enum; if a better reason is available, the corresponding error should be used instead. </tp:rationale>

TP_ERROR_STR_CHANNEL_INVITE_ONLY

TP_ERROR_STR_NOT_YOURS

#define TP_ERROR_STR_NOT_YOURS "im.telepathy.v1.Error.NotYours"

The D-Bus error name im.telepathy.v1.Error.NotYours

<tp:docstring xmlns="http://www.w3.org/1999/xhtml"> <p>The requested channel or other resource already exists, and another user interface in this session is responsible for it.</p> <p>User interfaces SHOULD handle this error unobtrusively, since it indicates that some other user interface is already processing the channel.</p>

TP_ERROR_STR_CANCELLED

#define TP_ERROR_STR_CANCELLED "im.telepathy.v1.Error.Cancelled"

The D-Bus error name im.telepathy.v1.Error.Cancelled

Raised by an ongoing request if it is cancelled by user request before it has completed, or when operations are performed on an object which the user has asked to close (for instance, a Connection where the user has called Disconnect, or a Channel where the user has called Close). <tp:rationale> The second form can be used to correspond to the Requested member in the <tp:type>Connection_Status_Reason</tp:type> enum, or to to represent the situation where disconnecting a Connection, closing a Channel, etc. has been requested by the user but this request has not yet been acted on, for instance because the service will only act on the request when it has finished processing an event queue. </tp:rationale>

TP_ERROR_STR_ENCRYPTION_NOT_AVAILABLE

Raised if a user request insisted that encryption should be used, but encryption was not actually available. <tp:rationale> This corresponds to part of Encryption_Error in the <tp:type>Connection_Status_Reason</tp:type> enum. It's been separated into a distinct error here because the two concepts that were part of EncryptionError seem to be things that could reasonably appear differently in the UI. </tp:rationale>

TP_ERROR_STR_ENCRYPTION_ERROR

Raised if encryption appears to be available, but could not actually be used (for instance if SSL/TLS negotiation fails). <tp:rationale> This corresponds to part of Encryption_Error in the <tp:type>Connection_Status_Reason</tp:type> enum. </tp:rationale>

TP_ERROR_STR_CERT_NOT_PROVIDED

Raised if the server did not provide a SSL/TLS certificate. This error MUST NOT be used to represent the absence of a client certificate provided by the Telepathy connection manager. <tp:rationale> This corresponds to Cert_Not_Provided in the <tp:type>Connection_Status_Reason</tp:type> enum. That error explicitly applied only to server SSL certificates, so this one is similarly limited; having the CM present a client certificate is a possible future feature, but it should have its own error handling. </tp:rationale>

TP_ERROR_STR_CERT_UNTRUSTED

Raised if the server provided a SSL/TLS certificate signed by an untrusted certifying authority. This error SHOULD NOT be used to represent a self-signed certificate: see the Self Signed error for that. <tp:rationale> This corresponds to Cert_Untrusted in the <tp:type>Connection_Status_Reason</tp:type> enum and to Untrusted in the <tp:type>TLS_Certificate_Reject_Reason</tp:type> enum, with a clarification to avoid ambiguity. </tp:rationale>

TP_ERROR_STR_CERT_EXPIRED

Raised if the server provided an expired SSL/TLS certificate. <tp:rationale> This corresponds to Cert_Expired in the <tp:type>Connection_Status_Reason</tp:type> enum and to Expired in the <tp:type>TLS_Certificate_Reject_Reason</tp:type> enum. </tp:rationale>

TP_ERROR_STR_CERT_NOT_ACTIVATED

Raised if the server provided an SSL/TLS certificate that will become valid at some point in the future. <tp:rationale> This corresponds to Cert_Not_Activated in the <tp:type>Connection_Status_Reason</tp:type> enum and to Not_Activated in the <tp:type>TLS_Certificate_Reject_Reason</tp:type> enum. </tp:rationale>

TP_ERROR_STR_CERT_FINGERPRINT_MISMATCH

Raised if the server provided an SSL/TLS certificate that did not have the expected fingerprint. <tp:rationale> This corresponds to Cert_Fingerprint_Mismatch in the <tp:type>Connection_Status_Reason</tp:type> enum and to Fingerprint_Mismatch in the <tp:type>TLS_Certificate_Reject_Reason</tp:type> enum. </tp:rationale>

TP_ERROR_STR_CERT_HOSTNAME_MISMATCH

<tp:docstring xmlns="http://www.w3.org/1999/xhtml"> <p>Raised if the server provided an SSL/TLS certificate that did not match its hostname.</p> <p>You MAY be able to get more details about the expected and certified hostnames by looking up the 'expected-hostname' and 'certificate-hostname' keys in the details map that came together with this error.</p> <tp:rationale> This corresponds to Cert_Hostname_Mismatch in the <tp:type>Connection_Status_Reason</tp:type> enum and to Hostname_Mismatch in the <tp:type>TLS_Certificate_Reject_Reason</tp:type> enum. </tp:rationale>

TP_ERROR_STR_CERT_SELF_SIGNED

Raised if the server provided an SSL/TLS certificate that is self-signed and untrusted. <tp:rationale> This corresponds to Cert_Self_Signed in the <tp:type>Connection_Status_Reason</tp:type> enum and to Self_Signed in the <tp:type>TLS_Certificate_Reject_Reason</tp:type> enum. </tp:rationale>

TP_ERROR_STR_CERT_INVALID

Raised if the server provided an SSL/TLS certificate that is unacceptable in some way that does not have a more specific error. <tp:rationale> This corresponds to Cert_Other_Error in the <tp:type>Connection_Status_Reason</tp:type> enum and to Unknown in the <tp:type>TLS_Certificate_Reject_Reason</tp:type> enum. </tp:rationale>

TP_ERROR_STR_NOT_CAPABLE

#define TP_ERROR_STR_NOT_CAPABLE "im.telepathy.v1.Error.NotCapable"

The D-Bus error name im.telepathy.v1.Error.NotCapable

Raised when requested functionality is unavailable due to contact not having required capabilities.

TP_ERROR_STR_OFFLINE

#define TP_ERROR_STR_OFFLINE "im.telepathy.v1.Error.Offline"

The D-Bus error name im.telepathy.v1.Error.Offline

Raised when requested functionality is unavailable because a contact is offline. <tp:rationale> This corresponds to Offline in the <tp:type>Channel_Group_Change_Reason</tp:type> enum. </tp:rationale>

TP_ERROR_STR_CHANNEL_KICKED

Used to represent a user being ejected from a channel by another user, for instance being kicked from a chatroom. <tp:rationale> This corresponds to Kicked in the <tp:type>Channel_Group_Change_Reason</tp:type> enum. </tp:rationale>

TP_ERROR_STR_BUSY

#define TP_ERROR_STR_BUSY "im.telepathy.v1.Error.Busy"

The D-Bus error name im.telepathy.v1.Error.Busy

Used to represent a user being removed from a channel because of a &quot;busy&quot; indication. This error SHOULD NOT be used to represent a server or other infrastructure being too busy to process a request - for that, see ServerBusy. <tp:rationale> This corresponds to Busy in the <tp:type>Channel_Group_Change_Reason</tp:type> enum. </tp:rationale>

TP_ERROR_STR_NO_ANSWER

#define TP_ERROR_STR_NO_ANSWER "im.telepathy.v1.Error.NoAnswer"

The D-Bus error name im.telepathy.v1.Error.NoAnswer

Used to represent a user being removed from a channel because they did not respond, e.g. to a call. <tp:rationale> This corresponds to No_Answer in the <tp:type>Channel_Group_Change_Reason</tp:type> enum. </tp:rationale>

TP_ERROR_STR_DOES_NOT_EXIST

Raised when the requested user does not, in fact, exist. <tp:rationale> This corresponds to Invalid_Contact in the <tp:type>Channel_Group_Change_Reason</tp:type> enum, but can also be used to represent other things not existing (like chatrooms, perhaps). </tp:rationale>

TP_ERROR_STR_TERMINATED

#define TP_ERROR_STR_TERMINATED "im.telepathy.v1.Error.Terminated"

The D-Bus error name im.telepathy.v1.Error.Terminated

Raised when a channel is terminated for an unspecified reason. <tp:rationale> This corresponds to None in the <tp:type>Channel_Group_Change_Reason</tp:type> enum. </tp:rationale>

TP_ERROR_STR_ALREADY_CONNECTED

Raised when the user attempts to connect to an account but they are already connected (perhaps from another client or computer), and the protocol or account settings do not allow this. <tp:rationale> XMPP can have this behaviour if the user chooses the same resource in both clients (it is server-dependent whether the result is AlreadyConnected on the new connection, ConnectionReplaced on the old connection, or two successful connections). </tp:rationale>

TP_ERROR_STR_CONNECTION_REPLACED

Raised by an existing connection to an account if it is replaced by a new connection (perhaps from another client or computer). <tp:rationale> In MSNP, when connecting twice with the same Passport, the new connection &quot;wins&quot; and the old one is automatically disconnected. XMPP can also have this behaviour if the user chooses the same resource in two clients (it is server-dependent whether the result is AlreadyConnected on the new connection, ConnectionReplaced on the old connection, or two successful connections). </tp:rationale>

TP_ERROR_STR_REGISTRATION_EXISTS

Raised during in-band registration if the server indicates that the requested account already exists.

TP_ERROR_STR_SERVICE_BUSY

#define TP_ERROR_STR_SERVICE_BUSY "im.telepathy.v1.Error.ServiceBusy"

The D-Bus error name im.telepathy.v1.Error.ServiceBusy

<tp:docstring xmlns="http://www.w3.org/1999/xhtml"> Raised if a server or some other piece of infrastructure cannot process the request, e.g. due to resource limitations. Clients MAY try again later. <tp:rationale> This is not the same error as Busy, which indicates that a <em>user</em> is busy. </tp:rationale>

TP_ERROR_STR_RESOURCE_UNAVAILABLE

Raised if a request cannot be satisfied because a process local to the user has insufficient resources. Clients MAY try again later. <tp:rationale> For instance, the <tp:dbus-ref namespace="im.telepathy.v1">ChannelDispatcher</tp:dbus-ref> might raise this error for some or all channel requests if it has detected that there is not enough free memory. </tp:rationale>

TP_ERROR_STR_WOULD_BREAK_ANONYMITY

Raised if a request cannot be satisfied without violating an earlier request for anonymity, and the earlier request specified that raising an error is preferable to disclosing the user's identity (for instance via <tp:dbus-ref namespace="im.telepathy.v1">Connection.Interface.Anonymity1.AnonymityMandatory</tp:dbus-ref> or <tp:dbus-ref namespace="im.telepathy.v1">Channel.Interface.Anonymity1.AnonymityMandatory</tp:dbus-ref>).

TP_ERROR_STR_CERT_REVOKED

Raised if the server provided an SSL/TLS certificate that has been revoked. <tp:rationale> This corresponds to Cert_Revoked in the <tp:type>Connection_Status_Reason</tp:type> enum and to Revoked in the <tp:type>TLS_Certificate_Reject_Reason</tp:type> enum. </tp:rationale>

TP_ERROR_STR_CERT_INSECURE

Raised if the server provided an SSL/TLS certificate that uses an insecure cipher algorithm or is cryptographically weak. <tp:rationale> This corresponds to Cert_Insecure in the <tp:type>Connection_Status_Reason</tp:type> enum and to Insecure in the <tp:type>TLS_Certificate_Reject_Reason</tp:type> enum. </tp:rationale>

TP_ERROR_STR_CERT_LIMIT_EXCEEDED

Raised if the length in bytes of the server certificate, or the depth of the server certificate chain exceeds the limits imposed by the crypto library. <tp:rationale> This corresponds to Cert_Limit_Exceeded in the <tp:type>Connection_Status_Reason</tp:type> enum and to Limit_Exceeded in the <tp:type>TLS_Certificate_Reject_Reason</tp:type> enum. </tp:rationale>

TP_ERROR_STR_NOT_YET

#define TP_ERROR_STR_NOT_YET "im.telepathy.v1.Error.NotYet"

The D-Bus error name im.telepathy.v1.Error.NotYet

Raised when the requested functionality is not yet available, but is likely to become available after some time has passed.

TP_ERROR_STR_REJECTED

#define TP_ERROR_STR_REJECTED "im.telepathy.v1.Error.Rejected"

The D-Bus error name im.telepathy.v1.Error.Rejected

Raised when an incoming or outgoing <tp:dbus-ref namespace="imt1.Channel.Type">Call1</tp:dbus-ref> is rejected by the the receiver.

TP_ERROR_STR_PICKED_UP_ELSEWHERE

Raised when a call was terminated as a result of the local user picking up the call on a different resource.

TP_ERROR_STR_CONFUSED

#define TP_ERROR_STR_CONFUSED "im.telepathy.v1.Error.Confused"

The D-Bus error name im.telepathy.v1.Error.Confused

Raised if a server rejects protocol messages from a connection manager claiming that they do not make sense, two local processes fail to understand each other, or an apparently impossible situation is reached. <tp:rationale> For instance, this would be an appropriate mapping for XMPP's errors bad-format, invalid-xml, etc., which can't happen unless the local (or remote) XMPP implementation is faulty. This is also analogous to Media_Stream_Error_Invalid_CM_Behavior, <code>TP_DBUS_ERROR_INCONSISTENT</code> in telepathy-glib, and <code>TELEPATHY_QT4_ERROR_INCONSISTENT</code> in telepathy-qt4. </tp:rationale>

TP_ERROR_STR_SERVICE_CONFUSED

Raised when a server or other piece of infrastructure indicates an internal error, or when a message that makes no sense is received from a server or other piece of infrastructure. <tp:rationale> For instance, this is appropriate for XMPP's <code>internal-server-error</code>, and is also appropriate if you receive sufficiently inconsistent information from a server that you cannot continue. </tp:rationale>

TP_ERROR_STR_SOFTWARE_UPGRADE_REQUIRED

<tp:docstring xmlns="http://www.w3.org/1999/xhtml"> <p>Raised as a <tp:dbus-ref namespace="imt1.Connection">ConnectionError</tp:dbus-ref> when a Connection cannot be established because either the Connection Manager or its support library (e.g. wocky, papyon, sofiasip) requires upgrading to support a newer protocol version.</p> <p>This error corresponds to the <tp:type>Connection_Status_Reason</tp:type> of Network_Error.</p> <tp:rationale> Some protocols transmit a protocol or library version number to the server, which will disconnect them if the version isn't appropriate. This way we can report the error to the user, and if appropriate, the user's client can check for updates. </tp:rationale>

TP_ERROR_STR_EMERGENCY_CALLS_NOT_SUPPORTED

Raised if a client attempts to dial a number that is recognized as an emergency number (e.g. '911' in the USA), but the Connection Manager or provider does not support dialling emergency numbers. <tp:rationale> Many VOIP providers have the ability to dial traditional (PSTN) telephone numbers, but do not provide the ability to dial emergency numbers (for instance, Google Voice). This error provides additional information about why such a call was unsuccessful. </tp:rationale>

TP_ERROR_STR_INSUFFICIENT_BALANCE

<tp:docstring xmlns="http://www.w3.org/1999/xhtml"> <p>Raised if the user has insufficient <tp:dbus-ref namespace="imt1.Connection.Interface">Balance1</tp:dbus-ref> to place a call or send a message.</p> <p>The key 'balance-required' MAY be included in <tp:dbus-ref namespace="imt1.Channel.Type.Call1">CallStateDetails</tp:dbus-ref> or a delivery report's <tp:type>Message_Part</tp:type> (with the same units and scale as <tp:dbus-ref namespace="imt1.Connection.Interface.Balance1">AccountBalance</tp:dbus-ref>) to indicate how much credit is required to make this call or send this message.</p>

TP_ERROR_STR_MEDIA_CODECS_INCOMPATIBLE

Raised when the local streaming implementation has no codecs in common with the remote side. <tp:rationale> This corresponds to <tp:value-ref type="Call_State_Change_Reason">Media_Error</tp:value-ref>. </tp:rationale>

TP_ERROR_STR_MEDIA_UNSUPPORTED_TYPE

The media stream type requested is not supported by either the local or remote side. <tp:rationale> This corresponds to <tp:value-ref type="Call_State_Change_Reason">Media_Error</tp:value-ref>. </tp:rationale>

TP_ERROR_STR_MEDIA_STREAMING_ERROR

Raised when the call's streaming implementation has some kind of internal error. <tp:rationale> This corresponds to <tp:value-ref type="Call_State_Change_Reason">Internal_Error</tp:value-ref>. </tp:rationale>

TP_ERROR_STR_CAPTCHA_NOT_SUPPORTED

<tp:docstring xmlns="http://www.w3.org/1999/xhtml"> <p>Raised if the <tp:dbus-ref namespace="imt1.Channel.Interface">CaptchaAuthentication1</tp:dbus-ref> Handler either has no UI to present captchas, or it does, but wasn't able to answer any of the captchas given.</p>