<< Click to Display Table of Contents >> Navigation: Reference > Log Reference > Analyzing Logs > Call Log |
Navigation: Reference > Log Reference > Analyzing Logs >
This topic describes the format of and how to analyze unified gateway call logs.
Table 1 describes the call log format of the unified gateway.
Table 1 call log
Field |
Description |
Example |
Serial No |
Serial number of a call log in the LMT. |
2 |
CallerDn |
Calling number of the call corresponding to a call log. |
5000 |
Time |
Time when a call log is generated. |
20130221-16:46:21 |
CalleeDn |
Called number of the call corresponding to a call log. |
5001 |
LogID |
ID of a call log generated by the unified gateway. |
0x00000006 |
ReleaseCause |
Cause code of the call release corresponding to a call log. For details about the common cause codes, see Table 4. |
144 |
Description |
Cause description of the call release corresponding to a call log. |
Normal calls are cleared. |
Double-click the call log of a call and view the detailed log information in the lower pane.
With regard to the calling for a specific service function, enable the call log switch of the modules associated with the service type to obtain call logs. After the logs are obtained, trace the status of these modules based on the service process to check whether the process is correct and whether there is any important error message. You can also search for keywords for a quick fault locating.
ϒ⁄Tracing modules
The actual scenario may be a combination of multiple simple scenarios. In the actual scenario, you are advised to decompose the scenario and trace each module so that problems can be located quickly and accurately.
ϒ⁄Searching for keywords
Keywords can be used in log analysis. Table 2 provides error keywords, and Table 3 provides message keywords.
Table 2 Error keywords
Keyword |
Description |
error |
Error. |
fail |
Failed. The message fail does not necessarily indicate faults. |
release |
Release. The message release is recorded each time a call is released. You need to determine whether faults occur based on the process information. |
alert |
Alarm. |
Table 3 Message keywords
Keyword |
Description |
Modules Involved |
Setup |
A call is initiated and the call process starts. |
CCM, USAM, INTESS, and trunks |
Alerting |
The phone rings. |
CCM, USAM, INTESS, and trunks |
Connect |
Call connection. |
CCM, USAM, INTESS, and trunks |
Release |
Call release. |
CCM, USAM, INTESS, and trunks |
ϒ⁄Referring to return codes
You can refer to return codes during log analysis to determine fault causes. For common return codes, see Table 4.
Table 4 Return codes
Return Code |
Return Code |
0 |
Newservice set conflict. |
1 |
Newservice set ok. |
2 |
Newservice set failed. |
3 |
Newservice cancel ok. |
4 |
Newservice cancel failed. |
5 |
Newservice verify ok. |
6 |
Newservice verify failed. |
7 |
Newservice use ok. |
8 |
Newservice use failed. |
9 |
Malicious call tracing ok. |
10 |
Malicious call tracing failed. |
11 |
Assend user. |
12 |
No disturb. |
13 |
Rrecored call save. |
14 |
Remote test ok. |
15 |
Long time no information. |
16 |
Long time no release. |
17 |
In band signal. |
18 |
Cock failed. |
19 |
Exceed max reattempt time. |
20 |
Rrelease before ring. |
21 |
Release before answer. |
22 |
Call barring. |
23 |
Operator disconnect ok. |
24 |
Operator disconnect failed. |
29 |
Record use ok. |
30 |
Call in barring. |
31 |
Call fail(tup). |
32 |
Dual seize. |
33 |
Remote password update failed. |
34 |
Remote password update ok. |
35 |
Remote login call forward ok. |
36 |
Remote login call forward failed. |
37 |
Remote cancel call forward ok. |
38 |
Remote cancel call forward failed. |
39 |
Join conference ahead failed. |
40 |
Chairmen has entered. |
41 |
Diam called owned. |
42 |
Wrong password. |
43 |
Redirect restriction. |
44 |
User queue failed. |
45 |
Group queue failed. |
46 |
Timeout in queue. |
47 |
No CR. |
48 |
No CCM. |
49 |
No network resource. |
50 |
No DTMF resource. |
51 |
No MFC resource. |
52 |
No dialing abandon. |
53 |
No dialing timeout. |
54 |
Partial dial abandon. |
55 |
Partial dial timeout. |
56 |
Long time no alerting. |
57 |
Long time no answer. |
58 |
Console call waiting. |
59 |
Join conference as chairmen. |
60 |
User suspended. |
73 |
Waiting call clear. |
77 |
Black white list barring. |
78 |
Cli judge restriction. |
79 |
Redirect from trunk restriction. |
81 |
Reave cirecuit. |
82 |
Billpool is full. |
83 |
No immeconf resource. |
96 |
Dial no reserved. |
97 |
User port not active. |
98 |
Application conference list. |
99 |
Add conference list. |
100 |
Del conference list one. |
101 |
CFU. |
102 |
Consolegroup call forward. |
103 |
Conference room is full. |
104 |
Otmn clip booking. |
105 |
PKT trunk rerouting. |
106 |
License limited. |
107 |
Sipuser license limited. |
108 |
Specail number failed. |
109 |
Default route analyse failed. |
110 |
Call clear. |
111 |
Radius access failed. |
112 |
Radius account failed. |
113 |
Call transfered. |
116 |
Confer terminal operate ok. |
117 |
Card radius auth failed. |
118 |
Card radius charge failed. |
119 |
Card radius query balance failed. |
120 |
Card radius change password. |
121 |
Card radius account failed. |
122 |
Card radius wait authers timeout. |
123 |
One user bind onemore card. |
126 |
Diam time not enough. |
127 |
No instant conference right. |
128 |
Unknow. |
129 |
Uncalloced phone number. |
130 |
No route to specified internetwork. |
131 |
No route to termial. |
132 |
Send private tone. |
133 |
Error include long distance. |
134 |
Route unacceptable. |
135 |
Call has established and deliverd on route established. |
144 |
Normal call clear. |
145 |
Called busy. |
146 |
Called no respond. |
147 |
No acknowlege. |
149 |
Call rejected. |
150 |
Number changed. |
154 |
Clear unselected. |
155 |
Terminal error. |
156 |
Invalid format or address not enough. |
157 |
Facility rejected. |
158 |
Respond to status enquiry. |
159 |
Normal. |
160 |
Number portable has used. |
162 |
No route available. |
166 |
Network error. |
169 |
Error for the time being. |
170 |
Exchange facility surge. |
171 |
Access info lost. |
172 |
No route or circuit applied available. |
175 |
No resource availbale. |
177 |
No suitbale service quality. |
178 |
Facility applied not preserved. |
183 |
Incoming call uncallow. |
185 |
Bearer capability not permit. |
186 |
No bearer capablitity available this time. |
191 |
No suitable service or optional project. |
193 |
Bearer capability not lay out. |
194 |
Route type not lay out. |
197 |
Facility applied not lay out. |
198 |
Only limited digital info bearer capability. |
209 |
Service or optinal project not lay out. |
210 |
Invalid call reference. |
211 |
Route indentified not exist. |
212 |
Suspended call exist but no call indentifier. |
213 |
Call indentifier is using. |
214 |
No suspended call. |
215 |
Call has the call indentifier applied cleard. |
216 |
Called is not CUG. |
219 |
Terminal uncompatable. |
223 |
Invalied transmit network selection. |
224 |
Invalid message. |
225 |
Necessary IE lost. |
226 |
Message type not exist or not lay out. |
227 |
Message state error or message error. |
228 |
IE not exist or not lay out. |
229 |
Invalid ie content. |
231 |
Recovery of time out. |
238 |
Para not exist. |
239 |
Protocol error. |
255 |
Interwork. |
Parent Topic: Analyzing Logs