infoX V100R001.3D3 錯誤碼說明書

1、infox錯誤碼說明書（3d3e）產(chǎn)品名稱密級infox產(chǎn)品版本共28頁v100r001infox v100r001.3d3 錯誤碼說明書prepared by 擬制陳向榮date日期2003-12-3reviewed by 評審人date日期approved by批準(zhǔn)date日期revision record 修訂記錄distribution list 分發(fā)記錄copy no.holder's name & role 持有者和角色issue date 分發(fā)日期1<rdpdt pdt開發(fā)代表>2<project manager 項目經(jīng)理>3<tea

2、m members 項目組成員>4<customer representative 客戶代表>5<others其它>catalog 目 錄1簡介52smpp話單錯誤碼53cmpp消息應(yīng)答錯誤碼63.1cmpp協(xié)議登錄錯誤碼63.2cmpp異步流程錯誤碼63.3cmpp3.0同步流程錯誤碼63.4cmpp2.0同步流程錯誤碼73.5cmpp狀態(tài)報告錯誤stat含義73.6給gns應(yīng)答錯誤碼說明94接口斷連錯誤碼說明94.1infox接口斷連的原因概述94.2業(yè)務(wù)模塊發(fā)送的消息協(xié)議錯誤104.3握手或接收異常錯誤104.4tcp/ip的socket關(guān)閉或產(chǎn)生異常114

3、.5windows平臺socket錯誤碼說明114.6unix平臺socket錯誤碼說明195維測及網(wǎng)管錯誤碼說明196錯誤碼說明216.1.1aaaa網(wǎng)關(guān)錯誤碼216.1.2bbbb scp返回的錯誤碼236.1.3cccc ismg返回的錯誤碼256.1.4dddd sp返回的錯誤碼256.1.5eeee dsmp返回的錯誤碼256.1.6ffff smc返回的錯誤碼276.1.7gggg space返回的錯誤碼296.1.8xxxx消息發(fā)往scp、sp、dsmp、smc出錯時錯誤碼296.1.9zzzz為smsc返回的狀態(tài)報告中err的值29 infox錯誤碼說明書keywords 關(guān)鍵

4、詞：abstract 摘 要：list of abbreviations 縮略語清單： abbreviations縮略語full spelling 英文全名chinese explanation 中文解釋smppshort message point to point protocoll 點對點短消息協(xié)議smsc（ smc）short message service center短消息中心cmppchina mobil point to point移動短消息點到點新協(xié)議dsmp數(shù)據(jù)業(yè)務(wù)處理平臺scpservice control point業(yè)務(wù)控制點1 簡介該文檔 適用于infoxv100r0

5、01.3d2版本網(wǎng)關(guān)。文檔讀者：infox維護人員2 smpp話單錯誤碼錯誤碼含義aaaa網(wǎng)關(guān)錯誤碼1xxxx消息發(fā)往scp出錯時錯誤碼2bbbbscp返回錯誤應(yīng)答時的錯誤碼，其中bbbb為scp返回的錯誤應(yīng)答消息中的錯誤碼值3xxxx消息發(fā)往下一級ismg出錯時錯誤碼4cccc下一級ismg返回錯誤應(yīng)答時的錯誤碼，其中cccc為下一級ismg返回的錯誤應(yīng)答消息中的錯誤碼值5xxxx消息發(fā)往sp出錯時錯誤碼6ddddsp返回錯誤應(yīng)答時的錯誤碼，其中dddd為sp返回的錯誤應(yīng)答消息中的錯誤碼值7xxxx消息發(fā)往dsmp出錯時錯誤碼8eeeedsmp返回錯誤應(yīng)答時的錯誤碼，其中eeee為dsmp返

6、回的錯誤應(yīng)答消息中的錯誤碼值9xxxx消息發(fā)往smc出錯時錯誤碼10ffffsmc返回錯誤應(yīng)答時的錯誤碼，其中ffff為smc返回的錯誤應(yīng)答消息中的錯誤碼值11xxxx消息發(fā)往space出錯時錯誤碼12ggggspace返回錯誤應(yīng)答時的錯誤碼，其中ffff為space返回的錯誤應(yīng)答消息中的錯誤碼值 有關(guān)aaaa、xxxx、bbbb、cccc、dddd、eeee、ffff和gggg的含義參見錯誤碼說明內(nèi)部等待狀態(tài)報告錯誤嗎： 錯誤碼含義98004等待狀態(tài)報告實體數(shù)不夠98005等待狀態(tài)報告超時98009等待狀態(tài)報告短信中心地址為空3 cmpp消息應(yīng)答錯誤碼3.1 cmpp協(xié)議登錄錯誤碼14為cm

