Internal Message Trace Guide - Training Slide: Security Level
Internal Message Trace Guide - Training Slide: Security Level
Internal Message Trace Guide - Training Slide: Security Level
www.huawei.com
IP Core
P registration P subscription
P session processing P P/IM processing
processing processing
P user data
SIPCB Charging QoS
management
NAT
P user index
management SIP distribution DIAMETER
distribution
COPS DNS
SIP TPT, CODEC
COMPRESS, IPSec DIAMETER CM
DPU
UDP/IP TCP/IP
BSU
HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 13
Related Tasks on the Application Layer of the
I-CSCF
UDP/IP TCP/IP
BSU
HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 14
Related Tasks on the Application Layer of the
S-CSCF
S calling party S called party
processing processing
S registration SP/IM S subscription
processing processing processing
S ILCM S OLCM
S subscription
SIPCB Charging Cx/Dx
data management
ENUM transaction
S user index
management SIP distribution DIAMETER
distribution
DNS/ENUM
SIP TP, CODEC
DIAMETER CM
CDB
UDP/IP TCP/IP
BSU
HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 15
Chapter 1 CSCF Architecture: Internal Module
(PID) and Its Functions
Remarks:
PID: In this document, a PID refers to the sub-module of a process (module). A PID is the
basic unit used for message communication.
For example, the PREG, PCALL, SREG, and SCALL are the sub-modules of the SCU
process.
MID: It indicates the module ID. In this document, the internal message trace mainly involves
the SCU and CDB processes.
3 Source It indicates the source IP address of the message and has a value only for an external (inter-NE)
Address message.
4 Source port It indicates the source port number of the message and has a value only for an external (inter-NE)
message.
5 Destination It indicates the destination IP address of the message and has a value only for an external (inter-NE)
Address message.
6 Destination It indicates the destination port number of the message and has a value only for an external (inter-NE)
port message.
7 Message Message interface type: Indicates the message that module A sends to module B.
Interface Type For example, TRC_MI_SIPC_P indicates the message that the SIPC sends to the PREG and PCALL.
CSCF_TRACE_MI_PREG_SIPC indicates the message that the PREG sends to the SIPC.
8 Message Type Message type name
For example, SIG_TRACE_MSG_INVITE_REQ indicates the INVITE message that the SIPC sends to
the PCALL.
CSCF_TRACE_MSG_ANID_QUERY indicates the message that the PREG sends to the DBMS to query
the access network ID.
9 Hex Message Hexadecimal code stream data of the message
Message interface type: Specifies whether the message is between two modules (PIDs) or between NEs.
For example:
TRC_MI_SIPC_P: Indicates a message sent by the SIPC to the PREG and PCALL.
CSCF_TRACE_MI_IMSG_DBMS: Indicates a message sent by the IMSG to the DBMS for data query.
Remarks: On the message trace interface, Diameter messages and SIP messages are identified in different
colors.
1.REGISTER
2.DNS Query
3.DNS Query
Resp
4. REGISTER
5. Diameter: UAR
6. Diameter: UAA
7.REGISTER
8.Diameter: MAR
10. 401 9.Diameter: MAA
Unauthorized
12. 401 11. 401 Unauthorized
Unauthorized
13.REGISTER
14.DNS Query
15.DNS Query
Resp
16. REGISTER
17. Diameter: UAR
18. Diameter: UAA
19.REGISTER
20.Diameter: SAR
21.Diameter: SAA
22. 200 OK
23. 200 OK AS
24. 200 OK
25.REGISTER
26. 200 OK
1.REGISTER(req)
2.DBMS_QUERY(req)
3.DBMS_QUERY(rsp)
4.REGISTER(rsp)
5.REGISTER(req)
6.DBMS_QUERY(req)
7.DBMS_QUERY(rsp)
8.REGISTER(rsp)
9.REGISTER(req)
10.DBMS_QUERY(req)
11.DBMS_QUERY(rsp)
12.REGISTER(rsp)
INVITE
INVITE
INVITE
INVITE
INVITE
INVITE
INVITE183
INVITE183
INVITE183
INVITE183
INVITE183
INVITE183
PRACK
PRACK
PRACK
PRACK
PRACK
PRACK200 PRACK200
PRACK200 INVITE180
PRACK200 INVITE180
PRACK200 INVITE180
INVITE200
INVITE180 INVITE200
INVITE180 INVITE200
INVITE180 INVITE200
INVITE200
INVITE200
ACK
ACK
ACK
BYE ACK
BYE ACK
BYE
BYE
BYE
BYE200
BYE200 BYE200
BYE200
BYE200
R15: INFO
R16: INFO_REQ
R17: INFO_RSP
R18: PLAY-MEDIA-REQ
R19: 200 OK
R20: MOD_REQ
R21: MOD_REPLY
R22: PLAY-MEDIA-RSP
R23: NTFY_REQ
R24: NTFY_REPLY
R25: MEDIA-COMPLETED-IND
R26: STOP-MEDIA-REQ
R27: : MOD_REQ
R28: MOD_REPLY
R29: STOP-MEDIA-RSP
R30: DETECT-DTMF-REQ
R31: MOD_REQ
R32: MOD_REPLY
R33: DETECT-DTMF-RSP
R34: NTFY_REQ
R35: NTFY_REPLY
R36: REPORT-DTMF-IND
R37: STOP-DTMF-DETECT-REQ
R38: MOD_REQ
R39: MOD_REPLY
R40: STOP-DTMF-DETECT-RSP
R41: INFO-REQ
R42: INFO
R43: 200 OK
R44: INFO-RSP
R45: BYE
R46: BYE-REQ
R47: BYE-RSP
R48: REL-SIPC-REQ R49: DB-MRFP-
RELEASE-REQ
R50: RELEASE-TERM-REQ
R51: 200 OK
R53: DB-MRFP- R52: SUB_REQ
RELEASE-RSP
R54: SUB_REPLY
R55: RELEASE-TERM-RSP
Message capture:
MRFC·ÅÒôÊÕºÅÁ÷³Ì
Module It corresponds to the SCU module No. The module No. can be
011 Attention required
number displayed on the Module Management interface on the OMU client.
Internal information
It refers to the failure to compare the received SIP message from the
Error cause 0000361d that does not require
access side with the contact address specified during the registration.
attention
The contents enclosed within quotation marks "" are the error
Error Fail to validate information. Currently, most errors are represented by Server internal
error, which provides no information about the error. A user can find Attention required
description the user
out the error only after querying codes. This problem needs to be
solved.
After a message is sent, if no response is received within the timeout time, the protocol stack reports an error response to inform
the service NE of the timeout.
Structure analysis:
The following attachment summarizes the release points of the CSCF service processing:
F:\IMSÖúÊÖ\
CSCFÒµÎñ´¦ÀíÊͷŵã»ã×Ü.rar
Step 2: Based on the contents in the Warning header field, check which NE sends the error response.
According to the message flows before and after the error response is returned, locate the message
that the NE receives before sending the failure response. Then, according to the main functions of the
NEs in the flow, infer the possible causes of the release.
Step 4: Based on the functions of the PID and release cause prompt text, analyze the possible causes.
Generally, possible causes can be classified into the following types:
1. The system configuration is incorrect.
Incorrect system configuration causes basic call and number analysis flow failures. In this case, check whether the related data
configuration is correct, for example, whether the link is Up.
Check whether the terminal is connected to a correct access network.
2. The user is not defined.
The user information carried in the SIP message that the user sends for registration is inconsistent with the user definition information
on the HSS.
3. The message does not conform to the protocol specifications. For example, the media negotiation does not conform to the protocol
specifications and a mandatory header field is missing.
In this case, in addition to checking whether the processing on the CSCFs is correct, analyze whether the messages sent by the
terminals and other NEs are correct.
Step 5: Based on the analysis result obtained in Step 4, check the related configuration.
Remarks: If the cause of the problem fails to be located after careful configuration check by performing the preceding procedure, save
the internal trace messages and contact the R&D personnel for locating the problem.
The I-CSCF The peer HSS of Check the traced Lines 47 and ulErrorCode
returns a 500 the I-CSCF is messages. Check whether 57 in line 47 and
response faulty. the I-CSCF sends any UAR. Warning in IHSSÁ´Â·DOWN
during If not, check whether the line 57
registration. IHSSL link is Up.
The P-CSCF The P-CSCF fails Check the traced messages Lines 11 and ulErrorCode
returns a 403 to query the between the Preg and 22 in line 11 and
response PACN table. DBMS. Check whether the Warning in
during PACN query is successful. If line 22 ×¢²áʱ½ÓÈëÍøµÄip
µØÖ·ÅäÖôíÎó£¬P»Ø403.rar.
registration. not, check whether the IP
address of the terminal
belongs to the network
segment configured on the
PACN.
The S-CSCF During the registration, the Check whether Lines 6, 173, integrity-
returns a 403 P-CSCF fails to set the access security is and 189 protected,
response during integrity-protected field to configured in the Warning in line PACN
ÖнÓÈë²à°²È«²ßÂÔÅäÖôíÎó,×¢²áS»Ø40
registration. Yes. Therefore, the S- access network 189, and
CSCF considers the security policy of ucAccessSecuri
registration request as the PACN. ty in line 6
invalid.
During registration, The P-CSCF, I-CSCF, or Check whether Lines 28, 29, Warning in line
the protocol stack S-CSCF fails to locate the the DNSSRV and 30, 31, and 56 56 and DNSÅäÖôíÎó£¬PÕÒ
²»µ½I--ptmf.rar
reports a 408 nexthop route or locates an DNSRESA are ulIpAddress in
timeout response. incorrect route. configured line 31
correctly.
During the The Contact address If the P-CSCF fails to Lines 210, 228, acPIpDispatchKey
call flow, used during the query the user data, 233, and 254 in line 210,
the P- registration carries check whether the query ulErrorCode and
CSCF Userinfo, whereas the keyword and the user acPDispatchKey in
×¢²áʱCONTACTµØ
returns a Contact address in the keyword saved during the line 233, and Ö·ÀïЯ´øUSRINFO£¬µ«INVITEÎ