Error codes

In the connector log files protocol specific error codes may be displayed within parenthesis when send or receive operations fail. The most common of these error codes are specified below, per protocol.

• CIMD2
• SMPP
• UCP/EMI
• OIS
• HTTP
• SMTP
• MGP
• EBE
• Linux error codes

CIMD2

Error code	Description
0	No error
1	Unexpected operation
2	Syntax error
3	Unsupported parameter error
9	Requested operation failed
100	Invalid login
102	Too many users with this login id
103	Login refused
300	Incorrect destination address
302	Syntax error in user data parameter
303	Incorrect user data parameter combination

SMPP

Error code	Description
0	No error
3	Invalid command id
4	Invalid bind status for given command
5	ESME already in bound state
8	System error
10	Invalid source address
11	Invalid destination address
12	Message ID is invalid
13	Bind failed
14	Invalid password
15	Invalid system id
20	Message queue full
21	Invalid system type
69	submit_sm failed
88	Throttling error (ESME has exceeded allowed message limits)
97	Invalid scheduled delivery time
98	Invalid message validity period

UCP/EMI

Error code	Description
1	Checksum error
2	Syntax error
3	Operation not supported by system
4	Operation not allowed
5	Call barring active
6	AdC (destination address) invalid
7	Authentication failure
22	Time period not valid
23	Message type not supported by system
24	Message too long

OIS

Error code	Description
0	Success
1	Invalid data
2	atabase (message data store) full
3	SME busy
5	Duplicate message
6	Destination unavailable
20	Call barred by user
21	Transmission error
24	Unknown subscriber
25	Call barred by network operator (destination)
26	Call barred by network operator (originator)
120	Network failure

HTTP

EMG can send back the following set of status codes for HTTP requests.

Status code	Status name	Description
200	Ok	An incoming message posted to /bin/send was received. The response contains three lines: the message id, the MGP status, and a text description. If the message was rejected, the message id is -1.
201	Created	An OAuth2 access token was created.
202	Accepted	An incoming MMS was received and accepted.
401	Unauthorized	The provided credentials were invalid.
402	Payment required	The EMG account did not have sufficient credits.
404	Not found	The URL was invalid.
500	Internal error	The submitted message was invalid.
501	Not implemented	The HTTP verb was not GET or POST.
503	Server busy	The maximum total queue size has been reached, so the submitted message was rejected. Submitting the message again at a later time may succeed.

SMTP

Error code	Description
220	Service ready
250	Requested mail action ok
251	User not local will forward to
421	Service not available
450	Mailbox unavailable
451	Requested action aborted
452	Requested action not taken
500	Syntax error, command unrecognized
501	Syntax error in parameter or arguments
502	Command not implemented
503	Bad sequence of commands
504	Command parameter not implemented
550	Requested action not taken

MGP

Error code	Description
Error code	Description
0	OK, no error
1	Unknown
2	Syntax error
3	Login
4	Already bound
5	Invalid arguments
6	Invalid command
7	Invalid message id
8	Invalid destination address
9	Invalid source address
10	No access
11	Message error
12	Invalid response
13	Communication error
14	Database error
15	UDH error
16	No credits left
17	Busy
18	Too long
19	Expired
20	No route

EBE

Error code	Description
0	No error
1	Message is rejected by the EBE script
127	EBE script could not run (“chmod +x program” not run?)

Linux error codes

Error codes returned from the Linux operating system, for example when trying to connect to remote entities (“CONNECT ERR” in connector log).

Error code	Errno	Description
110	ETIMEDOUT	Connection timed out
111	ECONNREFUSED	Connection refused