ZXUN CSCF

Troubleshooting
Training Material

ZTE UNIVERSITY
ZTE University, Dameisha
YanTian District, Shenzhen,
P. R. China
518083
Tel: (86) 755 26778800
Fax: (86) 755 26778999
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION

Copyright © 2010 ZTE CORPORATION.

The contents of this document are protected by copyright laws and international treaties. Any reproduction or distribution of
this document or any portion of this document, in any form by any means, without the prior written consent of ZTE CORPO-
RATION is prohibited. Additionally, the contents of this document are protected by contractual confidentiality obligations.

All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE CORPORATION
or of their respective owners.

This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions are dis-
claimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or non-in-
fringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the use of or reliance on the
information contained herein.

ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications covering the subject
matter of this document. Except as expressly provided in any written license between ZTE CORPORATION and its licensee,
the user of this document shall not acquire any license to the subject matter herein.

ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.

Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.

The ultimate right to interpret this product resides in ZTE CORPORATION.

Publishing Date (MONTH/DATE/YEAR) : 2010401

Contents

ZXUN CSCF Troubleshooting ......................................... 1

1 Fault Location Principles ........................................... 2
1.1 Fault Location Principles ......................................................... 2
1.2 Principle Introduction ............................................................. 2
2 Fault Location Approaches ........................................ 3
2.1 Alarm and Notification ............................................................ 3
2.2 Signaling Tracing ................................................................... 4
2.3 Tracing Failure Observation ..................................................... 4
2.4 Flow Trace ............................................................................ 5
2.4.1 All Flow Trace ............................................................... 5
2.4.2 Interior Flow Trace ........................................................ 6
2.5 Fault Code Portability Function ................................................ 6
3 Fault Location Steps .................................................. 7
3.1 Common Steps ..................................................................... 7
3.2 Fault Information Feedback..................................................... 7
4 Common Faults Instance ........................................... 9
4.1 Common Faults Inside NEs...................................................... 9
4.1.1 S-CSCF Replies with 403 when Registering
Authentication.................................................................................. 9
4.1.2 Fail to Forward Messages During Callee 's Session ............. 9
4.1.3 Registration on the Terminal is Cancelled Automatically
....................................................................................................10
4.1.4 Respond the Call with 404 Message ................................10
4.1.5 Caller Responds with 403 Message .................................10
4.1.6 S-CSCF Fails to Trigger AS .............................................11
4.1.7 Fail to Send the SAR Message on S-CSCF ........................11
4.1.8 Respond with 500 Message when Registering on
S-CSCF ..........................................................................................11
4.1.9 CSCF Responds with 503 Message ..................................12
4.1.10 CSCF Responds with 504 Message ................................12
4.2 Common Interworking Fault ...................................................13
 4.2.1 P-CSCF Responds with 403 Message when SBC Calls
P-CSCF ..........................................................................................13
4.2.2 Calling Number Display Error when SBC Makes a Call .........13
4.2.3 Call Fails to Reach MGCF ...............................................13
4.2.4 PSS Fails to Send Prack .................................................13
4.2.5 Media Information Loss .................................................14
Glossary ..................................................................... 15
ZXUN CSCF
Troubleshooting
After you have completed this course, you

will be able to:

>> Master Faults Positioning Principles
>> Master Faults Positioning Approaches
>> Master Faults Positioning Steps
>> Master Positioning and Handling Ap-
proaches of Common Faults

Confidential and Proprietary Information of ZTE CORPORATION 1

ZXUN CSCF Training Material

Chapter 1 Fault Location Principles

After you have completed this chapter, you will know:
>> Fault Location Principles
>> Principles Introduction

1.1 Fault Location Principles

� Locate the faults firstly inside and then outside.
� Locate the faults firstly in the system and then in the module.
� Locate the faults firstly in software and then in hardware.

1.2 Principle Introduction