7、pp協(xié)議標(biāo)準(zhǔn)錯誤碼，5557為網(wǎng)關(guān)擴展錯誤碼，59保留錯誤碼含義1消息結(jié)構(gòu)錯2非法源地址3認證錯4版本太高55超過系統(tǒng)接口數(shù)56超過帳號設(shè)置接口數(shù)57sp登陸ip錯誤58創(chuàng)建soap處理線程失敗59保留3.2 cmpp異步流程錯誤碼錯誤碼含義參見aaaa的取值說明3.3 cmpp3.0同步流程錯誤碼110000：網(wǎng)關(guān)錯誤碼2000130000：scp錯誤碼4000150000：前轉(zhuǎn)網(wǎng)關(guān)錯誤碼6000170000：sp錯誤碼8000190000：dsmp錯誤碼100001110000 ：smc錯誤碼120001 ：space錯誤碼錯誤碼含義aaaa網(wǎng)關(guān)錯誤碼2bbbbscp返回錯誤應(yīng)答時的錯誤碼

8、，其中bbbb為scp返回的錯誤應(yīng)答消息中的錯誤碼值4cccc下一級ismg返回錯誤應(yīng)答時的錯誤碼，其中cccc為下一級ismg返回的錯誤應(yīng)答消息中的錯誤碼值6ddddsp返回錯誤應(yīng)答時的錯誤碼，其中dddd為sp返回的錯誤應(yīng)答消息中的錯誤碼值8eeeedsmp返回錯誤應(yīng)答時的錯誤碼，其中eeee為dsmp返回的錯誤應(yīng)答消息中的錯誤碼值10ffffsmc返回錯誤應(yīng)答時的錯誤碼，其中ffff為smc返回的錯誤應(yīng)答消息中的錯誤碼值12ggggspace返回錯誤應(yīng)答時的錯誤碼，其中g(shù)ggg為space返回的錯誤應(yīng)答消息中的錯誤碼值3.4 cmpp2.0同步流程錯誤碼 1100：本網(wǎng)關(guān)錯誤碼 1012

9、00：前轉(zhuǎn)網(wǎng)關(guān)錯誤碼 201240：scp錯誤碼 241255：smc錯誤碼錯誤碼含義aa（199）網(wǎng)關(guān)錯誤碼，aa的取值參見aaaa的取值說明100aa 下一級ismg返回錯誤應(yīng)答時的錯誤碼201239scp返回錯誤應(yīng)答時的錯誤碼，其值含義參見相應(yīng)網(wǎng)關(guān)的配置文件cmpperrmap.dat。其中201為沒有對應(yīng)關(guān)系的scp錯誤241255smc返回錯誤應(yīng)答時的錯誤碼，其值含義參見相應(yīng)網(wǎng)關(guān)的配置文件cmpperrmap.dat，其中241為沒有對應(yīng)關(guān)系的smc錯誤3.5 cmpp狀態(tài)報告錯誤stat含義message statefinal message statesdescriptionde

10、livereddelivrdmessage 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)

11、unknownunknownmessage is in invalid staterejectedrejectdmessage is in a rejected statenoroutenoroute查找路由失敗ma:xxxxma:xxxxsmsc不返回響應(yīng)消息時的狀態(tài)報告mb:xxxxmb:xxxxsmsc返回錯誤響應(yīng)消息時的狀態(tài)報告mc:xxxxmc:xxxx沒有從smsc處接收到狀態(tài)報告時的狀態(tài)報告ca:xxxxca:xxxxscp不返回響應(yīng)消息時的狀態(tài)報告cb:xxxxcb:xxxxscp返回錯誤響應(yīng)消息時的狀態(tài)報告da:xxxxda:xxxxdsmp不返回響應(yīng)消息時的狀態(tài)報告db:x

12、xxxdb:xxxxdsmp返回錯誤響應(yīng)消息時的狀態(tài)報告sa:xxxxsa:xxxxsp不返回響應(yīng)消息時的狀態(tài)報告sb:xxxxsb:xxxxsp返回錯誤響應(yīng)消息時的狀態(tài)報告ia:xxxxia:xxxx下一級ismg不返回響應(yīng)消息時的狀態(tài)報告ib:xxxxib:xxxx下一級ismg返回錯誤響應(yīng)消息時的狀態(tài)報告ic:xxxxic:xxxx沒有從下一級ismg處接收到狀態(tài)報告時的狀態(tài)報告id:xxxxid:xxxx網(wǎng)關(guān)ismg內(nèi)部檢測錯誤碼id:0020id:0020space用戶鑒權(quán)模塊鑒權(quán)用戶停機或欠費錯誤id:0021id:0021space用戶鑒權(quán)模塊：用戶銷戶錯誤mi:zzzzmi:z

13、zzzsmsc返回狀態(tài)報告的狀態(tài)值為expiredmj:zzzzmj:zzzzsmsc返回狀態(tài)報告的狀態(tài)值為deletedmk:zzzzmk:zzzzsmsc返回狀態(tài)報告的狀態(tài)值為undelivml:zzzzml:zzzzsmsc返回狀態(tài)報告的狀態(tài)值為acceptdmm:zzzzmm:zzzzsmsc返回狀態(tài)報告的狀態(tài)值為unknownmn:zzzzmn:zzzzsmsc返回狀態(tài)報告的狀態(tài)值為rejectdmh:zzzzmh:zzzz其它值注意：其中accepted為中間狀態(tài)，網(wǎng)關(guān)若從短信中心收到后應(yīng)丟棄，不做任何操作；stat字段長度為7個字節(jié)，填寫時應(yīng)填表一中final message s

