HTTP response codes
JSONRPC errors
Code | Text Code | Description |
---|---|---|
-32700 | PARSE_ERROR | An error occurred on the BEMS-Connect service while parsing the JSON text. |
-32600 | INVALID_REQUEST | The received JSON is not a valid JSON-RPC message. |
-32601 | METHOD_NOT_FOUND | The requested remote procedure doesn't exist or is not available. |
-32602 | INVALID_PARAMS | The method parameters are invalid. |
BEMS-Connect errors (Generic)
BEMS-Connect
errors (Generic)Code | Text Code | Description |
---|---|---|
1004 | PARSE_ERROR | The BEMS-Connect service can't create the chat session. |
1005 | GENERAL_FAILURE | The BEMS-Connect service encountered a fatal error serving the request. |
1006 | GPS_NOT_RESPONDING | The BlackBerry Proxy is not responding. |
1007 | INVALID_GD_TOKEN | The BEMS-Connect service can't verify the GD token. |
1008 | INVALID_GD_AUTHTOKEN | The BEMS-Connect service could not verify the GD authtoken. |
1009 | GPS_HTTP_ERROR | An error response is received from the BlackBerry Proxy . |
1011 | NULL_ARGUMENT | One or more parameters are of a null value or empty. |
1012 | INVALID_ARGUMENT | One or more arguments are not valid. |
1013 | INVALID_OPERATION | An invalid operation occurred. |
1017 | CLIENT_SESSION_TIMEOUT | The BlackBerry Connect client session has timed out. |
1018 | OPERATION_FAILURE | The operation failed due to an invalid object state. |
1019 | RT_EXCEPTION | The operation failed due to SIP-related errors. |
1020 | PUBLISH_SUBSCRIBE_EXCPT | The SIP Service request was rejected by the instant messaging server. |
1021 | DEPENDENT_REQUEST_FAILED | A dependent request failed in this batch. |
1023 | SELF_REFERENCE_DEPENDENCY | The request makes a self referential dependency. |
1024 | UNKNOWN_BATCH_DEPENDENCY | The request dependency reference is unknown or undefined. |
1025 | ACTION_PENDING | The request is currently in progress. |
1026 | NOT_SUPPORTED_BY_SERVER | The request by the BlackBerry Connect client is not supported by this BEMS-Connect service version. |
1027 | WRONG_SERVER | The BlackBerry Connect client should connect to a different BEMS-Connect service. |
1028 | SERVER_BUSY | The server is too busy. |
SendMessage
Code | Text Code | Description |
---|---|---|
4000 | MSG_INVALID_OPERATION | The method is invoked multiple times using the same asyncResult. |
4001 | MSG_OPERATION_FAILURE | The operation failed due to invalid object state. |
4002 | REAL_TIME_FAILURE | The operation failed due to SIP-related errors. |
4003 | MSG_REMOTE_FAILURE_RESPONSE | The recipient contact doesn't respond to the establish request operation. |
4004 | MSG_DND_FAILURE | The message is not sent because the recipient has a Do Not Disturb state specified. |
4005 | MSG_NOT_FEDERATED_OR_INVALID_user | The contact is outside of your organization and is not federated with your company, or the user is invalid. |
4006 | INVITATION_FAILURE_RESPONSE | The recipient contact declined your invitation. |
Accept Chats
Code | Text Code | Description |
---|---|---|
7000 | INVALID_REQUESTID | An invitation is not available for the request ID. |
7001 | ACCEPT_CHAT_RT | The user is unable to complete accepting chat. |
7002 | AC_INVALID_PARAMS | BEMS-Connect service cannot accept the call because of invalid parameters. |
7003 | AC_INVALID_OPERATION | BEMS-Connect service cannot accept the call because of an invalid operation. |
4005 | MSG_NOT_FEDERATED_OR_INVALID
_USER | The user is outside of your organization and is not federated with your company, or the user is incorrect. |
4006 | INVITATION_FAILURE_RESPONSE | The recipient contact declined your invitation. |
BeginSession
Code | Text Code | Description |
---|---|---|
10000 | REGISTRATION_ERROR | An invitation is not available for the request ID. |
10001 | AUTHENTICATION_ERROR | The user is unable to complete accepting the chat request. |
TerminateSession
Code | Text Code | Description |
---|---|---|
11000 | SESSION_NOT_FOUND | The BEMS-Connect service couldn't find the session ID. Have the user log in to BlackBerry Connect again. |
11001 | XML_EXCEPTION | The BEMS-Connect service encountered a XML exception. |
AddContact
Code | Text Code | Description |
---|---|---|
12000 | ADD_CONTACT_FAILURE | Failed to add the contact to the BlackBerry Connect client contact list. |
12001 | ADD_CONTACT_EXISTS | The contact already exists in the BlackBerry Connect client contact list. |
RemoveContact
Code | Text Code | Description |
---|---|---|
13000 | REMOVE_CONTACT_FAILURE | Contact does not exist in the BlackBerry Connect client. |
BlockContact
Code | Text Code | Description |
---|---|---|
14001 | BLOCK_ALREADY_FAILURE | User is already blocked in the BlackBerry Connect client. |
UnblockContact
Code | Text Code | Description |
---|---|---|
15000 | UNBLOCK_CONTACT_FAILURE | Failed to unblock user. |
15001 | UNBLOCK_ALREADY_FAILURE | The user is already unblocked. |
Active Directory
Code | Text Code | Description |
---|---|---|
26000 | ADCACHE_EXCEPTION | Failed to setup ActiveDirectoryCache. |
26001 | ADCACHE_SIP_NOT_FOUND_EXCEPTION | Failed to find the SIP address of the contact. |
26002 | ADCACHE_MULTIPLE_SIP_EXCEPTION | The user has multiple SIP addresses. |
26003 | ADCACHE_INVALID_USER_EXCEPTION | The user is invalid. |
RegisterTempRemotePresence
Code | Text Code | Description |
---|---|---|
27000 | REGISTER_TEMP_REMOTE_PRESENCE_EXCEPTION | Failed to setup RegisterTempRemotePresence. |
27001 | REGISTER_TEMP_REMOTE_PRESENCE_ALREADY_EXISTS | The user already exists in the Contact List. |
UnregisterTempRemotePresence
Code | Text Code | Description |
---|---|---|
28000 | UNREGISTER_TEMP_REMOTE
_PRESENCE_EXCEPTION | Failed to setup RegisterTempRemotePresence. |
28001 | UNREGISTER_TEMP_REMOTE_
_PRESENCE_USER_NOT_IN_CONTACTLIST _CONTACTLIST_EXCEPTION | The user is not in the BlackBerry Connect contact list. |
28002 | UNREGISTER_TEMP_REMOTE
_PRESENCE_BAD_TYPE_EXCEPTION | The user has the wrong type (for example, the userID is an object type instead of a string type). |
NotifyBackground
Code | Text Code | Description |
---|---|---|
29001 | NOTIFYBACKGROUND_ ALREADY_IN_MODE | The BlackBerry Connect app is already in the background. |
StartChat
Code | Text Code | Description |
---|---|---|
31031 | CHAT_DOES_NOT_EXIST | There is no existing chat conversation with the specified recipient contact. |
31032 | WRONG_CHAT_ID | The existing chat conversation with the specified recipient contact has a different chat ID. |
31033 | CONTACT_OFFLINE | The specified contact is not logged in. |
31034 | NOT_CONTACT | The specified user is not on the contact list. |
Persistent chat
Code | Text Code | Description |
---|---|---|
40000 | PC_INVALID_OPERATION | The endpoint is not in a valid state. An endpoint can only be established once and cannot be reused after being terminated. |
40001 | PC_NULL_ARGUMENT | The asyncResult parameter is a null value. |
40002 | PC_COMMAND_FAILURE | The endpoint is not in a valid state to be established or the connection call flow is interrupted. |
40003 | PC_SERVER_CONNECTION_FAILURE | The PersistentChatEndpoint is not established, or the instant messaging server is not reachable, or the connection attempt is refused instant messaging server. |
40004 | PC_INVALID_PARAMS | The method includes invalid parameters. |
40005 | PC_GENERAL_FAILURE | The BEMS-Connect service encountered a fatal error serving the persistent chat request. |
40019 | PC_RT_EXCEPTION | The session encountered an error communicating with the instant messaging server. |
40020 | PC_SESSION_INVALID | The session is in an invalid state. The State cannot be idle. |
40021 | PC_INVALID_ARGUMENT | The input parameters are invalid. |
40025 | PC_MESSAGE_TOO_LONG | The message is too long. |
40100 | PC_NOT_SUPPORT_FAILURE | The persistent chat service is not enabled for this user or instant messaging server. |
40101 | PC_ROOM_STATE_FAILURE | Group discussion is in an invalid state or the user did not join yet. |
40102 | PC_ACCESS_DENIED | The signed in user is not authorized to perform the action. |
40103 | PC_DUPLICATE_ROOM_NAME | A group discussion or category with that name already exists. |
40104 | PC_ROOM_DISABLED | The group discussion is disabled. |
40105 | PC_ROOM_NOT_EXIST | The group discussion does not exist. |
40106 | PC_ROOM_NAME_TOO_LONG | The group discussion name is longer than 256 characters, spaces included. |
40107 | PC_ROOM_HIERARCHY_FAILURE | User cannot create rooms under the root category. |
40109 | PC_CONNECTION_INTERRUPTED | Connection flow interrupted. The endpoint is in an invalid state for the attempted operation. |
40110 | PC_DATABASE_CONNECTION_FAILURE | There was a problem with the BEMS-Connect service connection to the Microsoft SQL
Server database. |
40111 | PC_DATA_COLLISION_FAILURE | The object being modified has been changed. Refresh your copy of the object before attempting to modify it. |
40112 | PC_DUPLICATE_ADDIN_NAME | There is an existing addin name. |
40113 | PC_FILE_DOWNLOAD_FAILURE | BEMS failed to download the file. |
40114 | PC_FILE_UPLOAD_FAILURE | BEMS failed to upload the file. |
40115 | PC_INVALID_COMMAND_ARGUMENT | One or more provided parameters to the command are invalid. |
40116 | PC_INVALID_FILE_TRANSFER_TOKEN | Chat server (Lync/S4B) returned an invalid file transfer security token. |
40117 | PC_LIMIT_EXCEEDED | You have exceeded an internal server limit. |
40118 | PC_MESSAGE_NOT_SUPPORTED | The command is not supported by the BEMS-Connect service. |
40119 | PC_NO_SUCH_PRINCIPAL_FAILURE | One or more principals are invalid. |
40122 | PC_PRINCIPALS_ALREADY_DEFINED | The principals are already defined. |
40123 | PC_PRINCIPALS_NOT_IN_SCOPE | The principals are not in scope. |
40124 | PC_SERVER_ERROR | The instant messaging server reported an error. Refer to the exception message for the error code. |
40125 | PC_CREATE_ROOM_FAILURE | The signed in user cannot create the group discussion. |
40126 | PC_UNKNOWN_SERVER_FAILURE | An unknown error occurred on the server. |
40127 | PC_USER_NOT_JOINED_FAILURE | The signed in user has not joined to the group discussion. |
40128 | PC_PARTICIPANT_LIST_FAILURE | The user can't request the participant list of the group discussion. |
40129 | PC_DUPLICATE_ROOM_NAME_UPDATE_ UNKNOWN_SERVER_ERROR | An unknown error occurred on the Connect service. Updating the group discussion name with an existing room name may cause this error. |
40130 | PC_SAME_FILE_UPLOAD_NOT_ALLOWED | The file that is being uploaded to the specified group discussion is a duplicate. Duplicate uploads are not allowed. |
40131 | PC_FILE_POST_NOT_ALLOWED | File post operations are not allowed for the specified group discussion under category settings. |