First Outside, There are many NEs in the IMS network, such as SBC, P-CSCF,
Then Inside I-CSCF, S-CSCF, ZXUN SSS, UP10 and MGCF. Thus fault location
sequence comes as follows:
1. Be clear of which NE generated thif fault by code stream and
fault code portability function.
2. Analyze the detailed cause of this fault by further fault obser-
vation and signaling tracing.
First System, Then Here assumes that ZXUN CSCF has several sub-systems, including
Module SIP protocol stack, Diameter protocol stack, service and charging.
Thus fault location sequence comes as follows:
1. Be clear of the large layer or the sub-system.
2. Analyze the interior modules of the sub-system.
For instance, you have found it's SIP protocol stack fault, and then
fix whether it belongs to TU, TR or TP module.
First Software, Take the case of fault probability, software faults outnumber hard-
Then Hardware ware fault in spite of board and memory bank faults.
Therefore, we must pay much attention to the software fault, es-
pecially the frequently happened problems.

2 Confidential and Proprietary Information of ZTE CORPORATION

Chapter 2 Fault Location
Approaches

After you have completed this chapter, you will know:

>> Alarm and Notification
>> Signaling Tracing
>> Failure Trace
>> Flow Trace
>> Fault Code Portability Function

2.1 Alarm and Notification

Application When the key error results in startup failure, inefficient memory
of Alarm and results in abnormal service provision or overloaded system re-
Notification source results in malfunction, you can find the cause promptly
through error information output from NM alarms, and then trou-
bleshoot.
Collected information of alarm management falls into 3 categories:
alarm, recovery and notification.
� An alarm refers to serious faults or errors, such as halted mod-
ule, no data in the database, link communication interruption
and overtop CPU usage.
Alarm information is saved in foreground memory until receiv-
ing alarm recovery message from the alarm resource.
� Alarm recovery: After troubleshooting, the alarm resource re-
ports the recovery message of corresponding alarm to elimi-
nate the alarm displayed on NM monitoring platform.
� Notification: Notification refers to the prompt or caution of
some normal or unrecoverable events, such as module pow-
ering on, active/standby switchover and successful database
startup.
Application Scope � Basic Flow Fault
of Alarm and
Notification � Call Loss
� Multi-Module Performance
� Observe running status of the device.

Confidential and Proprietary Information of ZTE CORPORATION 3

ZXUN CSCF Training Material

2.2 Signaling Tracing

Signaling Tracing To certain extend, signaling tracing and code stream of the packet
Application catcher are similar, however, the packet catcher analyzes the re-
port transmitted in the network.
For instance, SIP signaling tracing analyzes the messages between
SIP protocol stack layers, between the SIP protocol stack and BRS,
and between the SIP protocol stack and upper layer service.
You can obtain these protocol reports through NM signaling tracing
and decode and analyze them.
Signaling Tracing In the Trace Managment interface of the Local Maintennace
Operations Terminal, select Signaltrace > CSCF > SIP > SIPByFlow, and
condition setting interface is shown in Figure 1, the items with *
are compulsory parameters.

FIGURE 1 OPERATION INTERFACE

Application Scope � When the packet catcher is disabled, you can confirm whether
this NE received the SIP message through this function.
� Tracing information is tremendous if tracing conditions are
unfixed, because too many useless information are included,
therefore, useful information provision is a tremendous
project.
� The NM tool may lose some information when obtaining infor-
mation from the foreground, which disturbs and misguide the
fault location.
Application scope of signaling tracing is limited.

2.3 Tracing Failure Observation

Failure Failure trace returns the error code from the failure trigger point,
Observation and reports the error codes of the failure point.
Application
Failure observation is a list, the upper layer where the fault takes
place. This list shows the interior flow which is point to line.

4 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 2 Fault Location Approaches

Failure In the Trace Managment interface of the Local Maintennace

Observation Terminal, select Signaltrace > CSCF > Flow > ALL FLOW
Operations TRACE, and condition setting interface is shown in Figure 2, the
items with (n) are compulsory parameters.

FIGURE 2 OPERATION INTERFACE

Failure observation supports the following approaches:

� Based on PUI
� Based on access IP address
� Based on SIP method
Application Scope Failure observation is the best approach in call test and basic flow
test, which can find the fault point directly.

2.4 Flow Trace

Flow Trace Flow trace traces the processing flows of all modules based on
Application the message flow, which includes messages interaction between
modules, function invoke interface, status transition information,
timer setting information and detailed debugging information.
Application Scope All flow trace is intended for carriers in big traffic. To decrease im-
pact on performance, the trace code stream is incomplete without
decoding operations.
In daily test, all flow trace can also trace the processing flow of
basic flow, and judges whether there is fault.

