CAPITULO II. MARCO TEÓRICO
2.2. Fundamentación Teórica
2.2.10 Dispositivos de Red
This describes explanations and causes of R2 signaling error codes.
The UMG8900 supports R2 signaling that is processed by service resource modules. Table 7-10 lists the explanations and possible causes of error codes generated during R2 signaling processing.
Table 7-10 Explanations and possible causes of R2 signaling error codes (VPU)
Error Code Code Name Explanation Possible Cause
120 R2_NULLPOINTE
_ERROR Starting timer fails. The operating system fails.
Error Code Code Name Explanation Possible Cause
The state machine of the R2 module times out.
125 R2_DBM_QUERY_
ERROR Querying CDB fails. Querying the CDB fails.
126 R2_OFFICE_DIRE
CT_ERROR
The office directory error occurs.
Messages sent by the MGC are incorrect.
127 R2_DSPCHNNO_E
RROR
The DSP chip or path number error occurs.
The chip No. or channel No. is invalid.
128 R2_RMMD_REQC
HN_ERROR Applying a path fails. No channel is idle.
129 R2_RMMD_DELC
HN_ERROR Deleting a path fails.
The program for
The type or length in the message header
The length of the message sent by the CMU is incorrect.
Error Code Code Name Explanation Possible Cause
136 R2_MSG_EVENTR
EPEAT_ERROR
The address event is repeated.
The message sent by the MGC contains
No Termination ID is available.
The message sent by the CMU contains no TerminationID IE. the MGC does not match that in the CAS attribute table. length in the R2 attribute sent by the MGC exceeds the length sent by the CMU is incorrect. sent by the MGC are illegal or inconsistent with specific
protocols.
142 R2_MSG_DILEN_
ERROR
The length of called number is incorrect.
The called number length in the R2 address signal sent by the MGC exceeds the maximum value.
143 R2_MSG_DISTR_E
RROR
The content of called number string is incorrect.
The called number in the R2 address signal sent by the MGC contains illegal characters.
144 R2_MSG_SILEN_E
RROR
The length of caller number is incorrect.
The calling number length in the R2 address signal sent by the MGC exceeds the maximum value.
Error Code Code Name Explanation Possible Cause
145 R2_MSG_SISTR_E
RROR
The content of caller number string is incorrect.
The calling number in the R2 address signal sent by the MGC contains illegal characters.
146 R2_MSG_CCLEN_
ERROR
The length of country code is incorrect.
The country code length in the R2 address signal sent by the MGC exceeds the maximum value.
147 R2_MSG_CCSTR_
ERROR
The content of country code string is incorrect.
The country code in the R2 address signal sent by the MGC contains illegal characters.
148 R2_MSG_SIGNAL
TYPE_ERROR
The signal type is incorrect.
The R2 signal sent by the MGC is not of the CPRS signals at the same time.
The MGC sends an R2 address signal without the called number, or does not send a called number detection event.
Error Code Code Name Explanation Possible Cause
The signals sent by the MGC carry
The E32 board No.
sent by the MGC is incorrect.
155 R2_MSG_NODIGI
TMAP_ERROR No Digitmap exists.
The MGC does not send Digitmap with the R2 address event.
156 R2_MSG_CPLCNO
EXIST_ERROR
No called party line condition (CPLC) parameter exists in GPRS signals.
The CPRS signal sent by the MGC contains no CPLC.
157 R2_NUM_INVALI
D_ERROR
The R2 number is invalid.
The caller type sent by the MGC is out of
parameter sent by the MGC is out of range.
160 R2_DISC_ERROR The distinctive
indicator is incorrect.
The distinctive indicator parameter sent by the MGC is out of range.
161 R2_NAC_ERROR The nature of circuit
is incorrect.
The circuit nature parameter sent by the MGC is out of range.
162 R2_CALLING_SP_
ERROR
The caller priority is incorrect.
No called number is received.
Error Code Code Name Explanation Possible Cause
An error occurs to the state machine for
The logical events of register signaling
The signaling type is incorrect.
The CAS type of the UMG8900 is
signaling type of the UMG8900 is of the UMG8900 is incorrect. sent is not configured in the CAS attribute table.
Error Code Code Name Explanation Possible Cause
174 R2_CC_NO_RECO
RD_ERROR
No R2 country code records exist.
The R2 country code cannot be found in the country code configuration table.
175 R2_RSD_COMPLE
TE_ERROR
An error occurs after register signaling sending.
Sending CPRS signals by the MGC times out.
176 R2_DM_MATCH_
DETECT_ERROR
An error occurs to R2 Digitmap mode detection.
Digitmap match is incorrect.
177 R2_SENDSIGNAL
_ERROR Sending signals fails. Sending signal fails.
178 R2_STOPSIGNAL_
ERROR
Stopping signals
fails. Stopping signal fails.
179 R2_DSPACKFAIL_
ERROR DSP replying fails.
DSP
acknowledgement fails.
180 R2_DSPCHN_STA
TE_ERROR
The DSP path state is incorrect. DTMF digits is out of range.
The number of DTMFs sent exceeds the maximum value allowed at the bottom layer. to be sent is invalid.
183 R2_DP_CLDRSP_E
RROR
A reply is received indicating the failure of receiving the request to send/
receive called number.
Notifying the E32 to send or receive the called number fails. the called number by the E32 times out.
185 R2_DP_CLDFNS_E
RROR
A reply is received indicating the failure of sending/receiving called number.
The E32 fails to send or receive the called number.
Error Code Code Name Explanation Possible Cause waiting the E32 to complete sending or receiving the called number times out.
187 R2_DP_STOPCLD
RSP_ERROR
A reply is received indicating the failure of receiving the request to stop receiving/sending the called number.
Notifying the E32 to stop sending or the request that the E32 stops sending or receiving the called finds that the sent address send list is inconsistent with the configured address send list.
Error Code Code Name Explanation Possible Cause
190 R2_MSG_LACK_P
ARA_ERROR
The necessary parameters are lacking in the message.
R2 checks sent messages and configuration information, and finds that the request is sent in the MFP service stage and the sent address signal is incorrect, that is, lack of sc and si.
Error Code Code Name Explanation Possible Cause that sends the route state signal, the signal type is Indian R2 signaling.
During processing of MFS signaling codes received by R15, the message type is incorrect.
During processing of MFGP-R15
signaling codes received by R2, the message type is the idle state of the R15 MFP2 channel, the office direction is the incoming send direction is the incoming direction.
After application for R2 channel to start service processing,
Error Code Code Name Explanation Possible Cause received when no channel exists.
During processing of the send tone request sent by the CMU, the RSD type is
RSD_MFP2 and the office direction is the incoming direction.
R15 MFP2 does not support incoming
information is to be sent.
The state of the TC channel is incorrect.
195 R2_EVENT_NOEX
IST_ERROR
The report event does not exist.
The report event does not exist.
196 R2_EVENT_PARA
LENGTH_ERROR
The parameter length of the reported event is incorrect.
The parameter length of the reported event is incorrect.
197 R2_MSG_LACK_E
VENT_ERROR
The necessary events are lacking in the message.
The message lacks necessary events.
198 R2_MSG_TFNNOE
XIST_ERROR
No TFN parameter is in the TN signal.
When R2 analyzes the IE:R2 tariff code signal, the TFN tariff code does not exist.
199 R2_TN_CODE_ER
ROR
The tariff code signal error occurs.
The tariff code signal is invalid.
200 R2_TN_NO_RECO
RD_ERROR
No tariff code record for R2 is available.
Querying the tariff code fails.
201 R2_TN_FLOW_ER
ROR
The tariff code flow error occurs.
During processing of tariff code sent by R2, the request is sent again after the code is sent.
Error Code Code Name Explanation Possible Cause
The address format is incorrect. event, the state is MSD_TC_MOD_A UTOT38SWITCH_
WA.
255 RETCODE_TEST_
CHIP_NOTEXIST
The tested chip does not exist on the CMU.
The tested chip on the CMU does not exist.