产品名称密级infoX产品版本共33页V100R001infoX V100R001.4D2 错误码说明书Prepared by 拟制陈向荣Date日期2003-12-3Reviewed by 评审人Date日期Approved by批准Date日期Huawei Technologies Co., Ltd. 华为技术有限公司All rights reserved版权所有 侵权必究（DVP05T04 V2.2/ IPD-CMM V2.0 / for internal use only）（DVP05T04 V2.2/ IPD-CMM V2.0 / 仅供内部使用）Revision Record 修订记录Date日期Revision Version修订版本CR ID / Defect IDCR号Sec No. 修改章节Change Description修改描述Author作者2003-12-31.00初稿完成陈向荣2003-12-231.01根据蒋玲利评审意见修改孙记堂2004-4-23根据3D8版本修改陈向荣2004-6-4增加HP、IBM平台的错误码说明陈向荣2004-9-141.04根据4D2版本修改Distribution List 分发记录Copy No.Holder's Name & Role 持有者和角色Issue Date 分发日期12345Catalog 目 录1 简介 52 SMPP话单错误码 53 CMPP消息应答错误码 63.1 CMPP协议登录错误码 63.2 CMPP异步流程错误码 63.3 CMPP3.0同步流程错误码 63.4 CMPP2.0同步流程错误码 73.5 CMPP状态报告错误stat含义 74 接口断连错误码说明 84.1 infoX接口断连的原因概述 84.2 业务模块发送的消息协议错误 84.3 握手或接收异常错误 94.4 TCP/IP的SOCKET关闭或产生异常 104.5 WINDOWS平台SOCKET错误码说明 104.6 UNIX平台SOCKET错误码说明 175 维测及网管错误码说明 236 错误码说明 25 AAAA网关错误码 25 BBBB SCP返回的错误码 27 CCCC ISMG返回的错误码 29 DDDD SP返回的错误码 29 EEEE DSMP返回的错误码 29 FFFF SMC返回的错误码 31 XXXX消息发往SCP、SP、DSMP、SMC出错时错误码 33 infoX错误码说明书Keywords 关键词：Abstract 摘 要：List of abbreviations 缩略语清单： Abbreviations缩略语Full spelling 英文全名Chinese explanation 中文解释SMPPShort Message Point to Point Protocoll 点对点短消息协议SMSC（ SMC）Short Message Service Center短消息中心CMPPChina Mobil Point to Point移动短消息点到点新协议DSMP数据业务处理平台SCPService control point业务控制点1 简介该文档 适用于infoXV100R001.4D2版本网关。
文档读者：infoX维护人员2 SMPP话单错误码错误码含义AAAA网关错误码1XXXX消息发往SCP出错时错误码2BBBBSCP返回错误应答时的错误码，其中BBBB为SCP返回的错误应答消息中的错误码值3XXXX消息发往下一级ISMG出错时错误码4CCCC下一级ISMG返回错误应答时的错误码，其中CCCC为下一级ISMG返回的错误应答消息中的错误码值5XXXX消息发往SP出错时错误码6DDDDSP返回错误应答时的错误码，其中DDDD为SP返回的错误应答消息中的错误码值7XXXX消息发往DSMP出错时错误码8EEEEDSMP返回错误应答时的错误码，其中EEEE为DSMP返回的错误应答消息中的错误码值 CMPP3.0为DSMP;9XXXX消息发往SMC出错时错误码10FFFFSMC返回错误应答时的错误码，其中FFFF为SMC返回的错误应答消息中的错误码值11XXXX消息发往SPACE出错时错误码12GGGGSPACE返回错误应答时的错误码，其中FFFF为SPACE返回的错误应答消息中的错误码值（SPACE：CMPP2.0、3.0为DHLR） 有关AAAA、XXXX、BBBB、CCCC、DDDD、EEEE、FFFF的含义参见错误码说明 内部等待状态报告错误吗： 错误码含义98004等待状态报告实体数不够98005等待状态报告超时98009等待状态报告短信中心地址为空3 CMPP消息应答错误码3.1 CMPP协议登录错误码1～4为CMPP协议标准错误码，55～57为网关扩展错误码，59～保留错误码含义1消息结构错2非法源地址3认证错4版本太高55超过系统接口数56超过帐号设置接口数57SP登陆IP错误58创建soap处理线程失败59保留60登陆帐号并非属于登陆的PROXY3.2 CMPP异步流程错误码错误码含义参见AAAA的取值说明3.3 CMPP3.0同步流程错误码1～10000：网关错误码20001～30000：SCP错误码40001～50000：前转网关错误码60001～70000：SP错误码80001～90000：DSMP错误码100001～ ：SMC错误码120001～ ：SPACE错误码错误码含义AAAA网关错误码2BBBBSCP返回错误应答时的错误码，其中BBBB为SCP返回的错误应答消息中的错误码值4CCCC下一级ISMG返回错误应答时的错误码，其中CCCC为下一级ISMG返回的错误应答消息中的错误码值6DDDDSP返回错误应答时的错误码，其中DDDD为SP返回的错误应答消息中的错误码值8EEEEDSMP返回错误应答时的错误码，其中EEEE为DSMP返回的错误应答消息中的错误码值10FFFFSMC返回错误应答时的错误码，其中FFFF为SMC返回的错误应答消息中的错误码值12GGGGSPACE返回错误应答时的错误码，其中GGGG为SPACE返回的错误应答消息中的错误码值3.4 CMPP2.0同步流程错误码 1～100：本网关错误码 101～200：前转网关错误码 201～240：SCP错误码 241～255：SMC错误码错误码含义AA（1～99）网关错误码，AA的取值参见AAAA的取值说明100＋AA 下一级ISMG返回错误应答时的错误码201~239SCP返回错误应答时的错误码，其值含义参见相应网关的配置文件CmppErrMap.dat。
其中201为没有对应关系的SCP错误241～255SMC返回错误应答时的错误码，其值含义参见相应网关的配置文件CmppErrMap.dat，其中241为没有对应关系的SMC错误3.5 CMPP状态报告错误stat含义Message StateFinal Message StatesDescriptionDELIVEREDDELIVRDMessage is delivered to destinationEXPIREDEXPIREDMessage validity period hasexpiredDELETEDDELETEDMessage has been deleted.UNDELIVERABLEUNDELIVMessage is undeliverableACCEPTEDACCEPTDMessage is in accepted state(i.e. has been manually read on behalf of the subscriber by customer service)UNKNOWNUNKNOWNMessage is in invalid stateREJECTEDREJECTDMessage is in a rejected stateNOROUTENOROUTE查找路由失败MA:xxxxMA:xxxxSMSC不返回响应消息时的状态报告MB:xxxxMB:xxxxSMSC返回错误响应消息时的状态报告MC:xxxxMC:xxxx没有从SMSC处接收到状态报告时的状态报告CA:xxxxCA:xxxxSCP不返回响应消息时的状态报告CB:xxxxCB:xxxxSCP返回错误响应消息时的状态报告DA:xxxxDA:xxxxDSMP不返回响应消息时的状态报告DB:xxxxDB:xxxxDSMP返回错误响应消息时的状态报告SA:xxxxSA:xxxxSP不返回响应消息时的状态报告SB:xxxxSB:xxxxSP返回错误响应消息时的状态报告IA:xxxxIA:xxxx下一级ISMG不返回响应消息时的状态报告IB:xxxxIB:xxxx下一级ISMG返回错误响应消息时的状态报告IC:xxxxIC:xxxx没有从下一级ISMG处接收到状态报告时的状态报告ID:xxxxID:xxxx网关ISMG内部检测错误码ID:0020ID:0020SPACE用户鉴权模块鉴权用户停机或欠费错误ID:0021ID:0021SPACE用户鉴权模块：用户销户错误MI::zzzzMI::zzzzSMSC返回状态报告的状态值为EXPIREDMJ:zzzzMJ:zzzzSMSC返回状态报告的状态值为DELETEDMK:zzzzMK:zzzzSMSC返回状态报告的状态值为UNDELIVML:zzzzML:zzzzSMSC返回状态报告的状态值为ACCEPTDMM:zzzzMM:zzzzSMSC返回状态报告的状态值为UNKNOWNMN:zzzzMN:zzzzSMSC返回状态报告的状态值为REJECTDMH:zzzzMH:zzzz其它值注意：其中ACCEPTED为中间状态，网关若从短信中心收到后应丢弃，不做任何操作；Stat字段长度为7个字节，填写时应填表一中Final Message States中的缩写形式，如状态为DELIVERED时填写DELIVRD，依此类推；4 接口断连错误码说明4.1 infoX接口断连的原因概述接口断连的原因一般可分为三类，分别为：A、握手超时（Enquire Link）B、业务模块发送的消息协议错误C、TCP/IP的SOCKET关闭或产生异常。
以下将对各情况进行描述4.2 业务模块发送的消息协议错误此情况由于客户模块发送了结构错误的消息，或者消息错位，导致infoX读取消息错误由于infoX与客户模块采用消息流格式，为防止由于消息错位造成以后的消息都不能正确取得，此时，对于基中的某些消息，infoX将断连接口原因分别为：错误码原因分析后续操作97001缺省解码失败为防止以后消息错位，接口将断连97002消息头错误为防止以后消息错位，接口将断连97003源缓冲区不够，不处理继续接收消息97004目的缓冲区不够为防止以后消息错位，接口将断连97005严重协议错误为防止以后消息错位，接口将断连97006协议中某字段一般性错误只删除此消息，不断开接口97007接收到NACK消息为防止以后消息错位，接口将断连97008接收太多的握手接口将断连97009地址错误，NPI、TON不支持只删除此消息，不断开接口97010时间格式错误只删除此消息，不断开接口97011DCS错误只删除此消息，不断开接口97012协议不支持只删除此消息，不断开接口97013～97999保留例：2001/05/28 15:31:03 2 ID为32的接口产生接口断连信息，对端地址： ErrCode:97001,ErrorType:04.3 握手或接收异常错误错误码原因分析后续操作19000保留19001接收消息的Buff出了问题接口将断连19002解码返回的值不对（只能是0/-1/>0）接口将断连19003握手超时接口将断连19004对端主动关闭Socket19005连接对方服务器的间隔时间，到时重连19006发送Login请求后，等待对方服务器的应答消息超时19007进行Socket底层的连接建立，等待connect函数的时间19008Dsmpfep read消息错误4.4 TCP/IP的SOCKET关闭或产生异常此情况是由于客户端主动关闭退出产生的提示信息，错误代码为“0”；例： 2001/05/28 15:32:14 2 ID为32的接口产生接口断连信息，对端地址： ErrCode:0,ErrorType:0或者由于SOCKET底层的其它异常错误，导致接口断连，此时的错误码将有多种多样，详细描述请见WINDOWS平台SOCKET错误码说明及UNIX平台错误码说明。
例：2001/05/30 15:49:32 2 ID为32的接口产生接口断连信息，对端地址： ErrCode:10054,ErrorType:04.5 WINDOWS平台SOCKET错误码说明MSDN对于SOCKET异常ID的描述错误码值错误码标识含义10004WSAEINTRInterrupted function call. A blocking operation was interrupted by a call to WSACancelBlockingCall.10013WSAEACCESPermission denied. An attempt was made to access a socket in a way forbidden by its access permissions. An example is using a broadcast address for sendto without broadcast permission being set using setsockopt(SO_BROADCAST). 10014WSAEFAULTBad address. The system detected an invalid pointer address in attempting to use a pointer argument of a call. This error occurs if an application passes an invalid pointer value, or if the length of the buffer is too small. For instance, if the length of an argument which is a struct sockaddr is smaller than sizeof(struct sockaddr). 10022WSAEINVALInvalid argument. Some invalid argument was supplied (for example, specifying an invalid level to the setsockopt function). In some instances, it also refers to the current state of the socket - for instance, calling accept on a socket that is not listening. 10024WSAEMFILEToo many open files. Too many open sockets. Each implementation may have a maximum number of socket handles available, either globally, per process or per thread. 10035WSAEWOULDBLOCKResource temporarily unavailable. This error is returned from operations on non-blocking sockets that cannot be completed immediately, for example recv when no data is queued to be read from the socket. It is a non-fatal error, and the operation should be retried later. It is normal for WSAEWOULDBLOCK to be reported as the result from calling connect on a non-blocking SOCK_STREAM socket, since some time must elapse for the connection to be established.10036WSAEINPROGRESSOperation now in progress. A blocking operation is currently executing. Windows Sockets only allows a single blocking operation to be outstanding per task (or thread), and if any other function call is made (whether or not it references that or any other socket) the function fails with the WSAEINPROGRESS error. 10037WSAEALREADYOperation already in progress. An operation was attempted on a non-blocking socket that already had an operation in progress - i.e. calling connect a second time on a non-blocking socket that is already connecting, or canceling an asynchronous request (WSAAsyncGetXbyY) that has already been canceled or completed.10038WSAENOTSOCKSocket operation on non-socket. An operation was attempted on something that is not a socket. Either the socket handle parameter did not reference a valid socket, or for select, a member of an fd_set was not valid. 10039WSAEDESTADDRREQDestination address required. A required address was omitted from an operation on a socket. For example, this error will be returned if sendto is called with the remote address of ADDR_ANY. 10040WSAEMSGSIZEMessage too long. A message sent on a datagram socket was larger than the internal message buffer or some other network limit, or the buffer used to receive a datagram into was smaller than the datagram itself. 10041WSAEPROTOTYPEProtocol wrong type for socket. A protocol was specified in the socket function call that does not support the semantics of the socket type requested. For example, the ARPA Internet UDP protocol cannot be specified with a socket type of SOCK_STREAM. 10042WSAENOPROTOOPTBad protocol option. An unknown, invalid or unsupported option or level was specified in a getsockopt or setsockopt call.10043WSAEPROTONOSUPPORTProtocol not supported. The requested protocol has not been configured into the system, or no implementation for it exists. For example, a socket call requests a SOCK_DGRAM socket, but specifies a stream protocol. 10044WSAESOCKTNOSUPPORTSocket type not supported. The support for the specified socket type does not exist in this address family. For example, the optional type SOCK_RAW might be selected in a socket call, and the implementation does not support SOCK_RAW sockets at all. 10045WSAEOPNOTSUPPOperation not supported. The attempted operation is not supported for the type of object referenced. Usually this occurs when a socket descriptor to a socket that cannot support this operation, for example, trying to accept a connection on a datagram socket.10046WSAEPFNOSUPPORTProtocol family not supported. The protocol family has not been configured into the system or no implementation for it exists. Has a slightly different meaning to WSAEAFNOSUPPORT, but is interchangeable in most cases, and all Windows Sockets functions that return one of these specify WSAEAFNOSUPPORT. 10047WSAEAFNOSUPPORTAddress family not supported by protocol family. An address incompatible with the requested protocol was used. All sockets are created with an associated "address family" (i.e. AF_INET for Internet Protocols) and a generic protocol type (i.e. SOCK_STREAM). This error will be returned if an incorrect protocol is explicitly requested in the socket call, or if an address of the wrong family is used for a socket, e.g. in sendto. 10048WSAEADDRINUSEAddress already in use. Only one usage of each socket address (protocol/IP address/port) is normally permitted. This error occurs if an application attempts to bind a socket to an IP address/port that has already been used for an existing socket, or a socket that wasn't closed properly, or one that is still in the process of closing. For server applications that need to bind multiple sockets to the same port number, consider using setsockopt(SO_REUSEADDR). Client applications usually need not call bind at all - connect will choose an unused port automatically. When bind is called with a wild-card address (involving ADDR_ANY), a WSAEADDRINUSE error could be delayed until the specific address is "committed." This could happen with a call to other function later, including connect, listen, WSAConnect or WSAJoinLeaf.10049WSAEADDRNOTAVAILCannot assign requested address. The requested address is not valid in its context. Normally results from an attempt to bind to an address that is not valid for the local machine. This can also result from connect, sendto, WSAConnect, WSAJoinLeaf, or WSASendTo when the remote address or port is not valid for a remote machine (e.g. address or port 0). 10050WSAENETDOWNNetwork is down. A socket operation encountered a dead network. This could indicate a serious failure of the network system (i.e. the protocol stack that the WinSock DLL runs over), the network interface, or the local network itself. 10051WSAENETUNREACHNetwork is unreachable. A socket operation was attempted to an unreachable network. This usually means the local software knows no route to reach the remote host.10052WSAENETRESETNetwork dropped connection on reset. The connection has been broken due to "keep-alive" activity detecting a failure while the operation was in progress. It can also be returned by setsockopt if an attempt is made to set SO_KEEPALIVE on a connection that has already failed. 10053WSAECONNABORTEDSoftware caused connection abort. An established connection was aborted by the software in your host machine, possibly due to a data transmission timeout or protocol error. 10054WSAECONNRESETConnection reset by peer. A existing connection was forcibly closed by the remote host. This normally results if the peer application on the remote host is suddenly stopped, the host is rebooted, or the remote host used a "hard close" (see setsockopt for more information on the SO_LINGER option on the remote socket.) This error may also result if a connection was broken due to "keep-alive" activity detecting a failure while one or more operations are in progress. Operations that were in progress fail with WSAENETRESET. Subsequent operations fail with WSAECONNRESET.10055WSAENOBUFSNo buffer space available. An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full. 10056WSAEISCONNSocket is already connected. A connect request was made on an already connected socket. Some implementations also return this error if sendto is called on a connected SOCK_DGRAM socket (For SOCK_STREAM sockets, the to parameter in sendto is ignored), although other implementations treat this as a legal occurrence. 10057WSAENOTCONNSocket is not connected. A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using sendto) no address was supplied. Any other type of operation might also return this error - for example, setsockopt setting SO_KEEPALIVE if the connection has been reset.10058WSAESHUTDOWNCannot send after socket shutdown. A request to send or receive data was disallowed because the socket had already been shut down in that direction with a previous shutdown call. By calling shutdown a partial close of a socket is requested, which is a signal that sending or receiving or both has been discontinued. 10060WSAETIMEDOUTConnection timed out. A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.10061WSAECONNREFUSEDConnection refused. No connection could be made because the target machine actively refused it. This usually results from trying to connect to a service that is inactive on the foreign host - i.e. one with no server application running. 10064WSAEHOSTDOWNHost is down. A socket operation failed because the destination host was down. A socket operation encountered a dead host. Networking activity on the local host has not been initiated. These conditions are more likely to be indicated by the error WSAETIMEDOUT. 10065WSAEHOSTUNREACHNo route to host. A socket operation was attempted to an unreachable host. See WSAENETUNREACH10067WSAEPROCLIMToo many processes. A Windows Sockets implementation may have a limit on the number of applications that may use it simultaneously. WSAStartup may fail with this error if the limit has been reached. 10091WSASYSNOTREADYNetwork subsystem is unavailable. This error is returned by WSAStartup if the Windows Sockets implementation cannot function at this time because the underlying system it uses to provide network services is currently unavailable. Users should check: that the appropriate Windows Sockets DLL file is in the current path, that they are not trying to use more than one Windows Sockets implementation simultaneously. If there is more than one WINSOCK DLL on your system, be sure the first one in the path is appropriate for the network subsystem currently loaded. the Windows Sockets implementation documentation to be sure all necessary components are currently installed and configured correctly. 10092WSAVERNOTSUPPORTEDWINSOCK.DLL version out of range. The current Windows Sockets implementation does not support the Windows Sockets specification version requested by the application. Check that no old Windows Sockets DLL files are being accessed. 10093WSANOTINITIALISEDSuccessful WSAStartup not yet performed. Either the application hasn't called WSAStartup or WSAStartup failed. The application may be accessing a socket which the current active task does not own (i.e. trying to share a socket between tasks), or WSACleanup has been called too many times. 10094WSAEDISCONGraceful shutdown in progress. Returned by WSARecv and WSARecvFrom to indicate the remote party has initiated a graceful shutdown sequence.10109WSATYPE_NOT_FOUNDClass type not found. The specified class was not found. 11001WSAHOST_NOT_FOUNDHost not found. No such host is known. The name is not an official hostname or alias, or it cannot be found in the database(s) being queried. This error may also be returned for protocol and service queries, and means the specified name could not be found in the relevant database.11002WSATRY_AGAINNon-authoritative host not found. This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server. A retry at some time later may be successful. 11003WSANO_RECOVERYThis is a non-recoverable error. This indicates some sort of non-recoverable error occurred during a database lookup. This may be because the database files (e.g. BSD-compatible HOSTS, SERVICES or PROTOCOLS files) could not be found, or a DNS request was returned by the server with a severe error.11004WSANO_DATAValid name, no data record of requested type. The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for. The usual example for this is a hostname -> address translation attempt (using gethostbyname or WSAAsyncGetHostByName) which uses the DNS (Domain Name Server), and an MX record is returned but no A record - indicating the host itself exists, but is not directly reachable. 4.6 UNIX平台SOCKET错误码说明错误码值错误码标识含义HP平台10001EPERMNot super-user10002 ENOENTNo such file or directory10003ESRCHNo such process10004EINTRinterrupted system call10005EIOI/O error10006ENXIONo such device or address10007E2BIGArg list too long10008ENOEXECExec format error 。