2.4.1 All Flow Trace

Flow Trace Flow trace traces the processing flows of all modules based on
Application the message flow, which includes messages interaction between
modules, function invoke interface, status transition information,
timer setting information and detailed debugging information.
Application Scope All flow trace is intended for carriers in big traffic. To decrease im-
pact on performance, the trace code stream is incomplete without
decoding operations.
In daily test, all flow trace can also trace the processing flow of
basic flow, and judges whether there is fault.

Confidential and Proprietary Information of ZTE CORPORATION 5

ZXUN CSCF Training Material

Introduction to All There are 3 all flow trace objects:

Flow Trace
� PUI-based trace includes full match, left match, right match
and etc.
� IP-based match: signaling IP address
� SIP-based match: initial request of the flow
Above can be combined at will, and obtained information can be re-
ceived/send messages, interaction between SIP and service mes-
sage, interaction between Diameter and service message.

2.4.2 Interior Flow Trace

Objects of interior flow trace are insiders, including R&D person-

nel, service personnel. This function provides approaches to locate
detailed problems.
Apart from three conditions of all flow trace, the configurable trace
conditions include other trace sub-conditions.
� Traffic type
� Report level
� Process type
Above sub-conditions can be set separately, and reported infor-
mation must satisfy set conditions.
On-site service personnel need to feed back error information by
recommended interior flow trace, through which R&D personnel
can locate the problems.

2.5 Fault Code Portability Function

This function refers to carrying error codes in SIP signaling.
When a NE has an error actively, X-ZTE-Cause header field will be
inserted in fault response message.
Other NEs will forward this fault response.
This field carries host name and fault code.
It's able to judge the point where fault happens through the host
name, and analyze preliminary fault cause.
For instance: X-ZTE-Cause: CSCF-6503. pcscf.ims.com.cn

6 Confidential and Proprietary Information of ZTE CORPORATION

Chapter 3 Fault Location Steps
After you have completed this chapter, you will know:
>> Common Steps
>> Fault Information Feedback

3.1 Common Steps

� Fix the fault NE through packet catching in the entire network.
� View alarm/notification, troubleshoot inefficient resource, Di-
ameter broken link and hardware fault.
� Analyze fault observation.
� Analyze interior flow trace.

3.2 Fault Information Feedback

On-site reflected information includes:
� Fault description, including phenomenon and version.
� Packet catching in the entire network. (compulsory)
� Fault observation (compulsory)
� All flow trace (optional), small traffic and trace all are recom-
mended.

Confidential and Proprietary Information of ZTE CORPORATION 7

ZXUN CSCF Training Material

This page is intentionally blank.

8 Confidential and Proprietary Information of ZTE CORPORATION

Chapter 4 Common Faults Instance
After you have completed this chapter, you will know:
>> Common Faults Inside NEs
>> Common Interworking Fault

4.1 Common Faults Inside NEs

4.1.1 S-CSCF Replies with 403 when
Registering Authentication

Phenomenon Terminal registers in the IMS network, S-CSCF replies with 401
message and challenges the terminal, and then terminal makes
a response upon receipt of this challenge, after receives second
registration message, S-CSCF replies with 403 message.
Possible Reasons � Enter a wrong password on the terminal, or the password is
inconsistent with that of number allocation of HSS.
� HSS contract algorithm is wrong.
� Domain name+domain selector+registration method
on S-CSCF should be configured to this domain+HSS host
name+home domain name. (domain name needs not to be
configured in case of multiple domains)
Countermeasures � Reallocate the number on HSS.
� Use other terminals for registration and troubleshoot whether
it is terminal fault.
� Check the configured data, it's unnecessary to configure the
home domain name on S-CSCF.

4.1.2 Fail to Forward Messages During

Callee 's Session

Phenomenon Establish a call normally, and update/reinvite/refer messages from

caller can be forwarded, while update/reinvite/refer from callee
cannot be forwarded.
Possible Reasons This error is route configuration error.
Usually, route analysis configuration lack of entry route selector
covers URI and TEL analysis.
� Request in outgoing session: route selector (exit)+analyzed
digit+approach

Confidential and Proprietary Information of ZTE CORPORATION 9

ZXUN CSCF Training Material

� Request in incoming session: route selector (entry)+analyzed

