Apéndice - Puerta de enlace SMS - Códigos de error
¿Qué son los códigos de error de SMS Gateway?Los códigos de error de SMS Gateway son códigos numéricos que se utilizan para indicar la causa de un error al enviar o recibir un mensaje SMS a través de un SMS Gateway. Los SMS Gateways son servidores intermediarios que permiten a empresas y particulares enviar y recibir mensajes SMS sin tener que conectarse directamente a un operador de red móvil.
Los códigos de error de SMS Gateway se pueden dividir en dos categorías principales:
- Errores relacionados con la red se indican con códigos en el rango 400. Estos errores pueden ocurrir por diversas razones, como que el teléfono de destino esté apagado, la red esté congestionada o el mensaje sea demasiado largo.
- Errores relacionados con el dispositivo se indican con códigos en el rango 500. Estos errores pueden ocurrir si el dispositivo no está configurado correctamente, si la tarjeta SIM no está insertada correctamente o si hay un problema de hardware con el dispositivo.
Los códigos de error de SMS Gateway generalmente se muestran como un mensaje de texto que comienza con la palabra "ERROR" seguida del código de error. Por ejemplo, un código de error de "400" indicaría un error de "Fallo de red", lo que significa que el mensaje no pudo enviarse debido a un problema con la red.
Los códigos de error de SMS Gateway pueden ser útiles para solucionar problemas con los mensajes SMS. Si recibes un código de error, puedes consultar una tabla de códigos de error de SMS Gateway para determinar la causa del error y tomar medidas para corregirlo.
Aquí están los principales códigos de error de SMS Gateway:
Errores relacionados con la red
- 400: Fallo de red
- 401: Buzón de destino ocupado
- 402: Buzón de destino no disponible
- 403: Mensaje demasiado largo
- 500: Error no especificado
- 501: Dirección del remitente inválida
- 502: Dirección de destino inválida
- 503: Contenido del mensaje inválido
Puedes encontrar la lista completa de códigos de error de SMS Gateway en la siguiente tabla:
Errorcode | Errorname | Errormessage |
Error messages | ||
1020 | ERROR_MAIN_BASE | |
1021 | ERROR_MAIN_GLOBALEXCEPTION | Global exception caught: [MSG] |
1022 | ERROR_MAIN_LOCALEXCEPTION | Local exception caught: [MSG] |
1023 | ERROR_MAIN_UNEXPECTED_STOP | Stopping engine due to an unknown error. [CODE] |
1024 | ERROR_MAIN_CANNOTLOAD_EXTENSION_PHASE1 | Cannot load extensions. [MSG] |
1025 | ERROR_MAIN_CANNOTLOAD_EXTENSION_PHASE2 | Cannot load extension [NAME]. [REASON] |
1030 | ERROR_LICENSING_BASE | |
1031 | ERROR_LICENSING_CANNOTCONTACT_ACTIVATIONSERVER | HTTP Download Error: [MSG] |
1032 | ERROR_LICENSING_CANNOTFIND_LICENSEFILE | Could not find license file [FILENAME]. |
1033 | ERROR_LICENSING_CANNOTLOAD_LICENSEFILE | Cannot load file [FILENAME]. Reason: [MSG] |
1034 | ERROR_LICENSING_CANNOT_SAVE_LICENSEFILE | Cannot save file [FILENAME]. Reason: [MSG] |
1040 | ERROR_CONFIG_BASE | |
1041 | ERROR_CONFIG_CANNOTCREATE_DIR | Unable to create directory '[DIR]'. [MSG] |
1042 | ERROR_CONFIG_CANNOTWRITE_FILE | Cannot write to file. Reason: '[REASON]' |
1043 | ERROR_CONFIG_CANNOTREAD_FILE | Cannot read configuration files. Reason: '[REASON]' |
1044 | ERROR_CONFIG_CANNOTDELETE_FILE | Cannot delete configuration file. [FILENAME] [MSG] |
1045 | ERROR_CONFIG_INVALIDSECTION | Invalid configuration directive in '[SECTIONNAME]' configuration. Directive: '[DIRECTIVE]' |
1046 | ERROR_CONFIG_INVALIDSECTION_SECTIONUNCLOSED | Unclosed section in configuration file. Check for closing , , tags. |
1047 | ERROR_CONFIG_INVALIDPARAM_ALREADYEXISTS | Duplicate values for parameter '[PARAM]' in [SECTIONNAME1] and [SECTIONNAME2]. Only the value [VALUE] is used. |
1048 | ERROR_CONFIG_INVALIDVALUE | Invalid configuration value '[VALUE]' for parameter '[PARAM]' in section '[SECTIONNAME]'. |
1049 | ERROR_CONFIG_INVALIDVALUE_LISTENERPORT | Cannot listen on port '[PORT]'. Invalid port number, using default port: 9500 |
1050 | ERROR_CONFIG_INVALIDVALUE_UNKNOWNSMSCPROTOCOL | Unknown protocol in configuration file: [PROTOCOL]. |
1051 | ERROR_CONFIG_INVALIDVALUE_NOPAIRFOUND | Parameter '[PARAM1]' in section '[SECTIONNAME]' must have a pair named '[PARAM2]'. |
1100 | ERROR_IFTCPCLIENT_BASE | |
1101 | ERROR_IFTCPCLIENT_CANNOTLISTEN | Cannot open TCP listener socket to accept clients on port '[PORT]'. ([MSG]) |
1102 | ERROR_IFTCPCLIENT_CONNECTTIMEOUT | Connect timeout. The connected TCP client [CLIENTNAME] did not send any data for more than 10 seconds. |
1103 | ERROR_IFTCPCLIENT_SOCKETERROR | Error during communication with UI: '[MSG]' |
1104 | ERROR_IFTCPCLIENT_CONNECTIONCLOSED | Client has closed connection ([ERRORMSG]) |
1105 | ERROR_IFTCPCLIENT_UNKNOWNPROTOCOL | Unknown protocol. SMPP, UCP, and OZTEXT are supported. |
1106 | ERROR_IFTCPCLIENT_TEXT_SYNTAXERROR | User '[USER]' has entered unknown command '[COMMAND]' on the console. |
1107 | ERROR_IFTCPCLIENT_TEXT_UNKNOWNPARAM | User '[USER]' has entered an unknown parameter '[PARAMETER]' for command '[COMMAND]' on the console. |
1108 | ERROR_IFTCPCLIENT_TCP_CLIENTTIMEOUT | Timeout. No response received for PDU |
1110 | ERROR_IFTCPCLIENT_SMPP_PROTOCOLUNSUPPORTED | Protocol '[PROT]' is not supported for this user. Check the 'Type' settings in the configuration file. |
1111 | ERROR_IFTCPCLIENT_SMPP_CLIENTTIMEOUT | Timeout. No response received for PDU '[PDUTYPE]'. |
1112 | ERROR_IFTCPCLIENT_SMPP_FORCEOUT | Another SMPP client ([CLIENTNAME]) is logged in with this username and password. That client will be disconnected because only one client instance is allowed to connect with a single username and password. Use a different username to connect with a second instance! Configure your client to connect as an SMPP transceiver! |
1113 | ERROR_IFTCPCLIENT_SMTP_MAILPARSE | Cannot parse incoming mail message from [FROM]. Mail format error. [MSG] |
1150 | ERROR_IFHTTP_BASE | |
1151 | ERROR_IFHTTP_LISTENER_GENERALERROR | ozHTTPListener error code: [CODE] says: [MSG] |
1152 | ERROR_IFHTTP_LISTENER_GENERALERROR2 | HTTPListener error code: [CODE] says: [MSG] |
1153 | ERROR_IFHTTP_INVALID_HTTPPORT | Cannot serve HTTP requests on this port. The HTTP API can be accessed on the following port: [PORT]. |
1154 | ERROR_IFHTTP_CANNOTSERVE_STATICCONTENT | Cannot serve static content [PATH]. [MSG] |
1155 | ERROR_IFHTTP_CANNOTSERVE_DYNAMICCONTENT | Cannot serve dynamic content [PATH]. [MSG] |
1156 | ERROR_IFHTTP_CANNOTREAD_TEMPLATE | Cannot read template [TEMPLATENAME], [FILENAME]. [MSG] |
1157 | ERROR_IFHTTP_UNKNOWNUSER | Invalid username or password. |
1158 | ERROR_IFHTTP_CANNOTFIND_ACTIONPARAM | No action parameter specified in HTTP query. |
1159 | ERROR_IFHTTP_INVALID_ACTIONPARAMVALUE | Action parameter specified in HTTP query is unknown: '[PARAM]'. |
1160 | ERROR_IFHTTP_INVALID_PARAMVALUE | Parameter '[PARAMNAME]' has an invalid value: '[VALUE]' |
1161 | ERROR_IFHTTP_MISSING_MANDATORYPARAM | The following mandatory parameter is missing from the request: '[PARAMNAME]'. |
1162 | ERROR_IFHTTP_INVALID_RESPONSEFORMAT | Invalid response format: [FORMAT]. |
1163 | ERROR_HTTPAPI_USERNOTFOUND | Cannot find user [USERNAME]. |
1164 | ERROR_HTTPAPI_PARAMETERMISSING | Mandatory HTTP parameter is missing: [PARAMNAME]. |
1165 | ERROR_HTTPAPI_ACTIONUNKNOWN | Invalid action parameter value: [NAME]. |
1166 | ERROR_HTTPAPI_CANNOTCREATEENV | Cannot create envelope. [MSG] |
1167 | ERROR_HTTPAPI_PARAMETERVALUEINVALID | Invalid parameter value for parameter [PARAMNAME]: '[PARAMVAL]' |
1180 | ERROR_IFREMOTING_BASE | |
1181 | ERROR_IFREMOTING_TRANSPORT_ERROR | Problem with API transport. [MSG] |
1182 | ERROR_IFREMOTING_GENERALERROR | Invalid API action. [MSG] |
1183 | ERROR_IFREMOTING_MESSAGEEVENT | Invalid event handling in API for event [EVENT]. [MSG] |
1184 | ERROR_IFREMOTING_STARTUP | Cannot start API. [MSG] |
1200 | ERROR_ENGINE_BASE | |
1201 | ERROR_ENGINE_CANNOTGET_ENVELOPE2SEND | Cannot get envelope from user [USERNAME]. [MSG] |
1210 | ERROR_ROUTER_BASE | |
1211 | ERROR_ROUTER_UNKNOWNUSER | Cannot add route. Unknown user '[USERNAME]'. [LINENO] |
1212 | ERROR_ROUTER_ROUTENAMENOTUNIQUE | Cannot add route. Route name is not unique '[ROUTENAME]'. [LINENO] |
1213 | ERROR_ROUTER_OPERATORNOTAVAILABLE | Cannot add route. Service provider name does not exist: '[OPERATORNAME]'. [LINENO] |
1214 | ERROR_ROUTER_INVALIDACTION | |
1216 | ERROR_ROUTER_COULDNOTFINDROUTEOUT | Message dropped. No outgoing route found. Message '[MSG]'. |
1217 | ERROR_ROUTER_COULDNOTFINDROUTEIN | Message dropped. No incoming route found for the message coming from operator [OPERATOR] '[MSG]'. |
1218 | ERROR_ROUTER_COULDNOTFINDCALLBACKID | Delivery reported as dropped. The corresponding message was sent more than 1 day ago. [MSG] |
1219 | ERROR_ROUTER_INVALIDREGEXP | Invalid regular expression [PATTERN] in routing condition. [ERROR]. [LINENO] |
1220 | ERROR_ROUTER_COULDNOTFINDROUTE | Could not find route [NAME] |
1221 | ERROR_ROUTER_LIMITREACHED | Sorry, you have reached the maximum number of routing rules (which is [NUMROUTES]) that you can add. |
1222 | ERROR_ROUTER_COULDNOTPLAYSOUND | Could not play sound: [NAME]. [MSG] |
1223 | ERROR_ROUTER_INVALIDCOST | Invalid cost value for route [NAME]: '[COST]' |
1224 | ERROR_ROUTER_COULDNOTFINDROUTEOUT_ROUTENAME | Message dropped. No outgoing route found. Route '[ROUTENAME]' does not exist. Message '[MSG]'. |
1225 | ERROR_ROUTER_COULDNOTFINDROUTEOUT_SIMPLE | Message dropped. No outgoing route found. |
1226 | ERROR_ROUTER_COULDNOTFINDROUTEOUT_ROUTENAME_SIMPLE | Message dropped. No outgoing route found. Route '[ROUTENAME]' does not exist. |
1227 | ERROR_ROUTER_INVALIDBACKUPROUTE | Invalid routing configuration. Routename [BACKEDROUTENAME] specified as a backup route in route [MYROUTENAME] does not exist. |
1228 | ERROR_ROUTER_COULDNOTFIND_BACKUPROUTE | Could not find a backup route to send the message. [MSG] |
1229 | ERROR_ROUTER_COULDNOTFIND_BACKUPROUTE_SIMPLE | Could not find a backup route to send the message. |
1240 | ERROR_SQLLOGING_BASE | |
1241 | ERROR_SQLLOGING_CANNOTCREATE_LOGDIR | Cannot create directory to store SQL log entries. [PATH]. [MSG] |
1242 | ERROR_SQLLOGING_CANNOTOPEN_LOGFILE | Cannot open log file for writing [PATH]. [MSG] |
1243 | ERROR_SQLLOGING_CANNOTWRITE_LOGENTRY | Cannot write SQL log entry [SQL]. [MSG] |
1244 | ERROR_SQLLOGING_CANNOTDELETE_QUEUEFILE | Cannot delete SQL queue file [FILENAME]. [MSG] |
1245 | ERROR_SQLLOGING_CANNOTWRITE_QUEUEFILE | Cannot write SQL queue file [FILENAME]. [MSG] |
1246 | ERROR_SQLLOGING_CANNOTREAD_QUEUEFILE | Cannot read SQL queue file [FILENAME]. [MSG] |
1250 | ERROR_ENCODING_BASE | |
1251 | ERROR_ENCODING_SCANOTFOUNDINPDU | Cannot find service center address in PDU. |
1252 | ERROR_ENCODING_UNKNOWNMESSAGETYPE | Unknown message type identifier in PDU. |
1253 | ERROR_ENCODING_MTNOTFOUNDINPDU | Cannot find message type field in PDU. |
1254 | ERROR_ENCODING_PHONENOLENNOTFOUNDINPDU | Cannot find phone number length byte in PDU. |
1255 | ERROR_ENCODING_INVALIDPHONENUMINPDU | Invalid phone number format in PDU. |
1256 | ERROR_ENCODING_PIDNOTFOUNDINPDU | Cannot find protocol identifier in PDU. |
1257 | ERROR_ENCODING_DCSNOTFOUNDINPDU | Cannot find data coding scheme in PDU. |
1258 | ERROR_ENCODING_SCTSNOTFOUNDINPDU | Cannot find service center timestamp in PDU. |
1259 | ERROR_ENCODING_UDLNOTFOUNDINPDU | Cannot find the user data length in the PDU. |
1260 | ERROR_ENCODING_TPMRNOTFOUNDINPDU | Cannot find TPMR in the PDU. |
1261 | ERROR_ENCODING_TPDTNOTFOUNDINPDU | Cannot find TPDT in the PDU. |
1262 | ERROR_ENCODING_STNOTFOUNDINPDU | Cannot find ST in the PDU. |
1263 | ERROR_ENCODING_DTNOTFOUNDINPDU | Cannot find DT in the PDU. |
1264 | ERROR_ENCODING_CANNOTENCODE | Cannot encode the PDU. Reason: [MSG] |
1265 | ERROR_ENCODING_CANNOTREADORDELSEGMENT | Cannot read or delete the multipart segment. [MSG] |
1266 | ERROR_ENCODING_TRNNOTFOUNDINSENTTRN | Cannot find TRN value '[TRN]' in the sent transactions. |
1267 | ERROR_ENCODING_TRNNOTFOUNDINSENTTRN2 | Cannot find TRN value '[TRN]' in the sent transactions (2). |
1268 | ERROR_ENCODING_CHECKSUMERROR | Checksum error in the PDU. [PDU] |
1269 | ERROR_ENCODING_CANNOTDECODE | Cannot decode the PDU. Reason: [MSG] |
1270 | ERROR_ENCODING_CANNOTENCODEMESSAGE | Cannot encode the message [MSG] |
1271 | ERROR_ENCODING_CANNOTCREATE_UNKNOWNTYPE | Unknown message type value '[MSG]'. Using default message type (SMS:TEXT) |
1273 | ERROR_ENCODING_CANNOTDECODE_UD | Cannot decode the User Data of the envelope. [MSG] |
1274 | ERROR_ENCODING_CANNOTDECODE_TEXTCOMPRESSIONNOTSUPPORTED | |
1275 | ERROR_ENCODING_CANNOTDECODE_UNKNOWNDCS |