ZXUN CG Debugging Guide

Objectives

 Upon completing the course, you will be able to:

 Grasp charging server debugging
 Grasp charging client debugging
 Grasp interface debugging
 Grasp service debugging
Contents

 Charging Server Debugging

 Charging Client Debugging
 Interface Debugging
 Service Debugging
Starting Service Programs
 Three processes must be started on the charging
server, which are as follows:
 nms: communication support process
 sctpfsm: SCTP handling process
 s10spu: ZXUN CG service handling process
 Run the following commands on the Terminal
interface:
 $nms start
 $s10spu start
 $sctpfsm start
Checking Process Running Status
 1. Log in to the charging server as the omc user. Right-click on the
desktop of the server, and select Tools > Terminal from popup menu
to enter the Terminal window
Checking Process Running Status
 2. Run the following command:
 $ps –ef|grep s10
 Appearance of nms, sctpfsm or s10spu means there
are legacy processes.
Modifying s10cfg.ini
 1. Enter the following path:
 $cd /ZXHOME/config

 2. Run the following command:

 $vi s10cfg.ini

 3. Enter s10cfg.ini editing status and change the following according to

actual needs:
 Locate the following line: PostOffice=131


Set the office number of the actual charging server to 131.
 Locate the following line: LOCALMODULE=130


Set the module number of the actual charging server to 130.
 Locate the following line: LocalIP=172.16.0.230


Set the IP address of the actual charging server to
172.16.0.230.
Adding CDR Source Nodes
 Adding Link Information
 1. Enter the following path.

$cd /export/home/omc/zxhome/config
 2. Run the following command:

$vi s10cfg.ini
 3. Edit the s10cfg.ini file by adding the following line:

Remote2= Name(Node2),Post(71),Node(1),Ip(129.0.31.70),
connect(c)
Adding CDR Source Nodes
Adding CDR Source Nodes
 4. Run the following
command to stop the nms
process:

$nms stop
 5. Restart the nms process.
Two circumstances may
occur:

If ZXUN CG service
programs are started by
s10dog, nms will be
automatically restarted by
s10dog after it has been
stopped.

Otherwise, run the $nms
start command to start nms.
Adding CDR Source Nodes
 Configuring Routes
 1. To add the route manually, run the following
command:

# route add [host|net] destination [gateway]

 2. To create a permanent static route, write the above

route configuration information into the
/etc/rc2.d/S99route file. The route will become
automatically effective when system starts.
Adding CDR Source Nodes
 Checking Link Status to the MP
 1. Run the following command:

$s10see
 2. On the s10see--main window , click Browse > System
Information to display the connection status of each link and node
 3. Check the following items in the Communication pane.

Check if State of IP address of the new MP is Connected.

Check if State of IP address of the charging server is Connected.

Check if State of IP address of the BD is Connected.

Check if listening is configured on MSS Communication System,

check if State of IP address of the charging client is Listening.
Adding CDR Source Nodes
 Stopping Service Programs
 1. On the s10dog window, click Close to stop s10dog
(Omit this step if s10dog is not running).
 2. Run the following commands to stop nms and s10spu

$nms stop

$s10spu stop

After running these commands, ZXUN CG service processing
programs will automatically exit.:
Adding CDR Source Nodes
 Stopping Legacy Service Programs
 1. To clear the active programs, run the following
command:

$pkill program name

program name includes: nms, sctpfsm and s10spu.
 2. Run the following commands:

$./omcdel
Contents

 Charging Server Debugging

 Charging Client Debugging
 Interface Debugging
 Service Debugging
Opening MSS Communication System Window

 1. When the charging client is started, right-click the icon on

Windows taskbar and then select Setup from the popup menu. The
Input Password dialog box pops up
Opening MSS Communication System Window

 2. On the Input Password dialog box, type the password andthen

click Ok to enter the ZTE Communication System window
Setting the Local Node Position
 1. On the ZTE Communication System window, click the Link Setup
tab.
 2. On the Link Setup page, click to enter the Set Position
dialog box
Setting the Local Node Position
Setting the Local Node Position
 3. Set the parameters and then click Ok.
 4. Click OK.
Setting the Local Node Role
 1. On the ZTE Communication System window, click the
Link Setup tab.
 2. On the Link Setup tab page, click the button to
enter the Set Role dialog box
Setting the Local Node Role
 3. Select Client and enter 5057 in the Port field.
 4. Click Ok to enter the Message dialog box

 5. Click OK to set whether to reboot Winnttcp immediately.

 6. Click OK.
Adding Access Nodes to Charging Server
 1. On the ZTE Communication System window, click the
Link Setup tab.
 2. On the Link Setup tab page, click the button to
enter the New Node dialog box
Adding Access Nodes to Charging Server
Checking Link Information
 On Windows taskbar, click the icon to enter the ZTE
Communication System window. Check link state in the Link State
tab page.
 2. Click the Link Information tab to enter the Link
Information tab page
 3. Check link state and then click the Link Setup tab to
enter the Link Setup tab page
Deleting Access Nodes
 1. On the ZTE Communication System window, click the
Link Setup tab.
 2. Select the node to be deleted and then click the
button to enter the Message dialog box
 3. Click OK to delete the access node or click Cancel to
discard the deletion.
Exiting MSS Communication System
 1. Right-click the icon in the lower right corner from
Windows taskbar and select Exit from the popup menu

 2. Enter the password in the popped up Input Password

dialog box
 3. Click OK to exit Winnttcp.
Contents

 Charging Server Debugging

 Charging Client Debugging
 Interface Debugging
 Service Debugging
Debugging CDR Collection Interface
 1. On Windows taskbar, click Start > Programs > Bill Client >CDR
Management Client to enter the Login SPU dialog box
Debugging CDR Collection Interface
 2. Enter login information and then click Ok. The Charging
System CDR Manager window appears
Debugging CDR Collection Interface
 3. In the left pane of Charging System CDR Manager, double click on
Normal CDR or click the icon before the Normal CDR to view different
CDR channels on the SPU
 4. Select the channel you want to view. The right pane will display the
file list in this channel.
 5. In the right pane, double-click a CDR file to check if its content is
correct.
CDR Output Interface Debugging
 Creating an Account to Receive CDRs
 Configuring a Route to BD
 Under the directory /etc/rc2.d on the Charging Server,

add a file S99router, with the following content:


route add default 10.41.34.254

 Testing FTP Login

 1. On Windows taskbar, click Start > Run.
 2. On the Run dialog box, type cmd and then press Enter.
 3. Type ftp 10.41.80.194 (change this IP address to the IP address
of the charging server), and press Enter
CDR Output Interface Debugging

 4. Enter zte as the user name, and the password of the user to receive
CDRs as the password. Login is complete when the screen displays
Logged in successfully.
CDR Output Interface Debugging
 Checking CDR Prefix
 Ask the BD to take away CDRs under the
export/home/bill/remote directory and check if the prefix
of CDRs has changed from B to C.
Contents

 Charging Server Debugging

 Charging Client Debugging
 Interface Debugging
 Service Debugging
CDR Correlation
 After the system passes interface testing, open
the CDR Manager to check if there is any CDR
under the correlation channel.
CDR Management
 The management of CDR includes:
 Saving CDRs
 Deleting CDRs
 Restoring CDRs
 Downloading CDRs to the local system