digit+approach
Countermeasures Add related configuration of digit analysis, such as route selector,
URI and TEL analysis.

4.1.3 Registration on the Terminal is

Cancelled Automatically

Phenomenon The terminal registers in the IMS network, and then registration is
cancelled automatically.
Possible Reasons � Based on IFC, S-CSCF triggers third-party registration, if AS
does not send successful response when subscribing session-
terminated, S-CSCF will send notify message to cancel the
successfully registered subscriber.
� An identical PUI logs in to other PC, and S-CSCF triggers sub-
scription-cancellation and send notify message to the regis-
tered subscriber.
Countermeasures � Make sure that AS is available, or has subscribed session-con-
tinue.
� Make sure that an identical number has not logged in any other
places.

4.1.4 Respond the Call with 404

Message

Phenomenon When called I-CSCF seeks for S-CSCF, or S-CSCF seeks for AS,
the request message cannot be forwarded in this NE, and this NE
responds with 404 message.
Possible Reasons Can not find the route.
Countermeasures Check data configuration, and ensure correctness of URI/TEL/IP
digit analysis.

4.1.5 Caller Responds with 403

Message

Phenomenon After successful registration, the subscriber makes a call and sends
INVITE message to P-CSCF, and caller responds with 403 message
which results in call failure.
Possible Reasons In most cases, the 403 message refers to authentication failure,
which means P-CSCF regards this caller to be illegal, the possible
reasons are as follows:
� SBC access carries no PPI head field.
� UNI access: The subscriber registers on IP1 and makes a call
on IP2.

10 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 4 Common Faults Instance

� UNI access: The subscriber registers on port 1 and makes a

call on port 2.
Countermeasures � Make sure that there is no error on the terminal.
� Make sure that the access property configuration of the entry
policy on P-CSCF is correct.

4.1.6 S-CSCF Fails to Trigger AS

Phenomenon Based on different services, S-CSCF needs to trigger AS, but ac-
tually AS is not triggered.
Possible Reasons � HSS subscriber has registered improperly, for example, header
field and code stream are unmatched, or the regular expression
is incorrect.
� Route configuration of the AS host name is improper, and fail
to find the outgoing route set.
� Packet catching mapping error, there is no code stream on the
packet catching, but actually the code stream is existing.
Countermeasures � Check the subscription on HSS, and re-subscribe if necessary.
� Check the route configuration.

4.1.7 Fail to Send the SAR Message on

S-CSCF

Phenomenon Request the registration on S-CSCF when a subscriber is register-

ing, and find there is no SAR (Server Assignment Request) mes-
sage.
Possible Reasons � Check whether the link configuration on the NM is proper, in-
cluding IP addresses, host name, domain name and port num-
bers of local end and opposite end.
� Check whether INIT and INIT_ACK of SCTPare normal.
� Check whether the interacted CER/CEA message are normal.
� Check the route configuration through failure observation.
Countermeasures Troubleshoot the problem according to possible reasons.

4.1.8 Respond with 500 Message when

Registering on S-CSCF

Phenomenon In the newly-established exchange, after data configuration,

S-CSCF always responds to registration request with 500 mes-
sage.
Possible Reasons � As seen from failure observation that subscriber's data upgrade
is failed.

Confidential and Proprietary Information of ZTE CORPORATION 11

ZXUN CSCF Training Material

� Delivery command for all tables is sync all and the command
for variable tables is sync chg.. Model value configuration
sends model value data to related table through the sync
modval command. Model value configuration supports per-
centage and rollback, and index cannot be place with data
transmission.
Countermeasures Run the sync modval command.

4.1.9 CSCF Responds with 503

Message

Phenomenon When performing subscriber registration or the callee has not reg-
istered the service, P-CSCF and S-CSCF will responds with the 503
message.
Possible Reasons In two following cases, S-CSCF will responds with the 503 mes-
sage.
� If there is retry-after header field in the 503 message, then
this subscriber will be locked, which means this subscriber is
in use.
� If there is no retry-after header field in the 503 message, it
means that S-CSCF fails to send MAR (Mutimedia Auth Re-
quest)/SARServer Assignment Requestmessage to HSS.
Countermeasures � Change another number or wait for a while, such as 4 mins.
� Check the route analysis configuration queried by HSS on
S-CSCF, it's recommended to include HSS host name in URI
analysis.