14、tates中的縮寫形式，如狀態(tài)為delivered時填寫delivrd，依此類推；3.6 給gns應(yīng)答錯誤碼說明錯誤碼含義0系統(tǒng)操作成功1沒有匹配路由2源網(wǎng)關(guān)代碼錯誤3路由類型錯誤4本節(jié)點不支持更新（gns分節(jié)點）5路由信息更新失敗6匯接網(wǎng)關(guān)路由信息時間戳比本地路由信息時間戳舊9系統(tǒng)繁忙10update_type錯誤11路由編號錯誤12目的網(wǎng)關(guān)代碼錯誤13目的網(wǎng)關(guān)ip錯誤14目的網(wǎng)關(guān)port錯誤15mt路由起始號碼段錯誤16mt路由截止號碼段錯誤17手機所屬省代碼錯誤18用戶類型錯誤19sp_id錯誤20sp_code錯誤21sp_accesstype錯誤22service_id錯誤23sta

15、rt_code錯誤24end_code錯誤4 接口斷連錯誤碼說明4.1 infox接口斷連的原因概述接口斷連的原因一般可分為三類，分別為：a、握手超時（enquire link）b、業(yè)務(wù)模塊發(fā)送的消息協(xié)議錯誤c、tcp/ip的socket關(guān)閉或產(chǎn)生異常。以下將對各情況進行描述。4.2 業(yè)務(wù)模塊發(fā)送的消息協(xié)議錯誤此情況由于客戶模塊發(fā)送了結(jié)構(gòu)錯誤的消息，或者消息錯位，導(dǎo)致infox讀取消息錯誤。由于infox與客戶模塊采用消息流格式，為防止由于消息錯位造成以后的消息都不能正確取得，此時，對于基中的某些消息，infox將斷連接口。原因分別為：錯誤碼原因分析后續(xù)操作97001缺省解碼失敗為防止以后消息

16、錯位，接口將斷連97002消息頭錯誤為防止以后消息錯位，接口將斷連97003源緩沖區(qū)不夠，不處理繼續(xù)接收消息97004目的緩沖區(qū)不夠為防止以后消息錯位，接口將斷連97005嚴重協(xié)議錯誤為防止以后消息錯位，接口將斷連97006協(xié)議中某字段一般性錯誤只刪除此消息，不斷開接口97007接收到nack消息為防止以后消息錯位，接口將斷連97008接收太多的握手接口將斷連97009地址錯誤，npi、ton不支持只刪除此消息，不斷開接口97010時間格式錯誤只刪除此消息，不斷開接口97011dcs錯誤只刪除此消息，不斷開接口97012協(xié)議不支持只刪除此消息，不斷開接口9701397999保留例：2001/0

17、5/28 15:31:03 2 id為32的接口產(chǎn)生接口斷連信息，對端地址：10.10.2.1 errcode:97001,errortype:04.3 握手或接收異常錯誤錯誤碼原因分析后續(xù)操作19000保留19001接收消息的buff出了問題接口將斷連19002解碼返回的值不對（只能是0/-1/>0）接口將斷連19003握手超時接口將斷連19004對端主動關(guān)閉socket19005連接對方服務(wù)器的間隔時間，到時重連19006發(fā)送login請求后，等待對方服務(wù)器的應(yīng)答消息超時19007進行socket底層的連接建立，等待connect函數(shù)的時間19008dsmpfep read消息錯誤4

18、.4 tcp/ip的socket關(guān)閉或產(chǎn)生異常此情況是由于客戶端主動關(guān)閉退出產(chǎn)生的提示信息，錯誤代碼為“0”；例：2001/05/28 15:32:14 2 id為32的接口產(chǎn)生接口斷連信息，對端地址：10.10.2.1 errcode:0,errortype:0或者由于socket底層的其它異常錯誤，導(dǎo)致接口斷連，此時的錯誤碼將有多種多樣，詳細描述請見windows平臺socket錯誤碼說明及unix平臺錯誤碼說明。例：2001/05/30 15:49:32 2 id為32的接口產(chǎn)生接口斷連信息，對端地址：10.10.2.1 errcode:10054,errortype:04.5 wind

19、ows平臺socket錯誤碼說明msdn對于socket異常id的描述錯誤碼值錯誤碼標(biāo)識含義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 br

20、oadcast 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 th

21、e 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 instan

22、ces, 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. 10

23、035wsaewouldblockresource 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

24、 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

25、 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 soc

26、ket 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

27、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 erro

28、r 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 itsel

29、f. 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 protoc

30、ol 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

31、_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_

32、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.1004

33、6wsaepfnosupportprotocol 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

34、 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_stre

35、am). 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 perm

36、itted. 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

37、 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 i

38、s "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

39、 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 in

40、dicate 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 kn

41、ows 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 o

42、n 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 w

43、as 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

44、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

45、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_dg

46、ram 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

47、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 sock

48、et 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 conne

49、cted 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

50、 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. the

51、se 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 application

52、s 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 p

53、rovide 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 f

54、irst 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

55、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)