4.1.10 CSCF Responds with 504

Message

Phenomenon CSCF may respond with the 504 message for subscriber's regis-
tration or calling.
Possible Reasons Opposite NE has no response or feed back 3XX/480 response,
while P-CSCF has no other optional next hop NE.
Countermeasures � Check whether the link is proper.
� Check why the opposite NE has no response.

12 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 4 Common Faults Instance

4.2 Common Interworking Fault

4.2.1 P-CSCF Responds with 403
Message when SBC Calls P-CSCF

Phenomenon After sucessful registration, the subscriber makes a call, and then
P-CSCF responds with 403 message directly.
Possible Reasons � PPI head field is not inserted in SBC.
� PPI header field inserted in SBC is wrong.
Countermeasures Check the configurations on SBC and add PPI header field.

4.2.2 Calling Number Display Error

when SBC Makes a Call

Phenomenon After successful registration, the subscriber makes a call, for ex-
ample, A calls B, P-CSCF forwards the INVITE message to S-CSCF,
in which the PAI header field of calling number is other subscriber
rather than subscriber A.
Possible Reasons It's necessary to configure Interface Type to Share IP in the
entry policy of P-CSCF of SBC access, however, it can be configured
to UNI on P-CSCF.
Countermeasures Modify the access properties of corresponding entry policy of the
SBC address on P-CSCF.

4.2.3 Call Fails to Reach MGCF

Phenomenon Called number is the subscriber of CS domain, but the INVITE mes-
sage has not reached MGCF.
Possible Reasons � Link between S-CSCF and MGCF is interrupted.
� Route configuration on S-CSCF is wrong, the route must be
outgoing to MGCF directly.
Countermeasures Check MGCF link and route configurations on S-CSCF.

4.2.4 PSS Fails to Send Prack

Phenomenon PSS (ZXUN SSS) sends the INVITE message actively to MGCF pass-
ing through S-CSCF, and then MGCF returns 180 response to PSS,
finally PSS sends Prack failure.
Possible Reasons � Act as proxy, S-CSCF adds no record-route, 180 turns back to
PSS through via, and PSS sends Prack through record-route.

Confidential and Proprietary Information of ZTE CORPORATION 13

ZXUN CSCF Training Material

� Fail to send Prack because of no direct link between PSS and

MGCF.
Countermeasures Configuration steps for adding record-route are as follows:
1. Enter the command: SHOW TESTCFG;
2. Perform or operation by the queried value and 0x8000, and
obtain the operation result.
3. Enter SET TESTCFG:TEST=operation result; (such as SET
TESTCFG:TEST=32768;

4.2.5 Media Information Loss

Phenomenon The INVITE message in CS reaches UP10 through MGCF triggering,

UP10 replies do-not-disturb tone 183 to S-CSCF, and when S-CSCF
forwards it to I-CSCF, there is no media information.
Possible Reasons � UO10 modifies and deletes the media message in 183.
� CSCF only check offer/answer models of SDP rather than de-
tailed SDP parameters. That's why SDP issues outnumbers AS
issues like PSS and UP10 issues.
Countermeasures Check AS processing.

14 Confidential and Proprietary Information of ZTE CORPORATION

 Glossary

AS
Application Server
BRS
BeaR Subsystem
CEA
Capabilities Exchange Answer
CER
Capabilities Exchange Request
CS
Circuit Switched
HSS
Home Subscriber Server
I-CSCF
Interrogating-Call Session Control Function
IFC
Initial Filter Criteria
INIT
INITiation
MGCF
MediaGateway Control Function
P-CSCF
Proxy-Call Session Control Function
PPI
PDH Physical Interface
PSS
PSTN/ISDN Simulation Services
PUI
Public User Identity
S-CSCF
Serving-Call Session Control Function
SCTP
Stream Control Transmission Protocol
SDP
Service Data Point
SIP
Session Initiation Protocol
SSS
Supplementary Service System
TP
Traffic Processing Module
TR
Transceiver

Confidential and Proprietary Information of ZTE CORPORATION 15

ZXUN CSCF Training Material

TU
Tributary Unit
UNI
User Network Interface
URI
Uniform Resource Identifiers

16 Confidential and Proprietary Information of ZTE CORPORATION