Maintenance Experience, Issue 55 (GSM Products) Change Tone Element PDF

Preface
In pursuit of the idea First-class service, Customer service, and in

Maintenance Experience
order to make more profit and provide better service for our customers,
Editorial Committee
we have edited Maintenance Experience (ISSUE 55), which includes
the troubleshooting of mobile and network part and some maintenance
Director: Zhou Susu
cases.
With the wide application of GSM products of ZTE, routine
Deputy Director: Chen Jianzhou
maintenance of the products, a major job of the technical maintenance
personnel of operators, has become more and more important. This Editor-in-Chief: Yang Cheng
issue, which collects articles written by GSM technical personnel of the
Editors:
customer service department of ZTE, describes practical cases and
Jiang Guobing, Wang Yaping, Ba Zexue, Gu Yu,
corresponding solutions that are often met during the commissioning
Zhang Shoukui, Wu Feng, Yuan Yufeng, Lei Kun,
and maintenance procedure. We hope it will be helpful to your routine
Tang Hongxuan, Chen Huachun, Ding Guixiang,
maintenance work.
Tian Jinhua, Zhu Wensheng, Ling Changwen,
For more articles of maintenance experience and related technical
Zhang Zhongdong, Liu Xianmin, Zhang Mingjing,
materials, please log on ZTE technical support website http://support.zte. Wang Zhaozheng, Chen Taiming, Wang Haidong,
com.cn Chen Le, Wang Tiancheng, Zheng Hongliang,
If you have any requirement, question, or suggestion, please feel free Wang Tao
to contact us. Your attention and support are greatly appreciated.
Technical Senior Editors:
Zhang Niantao, Wu Yongjun, Luo Liming, Ren Jimin
Executive Editors:
Li Fenglian, Xu Shanshan
Newsroom
Maintenance Experience Editorial Committee

ZTE Corporation Address: ZTE Plaza, Keji Road South, Hi-Tech
August, 2007 Industrial Park, Nanshan District,
Shenzhen, P.R.China
Postal code: 518057
Contact: Song Chunping
Email: doc@zte.com.cn
Tel: +86-755-26770600,26771195
Fax: +86-755-26772236
Contents
Mobile Subdivision
BSC Maintenance
Saving Error when Configuring Half-rate 3
Inter-BSC Handover Failure after Upgrading the Ericsson MSC 3
Communication Failure after Peripheral MP Switchover 4
A interface Traffic 5
Precaution for EDGE Downloading Testing 5
Silent Call 6
Network Cable from MP to GIU is Shielded 7
How to Modify the IP Address of OMP 8
BTS Maintenance
Site Commissioning Failure caused by Transmission Fault 9
PA Over-heated Alarm in OB06 10
New Site Fails to Receive Calls 10
BTS Fails to Start up because Transmission Connector is Loosely Welded 11
BSC could not Start up Normally 12
OMCR Maintenance
Help at OMCR Client Unable to be Displayed 13
Upper-Level NM Unable to Collect Performance Data 13
Radio Feature Checking Tool Usage 14
Login Failure due to Incorrectly Modifying Properties of Folders under /etc Directory 15
Not Receiving Returned Message from Server when Logging in to Client 15
BSC Rack View Unable to be Displayed Normally 16
OMCR Client Login Failure 16
CBC Data Importing Procedure 17
How to Move ORACLE Data Files to Other Paths 18
August 2007 Issue 55 Mobile Subdivision BSC Maintenance
Contents
Network Subdivision
Fault Instance
The Inter-office Trunks Could not be Occupied 19
High Call Failure Rate in a Certain BSC 20
Clock Aging on the SYCK Board 21
Errors in R2 Incoming CLIP 21
The Subscriber Database Was Interrupted 24
The IMSI Number Section in the Two DB Nodes of the User Is Repeated 25
There Are Echoes When Dialing the Call 26
Special Document
ZXG10-MSS Call Loss Analysis 28
Experience Exchangee
Changing the Tone Play Sequence 31
Configuration Method for Preventing the PPS Subscriber Data Call Service from Being Triggered to IN 32
FAQ
How to Implement the Active/Standby Network Card? 34
The Standby MP Gives an Alarm, but It Works Normally in Fact 35
The Network Board Cant Start When the Left MP Is the Active 35
Why the Active Indicator and the Standby Indicator of the Active MP Flash Every Several Seconds? 36
How to Locate the Fault that the Board Works Abnormally? 37
The Board Powers down during the MP Switching Because of the Inconsistent PP Version 37
The DTI Board Fails to be Powered On 38
Why Is Switching to the Standby DSN Board Unsuccessful After Unplugging the Active One? 38
Why Is the Fault Indicator on the MPPP Board on? 39
How to Recover the Inter-Module Communication of a Single Peripheral Module Immediately? 39
During Querying the Status of One Board, the System Prompts that the Communication is Interrupted 40
Mobile Subdivision BSC Maintenance
www.zte.com.cn
Saving Error when

Configuring Half-rate
Zhong Zhenfeng, ZTE Corporation
Symptom of MPMP and MPPP. Totally 118 time

After modifying and configuring half-rate, it fails slots are used for speech service, and
to save. each carrier occupies two HW timeslots
(one HW time slot supports 4 service time
Troubleshooting slots). So when configuring HR, consider
When configuring half-rate, the HW time slot the number of carriers and calculate the
of BIU is needed. The HW time slot of BIU is left available HW time slots. For example,
limited although the E1 timeslot at Abis interface is 100 carriers are configured on the left BIU,
enough. they occupy 200 HW time slots and there
The capacity analysis of BIU (take the left BIU are 118*2=236 HW time slots, hence the
as an example): one BIU on the left has eight HW time slots left are 236-200=36. One
8Mbps HW, the time slot configuration is described HW time slot support four service time slot,
as follows: 0~117 are used for speech service, so 36 idle HW time slots could configure
118~127 are used for the HDLC communication 144 auxiliary time slots.
Inter-BSC Handover Failure after

Upgrading the Ericsson MSC
Wu Yongsheng, ZTE Corporation
Symptom Troubleshooting
The Ericsson MSC in an office in Yun Nan According to GSM 08.08specification,
fails to switch over with ZTE GSM product after d u r i n g c r o s s M S C s w i t c h o v e r, t h e
upgrading. The symptom is: the Huawei micro-BTS switching message is allowed to exclude
under Ericsson MSC is able to switchover to the the MNC or MCC and report to LAC and
ZTE micro-BTS under Ericsson MSC, but the ZTE CI. According to the specification, the
micro-BTS fails to switchover to the Huawi micro- switching request message from ZTE BSC
BTS under Ericsson MSC. does not carry MNC or MCC. Ericsson
GSM Products
MSC requires the switching request must be carried,which leads to the fault. Users
from BSC must include MNC and MCC. could modify the switchover message format after
MSC side and BSC side do not have parameter CELLIDCFG=1 in ZXG10.CFG to avoid
the regulation whether MNC and MCC such kind of fault.
Communication Failure after

Peripheral MP Switchover
Qiao Linfeng, ZTE Corporation
Symptom and background. It is found that the data of active/

An MP on the left side of a peripheral standby MP and OMCR are consistent, so the
module is active MP. But it fails to originate problem is not caused by the data inconsistency.
call or answer the call after the active 2. Exchange the physical location of the two
MP is switched to the right side, despite MPs
that status indicators for the MP indicates After exchanging, it is found that the right MP
the right MP is running normally; when still fails to perform communication while the left
it is switched back to left, it resumes the one is normal, which indicates that the software
normal communication. and hardware of MP are both normal.
3. Exchange the connection from MP to COMM
Troubleshooting According to the connection of MP and the
The connection and data configuration analysis of the calling flow direction on the rack,
are normal to MSC, since the active MP the problem may occur in the connection from
performs the communication normally MP to COMM backplane, so exchange the two
when it is on the left. The problem may lie connection cables to solve the problem. Conclusion
in the data or the hardware of the MP on could be drawn that the connection between
the right, troubleshoot as follows: original right MP and COMM backplane is broken
1. Compare the ZDB data of active MP or the interface is faulty.
and OMCR 4. If the problem still exists after the above
The ZDB data is supposed to be troubleshooting, the problem may lie in the
checked first because the problem may be backplane in control layer or BIF layer; replace the
caused by inconsistent data between MP backplane to solve the problem.
www.zte.com.cn
A interface Traffic
Wu Jianwen, ZTE Corporation
Symptom Table 1. FacchCallInd is an 8-bit bitmap

The traffic of a BSC is found extremely huge on
Location Meaning
site; the equipment is running in full configuration.
1: FACCH setup process is allowed in emergency call
And statistics show that the traffic in busy hour is bit1
0: FACCH setup process is not allowed in emergency call
over the maximum number of service time slots 1: FACCH setup process is allowed in acknowledgement
configured at A interface. The reason is unknown. paging
bit2
0: FACCH setup process is not allowed in acknowledgement
Troubleshooting paging
The statistics for the communication is 1: FACCH setup process is allowed in originating call
bit3
0: FACCH setup process is not allowed in originating call
found including the traffic of FACCH during the
1: FACCH setup process is allowed in call re-establishment
inspection. Field specification of FACCH access is bit4
0: FACCH setup process is not allowed in call re-establishment
as follows:
bit5 ~ bit8 Reserved, is always 0
When there is no available SDCCH in the cell
as an MS attempts to access the network, BSC
could allocate TCH according to the actual According to the symptoms, the
situation, namely FACCH call setup process. technician cancels all other FACCH
Whether and how to use FACCH call setup access except emergency call. Traffic
process are subject to FacchCallInd, as shown is back to normal and the problem is
in table 1. solved.
Precaution for EDGE

Downloading Testing
Wu Jianwen, ZTE Corporation
Symptom deteriorated, such situation is even worse.

Network registration failure or disconnection
occurs occasionally when mobile phone dialing Troubleshooting
while it is running normally during the EDGE Coding scheme of EDGE is MCS,
downloading test, especially in the case that which integrates the error tolerance
human mobility and radio environment is further protection system into the coding scheme.
GSM Products
MCS modulation coding scheme contains scheme, the modulation and demodulation will
9 subsets, MCS1 ~ MCS9. Among be undermined significantly in complicated and
them, MCS1 to MCS4 employ Gaussian deteriorated radio environment (i-e. poor C/I),
Minimum Shift Keying (GMSK) modulation, access will be affected as well.
the error-tolerance protection ability is In the EDGE property of radio resource
strong but data throughput is relatively low management, select the option that enable the
as a result. MCS5 to MCS9 adopt 8-PSK dynamic change of EGPRS MS default coding to
modulation, data throughput is relatively improve the error-tolerance and guarantee the
larger. When adopting higher modulation normal access of MS.
Silent Call
Wang Ke, ZTE Corporation
Symptom Troubleshooting
Connection with MGW is completed, in 1. Initially suppose the problem occurs in the
the dialing test afterward, the circumstance carrier of the base station. After locking channel
is that there is no ring back tone at the test, it is found that such fault will also happen
calling party but the phone rings at the after dialing for certain times, but it does not occur
called party in every 5 or 6 calls, and it is continuously in a certain channel, so the carriers of
mute if connected. the base station are normal.
2. Perform self-loop test on BSC. After self-loop
test on A-interface, MTP board flashes persistently,
callers could hear their own voices after being
connected. Upon above, it could be concluded that
the problem results from the board of BSC.
3. Compare the Data with switch side, all
signaling is found normal. Perform dialing test on
certain time slot, such problem still occurs. So it
could be concluded that it is not because of CIC
pair error.
4. At last, check MGW data. After overall
inspection on all data, the third SMP board of
MGW, which is only used to convey the signaling,
is set to convey both service and signaling. Change
the board to signaling only and the problem will be
solved.
www.zte.com.cn
Network Cable from

MP to GIU is Shielded
Cai Xiaodan, ZTE Corporation
Symptom interface on backplane. The network cable

UDP communication link between BRP board between the involved peripheral module and
and MP broken alarm occurs frequently at the GIU HMS is connected to the top pot on the
background of OMCR client alarm interface and backplane, which is very close. Therefore,
the alarm lasts shortly. The alarm objects are all the dropping off power cable is suspected
related with the same peripheral module. to interfere with the network cable.
4. Adjust the network cable to another
Troubleshooting network cable, the alarm disappears and
1. Only one peripheral module is involved in the services resume being stable.
problem, so the software of the board is normal. 5. To further confirm whether the power
2. Check the hardware, switching over relevant cable causes the interference or the HMS
active/standby board (HMS/PUC/DSNI) makes no network interface fault, adjust the network
difference. The situation is improved a little bit by cable back to the original position, and re-
switching over active/standby MP, but the alarm bundle the power cable according to the
still appears quite often. specification, alarm disappears and the
3. Check the hardware of BSC foreground, it service is normal. So it is concluded that
is found that the power cable drops off the cabling the fault is due to the interference by the
trough on GIU backplane, and falls to the network power cable with the network cable.
GSM Products
How to Modify the IP

Address of OMP
Chen Qi, ZTE Corporation
Symptom address set here is only used for originating link

In multiple-iBSC environment or special setup at background, which will not affect the
circumstances, IP address of OMP should OMP_IP configuration in foreground/background
be set up. database.
3 . The above two steps establish the link
Troubleshooting between background and foreground first. After
1. When starting up OMP, the network link setup, the OMP IP address of foreground/
parameter of OMP could be set up at background could be modified on the BSC global
serial port, including the IP address of resource at background. After modifying, perform
OMP and OMC. Afterward, the startup increment synchronization to the foreground.
could continue, and OMP starts to use the 4. Save all the settings at foreground. It will
set IP address. But after restarting, OMP take 2 or 3 minutes and will telnet to OMP, switch
will get IP configuration from database and to the the path cd /DOC0/DATA1, use command
the address set at serial port will be invalid 11 to check dbver.zdb file. If the file has been
as a result (Database table is r-global.zdb, generated and the version is the latest, it indicates
field is OMP_IP). that the synchronization has been accomplished (no
2 . Background could set the IP dbver.zdb file during synchronization).
address of the foreground on BSC 5. Reboot the OMP again; it will start with the
m a n a g e d e l e m e n t ; h o wever, the IP new IP address.
Mobile Subdivision BTS Maintenance
www.zte.com.cn
Site Commissioning Failure

caused by Transmission Fault
Qiao Linfeng, ZTE Corporation
Symptom BSC directly and the problem is solved.

Add a new BTS (V2) site under BSC (V2.95),
which is connected in chain with an existing site Fault Analysis
running stably. After power ON, CMM is normal, but Above problem is due to the issue of
all carriers report LAPD alarm. All carriers panel transmission quality that leads to high
displays downloading software, however, it does bit error rate and consequently results in
not accomplish for about one hour. software version downloading failure.
Troubleshooting
1. Because it is a new site, the transmission
issue is suspected first. Loop back from the site
to BSC, the corresponding LED for TIC board
indicates normal and no PCM alarm is reported;
loop back from the upper layer site to BSC, the
transmission is normal and the upper layer site
working normally.
2. Trace the OAM signaling, it could be found
that normally after 4 data segments are sent to
BTS from BSC; BTS is required to reply a Data
Segment ACK. But in this case, the site only
receives one acknowledgement message after
sending 6 or 7 data segments, such occurrence is
frequent and leads to continuous downloading. The
carriers fail to start up for long.
3. No abnormity is found when checking
the software in database and primary software.
Furthermore, all upper layer sites work normally,
so the problem may occur during the transmission
from the current site to its upper layer site or the
OAM time slot of the site in transmission.
4. Change an E1 transmission connected with
GSM Products
August 2007 Issue 55 Mobile Subdivision BTS Maintenance
PA Over-heated Alarm in OB06

Wu Lei, ZTE Corporation
Symptom disappear.
The site reports that PA overheated 2. If the carrier with alarm is BCCH, it is
alarm appears in an OB06 base station suggested to switch BCCH another carrier without
in the traffic peak period randomly. Then PA alarm, and observe if the alarm will disappear.
the corresponding carrier will be blocked 3. If the alarm still exists after replacing BCCH,
automatically. and the BCCH alarm shifts with the changing of
BCCH, which means PA overheated alarm in BCCH
Troubleshooting is due to the excessive load when traffic is high.
1. Find if there is any regularity in the Users can detach BCCH in different cells as much
carriers that have PA alarm, for example, as possible for heat dissipation. At the same time
replace the TRX of the carrier in which check if the BTS heat dissipation system works
the alarm appears frequently or with high normally to make sure TRX works in working
possibility and observe if the alarm will temperature. In this way, the alarm will disappear.
New Site Fails to Receive Calls

Gao Zhicun, ZTE Corporation
Symptom
It is found the new site fails to receive the
incoming call in routine test, announcing cannot be
reached at the moment.
Troubleshooting
1. Problem still exists after restarting the MS.
2. Check the radio parameters and the software
version, no abnormity is found and no equipment
has alarm.
3. Through signaling tracing, it is found that
no paging message is delivered from upper layer
Figure 1. Calling Procedure of the Called Party

(MSC) to BSC, which leads to paging failure to MS.
10 Maintenance Experience
www.zte.com.cn
4. Tracing on the switch, it is found that there is that the above method has low
no paging message in the signaling tracing result. maneuverability. So another method is
According to the specification, figure 1 shows call employed on site: change the LAC No.
procedure of the called party. It could be observed Distinguish ZTE BSC with the previous
from the figure that the first paging message Huawei BSC. The problem is solved after
is delivered from switch to BSS side, and the setting LAC No. as 113.
following task is processed and forwarded by BSS.
5. Replace Huawei base station with new base Fault Analysis
station. The LAC of the previous base station Generally, the problem, which is
(Huawei) is 71. At present ZTE BSC uses the same related to calling procedure, could be
LAC as the previous BSC, so the signaling points analyzed according to the procedure in the
of multi-BSC need to be connected on switch specification step by step, compared with
otherwise the paging message will be delivered to the actual message flow. CI of the calling
the first BSC, which lead to failing to paging the party is a vital parameter and the LAC at
users under other BSC. the called party needs special concern as
6. The customer service engineers conclude well.
BTS Fails to Start up because

Transmission Connector is
Loosely Welded
Jiao Qiming, ZTE Corporation
Symptom cabinet top is damaged. In case BTS self-

Some BTS are disconnected in Jin Zhou area loop is normal, SYN indicator should be
in Liao Ning. Observing the alarm management off. But after the self-loop on site, the
interface at OMCR background reveals that BTS SYN indicator is found still ON. So it is
operation and maintenance in the background concluded that the E1 cable on cabinet top
alarm is disconnected, SYN of CMM board turns or CMM board is faulty.
red and the BTS could not start up normally. 2. Change the CMM board, but the
problem still exists.
Troubleshooting 3. Checking the E1 line on the cabinet
1. First E1 is judged to be faulty. Check the top, it is found that the E1 connector on
transmission circuit carefully. Self-loop the BSC the cabinet top is loosely welded, resulting
from DDF rack of BTS and self-loop the BTS at the in the startup failure of BTS. The problem
same time to confirm if the E1 cable at base station is solved after being re-welded.
GSM Products 11
August 2007 Issue 55 Mobile Subdivision BTS Maintenance
BSC could not Start up Normally

Wang Yanjin, ZTE Corporation
Symptom position with the standby CMM board to observe if

Base station is unable to start up the BTS recover.
normally (CMM restart repeatedly), 3 . Check the data. Compare the ZDB file
TIC indicator of BSC is normal, but the at background and foreground to check if there
signaling of the site could not be traced is the information of this site. The data is found
successfully. inconsistent at foreground and background, which
is responsible for the signaling tracing failure.
Troubleshooting 4 . The problem is solved after the data at
1. Check if the transmission is normal background is made consistent with the data at
by self-loop. Note that only reception foreground.
is checked at BSC side, if the cable for
transmission is faulty, some times it could Fault Analysis
not be found out by checking the TIC Generally, signaling tracing failure indicates
indicator. that the transmission is faulty, but this case is
2. If the transmission is normal, reset exceptional. Therefore, for such kind of problem, it is
the CMM board, plug/unplug or change suggested to check the consistency of ZDB files.
Mobile Subdivision OMCR Maintenance
www.zte.com.cn
Help at OMCR Client

Unable to be Displayed
Jin Kangfei, ZTE Corporation
Symptom variable OMCDOC setting is correct.

When clicking HELP directory, system prompts Modify it if it is incorrect.
location failure, and the help can not be opened. 2. If the problem still exists, check
However, all other functions at the client can be whether Adobe Reader, the tool for reading
performed normally. PDF document, has been installed in the
computer where OMCR client is installed.
Troubleshooting If not, install the tool.
1 . R i g h t - c l i c k o n M y C o m p u t e r, s e l e c t 3. After performing the above steps,
Properties. In the pop-up System Properties run HELP directory again, the problem is
dialog, select Advanced tab and click Environment resolved.
variables button to check whether the environment
Upper-Level NM Unable to
Collect Performance Data
Chen Qi, ZTE Corporation
Symptom share dmemory("shared pool

In a certain office server, the upper-level NM 2 . F o r O R A - 0 4 0 3 1 e r r o r, t h e
fails to collect performance data. troubleshooting method recommended by
ORACLE is as follows:
Troubleshooting If the shared pool is out of memory, either
1. It is found that the performance basic table use the DBMS_SHARED_POOL package
contains performance data but the intermediate to pin large packages, reduce your use of
table contains no data. After checking diff log file, shared memory, or increase the amount
the following errors are found: of available shared memory by increasing
06:05:04DIFORA:ERROR SQL CODE:- the value of the initialization parameters
4031ORA-04031:unable to all ocate 4096 bytes of SHARED_POOL_RESERVED_SIZE and
GSM Products 13
August 2007 Issue 55 Mobile Subdivision OMCR Maintenance
SHARED_POOL_SIZE. If the large pool be equal to SHARED_POOL_SIZE. Restart

is out of memory, increase the initialization ORACLE and run PMDR command to regenerate
parameter LARGE_POOL_SIZE. the intermediate table. Run perl/export/home/
3. After checking initomc.ora file, it is omc/tools/unidb/pnms.pl-m2007032104 to
found that SHARED_POOL_SIZE setting recollect upper-level NM performance data. The
is normal but LARGE_POOL_SIZE is set system runs normally.
too small. Since the upper limit of memory
pool is set by LARGE_POOL_SIZE setting, Fault Analysis
LARGE_POOL_SIZE should be larger In parameter settings in initomc.ora file,
than or equal to SHARED_POOL_SIZE. LARGE_POOL_SIZE should be larger than or
4. Modify LARGE_POOL_SIZE to equal to all other POOL_SIZE parameters.
Radio Feature
Checking Tool Usage
Yang Yong, ZTE Corporation
Symptom CI=1000-1004 (input the planned CI range)

In current OMCR versions, Radio NCC=0-3 (input the planned NCC)
Resource Management supports radio FreqBand=0 (input the frequency band. 0: GSM
feature checking to facilitate checking 900; 1: EGSM 900; 2: 1800M)
whether configured data are within the FreqScope=96-122 (input the frequency
planned range. This section introduces range)
how to perform radio feature checking. SameFreqVerify=1 (whether to check co-
frequency)
Troubleshooting NeighourFreqVerify=1 (whether to check
1. Edit rrcheck.ini file under adjacent-frequency)
$OMCHOME/conf directory on the server, 2. After modifying the above parameters, exit
modify the following parameters: the client and log in again to enter Radio Resource
CHECK=1 (modify to be 1) Management.
MCC=460 (input MCC of the local 3 . Enter Validity Check, open Radio Feature
network) Check to select items to be checked.
MNC=02 (input MNC of the local 4. Right-click on BSC, select Radio Feature
network) Check. The system performs check according to
LAC=34161,34162,34163 (input LAC parameter setting in the rrcheck.ini file. The system
value of the BSC; can be multiple gives error prompt if there is any parameter not
values separated by coma ) satisfying the setting.
www.zte.com.cn
Login Failure due to Incorrectly

Modifying Properties of Folders
under /etc Directory
Wang Jianxing, ZTE Corporation
Symptom incorrectly modifying properties of folders

When modifying omc user directory properties under /etc directory. If the property of pam.
in a certain experimental environment, the property conf file under /etc directory is not 664, it will
of a folder under /etc directory is modified to be cause users unable to login to the server.
777 by mistake. It causes that no user can login to
the server after the system restarts. Solution
Insert the system CD into CD drive.
Troubleshooting Start system and run bootcdroms to enter
alled in the computer where OMCR After single user mode. Modify the property of
referring to relevant materials and other similar pam.conf file to be 664 and restart server.
cases, it is found that the problem is caused by The problem is resolved.
Not Receiving Returned

Message from Server when
Logging in to Client
Wang Yanjin, ZTE Corporation
Symptom to be F drive, causing OMCR client login

When logging in to OMCR client, the system failure.
prompts not receiving returned message from Modify the tracepath parameter in
server, and the login fails. fmwsf.ini file to be an existent path. The
problem is resolved.
Troubleshooting
After checking, it is found that in the alarm Fault Analysis
box setting file fmwsf.ini, a nonexistent path is set Parameter settings in the alarm box
for the tracepath parameter. For example, there setting file should be correct, otherwise, it
is no F drive in the machine but tracepath is set will influence OMCR client login.
GSM Products 15
BSC Rack View Unable to be

Displayed Normally
Fang Guangzhi, ZTE Corporation
Symptom The default resolution of OMCR rack view is

In OMCR client, the BSC rack view can 800x600, and the maximum resolution supported
not be displayed normally. is 1024x768. Thus if the resolution is adjusted to be
larger than 1024x768, for example, 1600x800, the
Troubleshooting BSC rack view in OMCR client can not be displayed
With the increase of base stations, normally.
users require to see more base stations Therefore, users must adjust the resolution
in the interface and thus often adjust within appropriate range so that the BSC rack view
resolution. can be displayed normally.
OMCR Client Login Failure

Jiao Qiang, ZTE Corporation
Symptom login fails either, with the same system prompt.

After BSC (V2.95) upgrade is 3. After checking ftpuser name and password
completed on a certain China Unicom site, in lmfcfg.ini file, it is found that all are correct.
the client login fails and system prompts 4. After checking the client syscfg.ini file, it
that remote server does not return login is found that client printing log is disabled in the
message. upgraded configuration file. However, a directory
saving client printing log is created as TracePath
Troubleshooting = d:/client/log. Checking the client directory
1. After checking, it is found that at client, it is found that there is no such log
the owner of /export/home/omc/tmp/ftp directory.
directory on OMCR server is ftpuser. 5. Create the directory d:/client/log. Login to the
2. After modifying the owner to be omc, client again and the problem is resolved.
www.zte.com.cn
CBC Data Importing Procedure

Yang Yong, ZTE Corporation
Symptom tempstep number;

After commissioning the built-in CBC function, cur number;
the server should be reconfigured. In addition to alterstr varchar2(100);
importing basic configuration data, alarm data, and begin
performance data to the new server, CBC data cur := dbms_sql.open_cursor;
should also be imported to the new server.
/*protection*/
Troubleshooting select max(smsid) into maxid from
In OMCR (V2.97), there are cbcimp and cbcexp b_message;
scripts. Run cbcexp script to export CBC data of the if (maxid is null) then
old server and run cbcimp script to import CBC data return;
to the new server. end if;
In OMCR (V2.95), there are no above select seq_smsid.nextval into seqid
scripts. Write tables B_Channel, B_area, B_BTS, from dual;
B_message, b_messageop and b_messageinit, seqid := seqid-1;
which are required by CBC data, into exparam.dat if (seqid >= maxid) then
file. In this way, CBC data can be exported when alterstr := 'alter sequence seq_smsid
executing cmexp script, and then can be imported to increment by -1';
the new server when executing cmimp script. After dbms_sql.parse(cur,alterstr,
CBC data import is completed, execute altercbcseq. dbms_sql.v7);
sql script. The script content is as follows: select seq_smsid.nextval into maxid
prompt *********************************************** from dual;
*********************************** alterstr := 'alter sequence seq_smsid
prompt * FUNCTION : Modify the value of increment by 1';
SEQUENCE in B_MESSAGE table to be the dbms_sql.parse(cur,alterstr,
maximum value of SMSID in the table dbms_sql.v7);
prompt * dbms_output.put_line('SEQUENCE
prompt * AUTHOR : ZHOUZIPU O F TA B L E B _ M E S S A G E N O T
prompt * CREATEDATE: 2006/8/31 CHANGED!');
prompt * dbms_sql.close_cursor(cur);
prompt * UPDATEDATE: return;
prompt *********************************************** end if;
*************************************** /*protection*/
set serveroutput on;
tempstep := maxid-seqid;
declare alterstr := 'alter sequence seq_smsid
maxid number; increment by '||to_char(tempstep);
seqid number; d b m s _ s q l . p a r s e ( c u r, a l t e r s t r,
GSM Products 17
dbms_sql.v7); alterstr := 'alter sequence seq_smsid increment

d b m s _ o u t p u t . p u t _ l i n e ( ' A LT E R by 1';
SEQUENCE STEP TO MAX SMSID OF dbms_sql.parse(cur,alterstr, dbms_sql.v7);
TABLE B_MESSAGE:'||TO_CHAR(tempste dbms_output.put_line('ALTER SEQUENCE
p)||'!'); STEP TO 1!');
dbms_sql.close_cursor(cur);
select seq_smsid.nextval into maxid end;
from dual; /
dbms_output.put_line('SEQUENCE
INCREASE TO MAX SMSID OF TABLE quit;
B_MESSAGE'||TO_CHAR(MAXID)||'!');
How to Move ORACLE

Data Files to Other Paths
Jiao Qiang, ZTE Corporation
Symptom be implemented through disconnecting network

There is no space in the disk partition cables.
where data files locate, causing upper- (3) Make table space of the data file to be
level NM unable to receive performance moved offline. Take the CBC data file for example,
data and OMCR running abnormally. run the following command:
In this case, some data files should be sqlplus sys/oracle ALTER TABLESPACE
moved to other partitions. "CBC_SPACE" OFFLINE NORMAL
(4) Run the following command to move the
Troubleshooting data file to new directory:
1. Run the following command to query mv /oracleapp/u02/cbc01.dbf /export/home/
data file information: sqlplus sys/oracle oradat
select name, bytes from v$datafile (5) Run the following command to modify the
2. Decide which file should be moved data file direction:
to /export/home/oradat according to data ALTER DATABASE RENAME FILE '/
file size. oracleapp/u02/cbc01.dbf' TO '/export/home/oradat/
3. After deciding which data file to be cbc01.dbf'
moved, perform the following steps: (6) Run the following command to make the
(1) Run the following command to table space online again:
terminate omcr: A LT E R TA B L E S PA C E " C B C _ S PA C E "
omckill -kill 1 ONLINE
(2) Disconnect with other database (7) Restart OMCR, connect network cable, and
such as the upper-level NM, which can the operation is completed.
www.zte.com.cn
The Inter-office Trunks

Could not be Occupied
Huang Wuxiang, ZTE Corporation
Symptom congestion, signal pass or no tone in two

After adding modules for the MSC, and directions.
checking the new added trunks from the MSC
to the PSTN and the BSC through the dynamic Solution
management, it was found that all the trunks were The engineer modified the data
in the IDLE status. The new added trunks from configuration according to the following
the MSC to the PSTN and the BSC could not be request:
normally occupied all the time. 1. For the trunk to the PSTN side,
the engineer deleted the new added
Analysis route group configuration in the Trunk
1. For the trunk to the PSTN, when checking Configuration > Trunk Route Chain, and
the related configuration, the engineer found that configured the new added route to the
the new added trunk route was configured as the existing PSTN trunk route group.
new route group and directed to the same PSTN 2. For the trunk to the BSC side, the
office as the original route group. The new trunk engineer modified the PCM number of the
route group was added to the trunk route chain. MSC side to make it consistent with that of
There is precedence among the route groups the BSC side.
corresponding to an outgoing route chain. When 3. After modifying the data
the first route group is not fully occupied or configuration and synchronizing the data,
interrupted, the system will preferentially select the the engineer found that the trunk was
first route group. So, the new added route group normally occupied when performing the
could not be occupied all the time. All the routes dialing test.
in the same route group share the load, so all the

routes in the same route group can be occupied
averagely.
2. For the trunk to the BSC, there was no
outgoing route configuration, so it was required to
find the reason from other aspects. When asking
the maintainer of the BSC side to cooperate in the
check, it was found that the PCM numbers of both
ends were not consistent, which further caused
that the CIC numbers of both ends were also
inconsistent. So, when the new added trunk was
occupied, it would cause faults, such as the call
GSM Products 19
August 2007 Issue 55 Network Subdivision Fault Instance
High Call Failure

Rate in a Certain BSC
Chen Yunlong, ZTE Corporation
Symptom had been modified at the BSC side recently, and

It was hard for subscribers in a certain each cell status was normal. By checking the
BSC to make or answer a call. About only status of every link at the MSC side and the BSC
2 calls from 10 calls were successfully. side simultaneously, the engineer found that the
The called party under this BSC links at the MSC side were normal without related
received the spice mobile switched off alarms. However, several links at the BSC side
message, while the calling party received were in unstable status.
the Error in Connection message during The engineer opened the MSC performance
an outgoing call. statistics to check the traffic send and received
traffic statistical data of the NO.7 link. He/she
Troubleshooting found that the traffic send values of several links
After performing the signaling tracing were almost 0. At the same time, the carrier
analysis, the engineer found that the MSC informed that these links had been evenly allocated
constantly sent the paging request message to different STB boards at the MSC side the day
to the BSC, but it did not receive any paging before, but not all links had been tested after the
response message. There are the following modification.
two possibilities according to the analysis:
There were problems at the BSC side; Solution
The signaling link was faulty. The engineer deactivated these links, and then
The engineer confirmed that no data activated them again at the MSC side. He/she
opened the signaling tracing to trace every link.
At this moment, the links became normal and the
subscribers under this BSC could originate and
receive a call normally.
Summary
Before adding, deleting or modifying the
link configuration information, it is necessary to
deactivate this link first and then open the signaling
tracing to confirm it is in idle status.
Activate the link after the modification. Execute
a dial-up test on each link, and open the signaling
tracing to confirm whether the link is in working status.
In addition, it is necessary to cooperate with the BSC
side to ensure both ends of the link are normal.
www.zte.com.cn
Clock Aging on the SYCK Board

Chen Yunlong, ZTE Corporation
Symptom all the clocks of the system circularly

After the system in one office ran for a period of extracted the clock from each other. This
time, a clock aging alarm occurred on one SYCK phenomenon continued for a long time,
board of the HLR, displaying the reason that the which caused central frequency deviation
digital-analog conversion exceeds the range. After on each module of each office.
several days, the same alarm occurred on the
SYCK board of modules 3 and 5 of the MSC, and Solution
the SYCK board of the SC. Since the system did not extract the
clock from external offices, it was required
Analysis to manually set the clock mode of the
After checking the clock systems of both central SYCK board of the CSM module of the
modules and peripheral modules of the MSC, it MSC to free mode. In this way, the CSM
was found that the clock modes of all the SYCK module provided the clock reference, the
boards were in tracing status. However, from the peripheral modules traced and extracted
connection cables on the backplane of module the clock from the CSM module, and
2 of the MSC, it was known that the clock was other offices extracted the clock from
not extracted from external offices. In fact, the the peripheral modules. When the clock
SYCK board of module 2 connected to the CFBI reference was successfully caught, the
board, and the SYCK boards of modules 3, 4 and SYCK board automatically ran in the trace
5 only connected to the FBI board. In this case, mode. The alarm was cleared.
Errors in R2 Incoming CLIP

Sun Jingrun, ZTE Corporation
Symptom where the MSC A office found the called

The inter-office signaling between the MSC A number home to itself, the calling number
and the call center adopted the R2 signaling, and was not displayed on the terminal of the
the incoming/outgoing call could be put through. called party at the MSC A side.
However, the following two problems occurred in 2. After the trunk indicator of the MSC
Calling Line Identification Presentation (CLIP): A was modified, the calling number was
1. For an incoming call from the call center, displayed on the terminal of the called
GSM Products 21
party at the MSC A side, but NDC90 (90 is the

NDC of the MSC A) was added at the beginning of
this number.
Analysis
1. During the incoming call, the CAS message
traced at the MSC A side is shown in Figure 1.
After the forward register signal sent the called
number 90980005, the MSC A did not send the A5
signal to request the calling number. Therefore, the
call loss message 1032= CasOpWtOpDnTimeOut
appeared.
2. After the trunk indicator of the MSC A was
modified, the calling number obtained from in the
CAS message at the MSC A side was 80018,
but the calling number displayed on the MS was
9080018 (the NDC 90 of the MSC A was added
at the beginning of the calling number). The CAS
message traced is shown in Figure 2.
The MSC A possibly added 90 at the
Figure 1. Cas Message at the Msc a Side (1)
beginning of the number 80018, for the calling
number attribute is the subscriber number.
After checking the security variable of the MSC
A, the engineer found that the value of Display
Mode of Calling Number was 1. The MSC A added
90 at the beginning of the subscriber number
80018, and the number became in the valid
national number format.
Solution
1. For the fault of no calling number displayed,
the solution is described as follows:
(1) In the trunk indicator of the call center, check
the (Incoming) Caller Number Available check
box and uncheck the (Malicious call) incoming A6
signal followed closely with KA signal check box.
(2) During analyzing the local office number
segment 90 in the incoming trunk selector of the
call center, check the Sending A6 signal after the
8th digit of the incoming number flow check box.
After the analysis, the minimum number length of
Figure 2. Cas Message at the Msc a Side (2) the local office number segment 90 is eight digits
www.zte.com.cn
and the maximum number length is eight digits.

And then execute a dial-up test. During an
incoming call from the call center, the MSC A sends
the A5 signal to request the calling number 80018
in the backward register signal.
2. For the fault of adding 90 at the beginning
of the calling number, there are following two
solutions:
Solution 1: modify the Display Mode of Calling
Number security variable of MSC A to 0. After
modification, the local fixed number will be
displayed in the format of subscriber numbers,
which only affects the display of calling number Figure 3. Adding the Calling Number Selector 201
on the MS.
Solution 2: convert the attribute of the calling
number into the valid national format in the
incoming trunk group of the fixed exchange B.
In this case, the calling number in the CDR will
be affected, and other traffic incoming from this
trunk group will be affected as well.
The second method is adopted according to the
actual conditions on site. The detailed procedures
are as follows:
Add a new calling number selector 201, as
Figure 4. 800 Number Section Analysis
shown in Figure 3.
Analyze the calling section 800 in the entrance
14 of the local analyzer, as shown in Figure 4.
Modify the trunk selector of the MSC1 and the
Call center, and then add 201 for the Origin Digit
Preprocess DAS, as shown in Figure 5.
Figure 5. Trunk Selector
GSM Products 23
The Subscriber Database

Was Interrupted
Symptom links of 129, 170, 140 and 141, they were all
A subscriber database interruption normal. There were lots of c:\zxg10\diarypro.exe
alarm was generated in one office, file loss error messages on the 170 dual-computer
and no subscriber information could be server. The cluster dual-computer resources were
successfully queried in the HLR agent. suspended. After restarting the dual-computer
1. After performing signaling tracing cluster, the switchover test was normal, and the
on the MSC, it was found that the HLR all communication with 129 was normal.
returned Map Error messages whose In the HLR dynamic management, the engineer
contents are system fault when the MSC switched over back to the 170 active database.
sent the sent route info message to the After that, the subscriber information could be
HLR. successfully queried in the agent, but the HLR
2. After performing signaling tracing still returned Map Error messages. After a while,
on the HLR and opening the failure the system was switched back to the standby
observation, it was found that there were database of 129. After several times of switchover
lots of system fault and connect to and restarting the server 129, the engineer
database error messages. canceled the automatic switchover option in the
HLR dynamic management, but the problem still
Analysis existed.
In the dynamic management, it was
found that the system had been switched Solution
over to the standby database HLRDB170 After restarting the two MAP processors of the
of 129. After checking the communication HLR, the problem was solved.
www.zte.com.cn
The IMSI Number Section in the

Two DB Nodes of the User
is Repeated
Chen Yu, ZTE Corporation
Symptom is required to back up the database before

During the local maintenance, it is found that the operation and it is also required to
the IMSI sections in the 170 DB node and the 173 recheck them after the operation.
DB node of the user are repeated, but the service delete from baseinfo where
is not affected. imsi>=0x413082100000001F and
imsi<=0x413082100007500F
Analysis go
Through the data analysis, it is found that the
repeated continuous IMSI sections in these two delete from camelinfo where
database are 413082100000001~4130821000075 imsi>=0x413082100000001F and
00 and there are 7500 in total. The 7500 IMSIs in imsi<=0x413082100007500F
the 173 node are redundancy data and they should go
be deleted.
After checking the corresponding log, it is found delete from convert_info where
that the repeated number sections are caused by imsi>=0x413082100000001F and
the number adding failure of the carriers operator. imsi<=0x413082100007500F
As shown in Figure 1, the carriers maintainer go
adds the IMSI section in the 173 node, imports
these 7500 authentication data from the d e l e t e f r o m d n w h e r e
background. Then he/she deletes the IMSI section imsi>=0x413082100000001F and
from the 173 node, changes the DB node as 170 imsi<=0x413082100007500F
node and then re-imports these 7500 authentication go
data. Because there are still some related data
left on the 173 node, it causes the IMSI section of
some table repeated and wastes the space of the
173 node.
Solution
These repeated IMSI data in the related table
of the 173 node can be deleted.
The following script can delete all the data in
the related table of the redundancy IMSI section. It Figure 1. Database Node Configuration
GSM Products 25
delete from dynamicinfo where delete from scaddress where

imsi>=0x413082100000001F and imsi>=0x413082100000001F and
imsi<=0x413082100007500F imsi<=0x413082100007500F
go go
delete from ggsnlist where delete from sscfsubaddr where

imsi<=0x413082100007500F imsi<=0x413082100007500F
go go
delete from o_trace where delete from sscuginfo where

imsi<=0x413082100007500F imsi<=0x413082100007500F
go go
delete from pdpinfo where d e l e t e f r o m s s d a t a w h e r e

imsi<=0x413082100007500F imsi<=0x413082100007500F
go go
delete from rszi where d e l e t e f r o m s s i n f o w h e r e

imsi<=0x413082100007500F imsi<=0x413082100007500F
go go
There Are Echoes When

Dialing the Call
Symptom Analysis
Between the two MSCs of the two When checking the trunk configuration of the
provinces SHIRAZ and FASA in Iran, the MSC, the engineer finds that the Echo suppressor
echo occurs when all the subscribers included in the trunk circuit group indicator, the ICM
originate or receive the local fixed-line need echo suppressor and the OTG need echo
phone. suppressor in the outgoing route basic attribute
www.zte.com.cn
are all checked. The version of the DTEC is on the DTEC board are as follows:
DTECG060401. 1~2 jumper the echo control is in the
When tracing the signaling in this MSC, the incoming trunk side and it is used as a
engineer finds that all Echo control device indicator trunk form the mobile network side to
in the IAM message sent are all in the included the fixed-line side.
status and all Echo control device indicator in the 2~3 jumper the echo control is in the
ACM message sent are in the incoming half echo outgoing trunk side and it is used as
control device included status. When the local is a trunk from the fixed-line side to the
the called party, all Echo control device indicator in mobile network side.
the signaling sent by the fixed-line are in the not In fact, all the jumpers on the DTEC
included status. are on the 2~3 jumper. The problem is
It is doubtful that there is something wrong with solved after the changing all the jumpers
the echo control of the fixed-line side, but the fixed- on the DTEC board to 1~2 jumper.
line has the auto-control function. When performing
the dialing test for the fixed-line distance phone of Summary
the fixed-line switcher, the engineer doesnt find Through the fault phenomenon, it
any echo. When performing the signaling tracing, is found that the echo control function
the engineer finds that the signaling is same to the also can be implemented in the
signaling described above, so it is known that the signaling tracing even if the software
echo control of the fixed-line side is all right. set is correct. If the hardware setting is
wrong, the phenomenon reported by the
Solution signaling tracing is only a misleading
Check the jumper of the DTEC board. The appearance and that cant be the
descriptions of the jumper X23~X30 and X33~X40 complete judgment.
GSM Products 27
August 2007 Issue 55 Network Subdivision Special Document
ZXG10-MSS Call Loss Analysis

The call loss observation in the signaling of the A-interface, it was found that some
operating and maintenance system of MSCs sent back the CREF message after they
ZXG10-MSS is an important maintenance received the BSC connection request (CR). The
function. Most service faults will be detailed commands were as follows:
reported to the call loss observation timely. LI:62
The call loss observation and analysis SIO:C3
is an important method of locating the SIF:
fault, and it is indispensable for the daily 89 22 00 8E 22 00 0B 01 5B 2A 04 02 02 06 04
maintenance. This topic introduces 43 89 22 FE 04 04 43 8E 22 FE 0F 21 00 1F 57
several examples that adopt the call loss 05 08 00 64 F0 00 71 D4 9C EA 17 12 05 08 70
observation to analyze and locate the 64 F0 00 FF FE 33 08 49 06 00 66 42 08 32 86
faults. 00
1. When the service observation CR----Connection request
was used to monitor the running status Mandatory parameter:
in the MSC/VLR office, it was found Source local reference:91.42.4
that the mobile management (MM) part Protocol type: type 2
of the module 8 reported many invalid Called address:
parameter call losses. When the No.7 Signaling point code(14):04_51_01
signaling was used to tracing the SCCP *SSN: FE
www.zte.com.cn
*select the route according to the DPC+SSN in engineer found that the call completion
the MTP ratio of the module 9 was less than before.
Optional parameter: When querying the traffic statistics of
Calling address: the trunk group, the ZTE engineer also
Signaling point code:(14):04_51_06 found that the call completion ratio of
*SSN: FE the incoming call to one office direction
*Select the route according to the DPC+SSN in declined greatly.
the MTP After tracing the ISUP signaling of
LI:21 this office direction and ordering the
SIO:C3 traced signaling according to the CIC,
SIF: the ZTE engineer found that the local
8E 22 00 89 22 00 0A 03 5B 2A 04 03 01 office returned the CFL when the opposite
03 04 office occupied the circuit of one PCM.
43 89 22 FE 00 When it was checked with the dynamic
CREF----Connection rejected management, it was found that the
Mandatory parameter: circuit of the PCM was on the blocking
Destination local reference:91.42.4 status because the frame was out of
Reasons for rejection: SCCP subscriber synchronism. So why did the opposite
rejects o ff i c e o c c u p y t h e s e c i r c u i t s ? A f t e r
Optional parameter: contacting the maintainer to confirm the
Called address: circuit status, the ZTE engineer knew
Signaling point code(14):04_51_01 that the local maintainer found that there
*SSN: FE was something wrong with the PCM
*select the route according to the transmission before and then they self-
DPC+SSN in the MTP looped these circuits when checking them,
When checking the CR sent by the BSC, so the switch of the opposite office thought
the engineer found that the italics were the cell the circuits were on the normal status and
numbers carried by the service request. When tried to occupy them. After the opposite
querying the configuration table of the MSC cell, office blocked the circuit, the no available
the ZTE engineer did not find out the cell. digital circuit call loss disappeared and
After contacting the maintainers of the BSC the call completion ratio recovered to
side and analyzing the problem with them, the ZTE normal.
engineer confirmed that the BSC data configuration 3. When a MPM module was added in
was wrong when the BS was adjusted, which the MSC/VLR office, it was found that the
further caused the location update failure. The subscribers under this module could not
problem was solved after the BSC configuration successfully call some mobile phones in
was modified. other areas. When the call loss observation
2. When the service observation was used to was used, it was found that the MAP
monitor the running status in the MSC/VLR office, of the newly added module frequently
it was found that the ISUP of the module 9 reported reported the route optimization is not
many no available digital trunk circuit call losses. allowed call loss. When using the MAP
When querying the basic traffic statistics, the ZTE signaling tracing ,the ZTE engineer found
GSM Products 29
August 2007 Issue 55 Network Subdivision Special Document
the orflag=1 instead of orflag=0 in the load sharing mode. So, it was doubted that the
route request message sendrouteinfo_req 146 intelligent service subsystem of the GMSC
sent by the module, which meant the route on the H1 was not configured, which filtered the
optimization was supported. This was the message instead of transmitting it to the GMSC.
reason that caused the HLR returning the When checking the data, the H1 maintainer found
route optimization is not allowed errors that 146 subsystem of the GMSC on the H1 was
and further caused the failure of some not configured in fact. After the H1 added the
calls. Whether the route optimization configuration data, there was no No NET call loss
was supported was determined by the in the call loss observation of the GMSC and the
corresponding parameters in the security call completion ratio was enhanced.
management. It is required to point out that the call loss in the
After the checking, it was found that call loss observation does not mean that there is
the route optimization was supported by something wrong with the equipment of the local
the security variable in the newly added office or other offices. There are many reasons
module, which caused the problem. The why the call loss is reported when the service is
problem was solved after the security not completed normally. For example, the ringing
variable was modified. release early is also a kind of call loss. When
4. One mobile gateway office reported some doubtful phenomenon is found in the service
that the incoming call completion ratio was observation, it is required to analyze and confirm
very low all the time. whether it is a normal phenomenon. For example,
When the call loss observation was the maintainer of one GMSC is often worried about
used, it was found that the TUP reported that the CAMEL service is failed call loss often
many No NET call losses. After the called occurs, and then performs the dialing test for the
numbers were checked, it was found numbers suffering from call loss and queries the
that all of them were prepaid intelligence status of these subscribers from the SCP. After
subscribers. When using the MAP tracing that, the maintainer finds out that all these numbers
signaling, the ZTE engineer found that are overdue or not enabled for other reasons, so
some signaling sent from the GMSC to the the doubt is eliminated.
local SCP could not receive the response, In general, the call loss observation plays a
which further caused the call failure. All very important role in locating the emergency fault
the signaling sent from the GMSC to the of the system, daily maintaining the equipment and
SCP were transmitted by the HSTP1 optimizing the system. It is required to check the
and the HSTP2. When tracing the SCCP call loss when there are service faults. And it is also
signaling, the ZTE engineer found that required to observe the call loss during the daily
the subsystems of the calling party in the maintenance. Be cautious when the system reports
messages sent from the H1 to the GMSC some unusual call loss. Combine the tools, such
were all HLR instead of SCP. as signaling tracing, performance statistics and
After the checking, it was known that dynamic management to locate the fault, perform
the signaling from the SCP to the GMSC the aimed dialing test, analyze the reason of the
was sent to the H1 and the H2 in the call loss and then take measures.
Network Subdivision Eperience Exchange
www.zte.com.cn
Changing
the Tone Play
Sequence
The old tone play sequence was English,

Native language. The customer requires that the Figure 1. Tone Element Editing--tc_en_msctpbusywait
tone play sequence should be changed to Native
language, English. The following takes the call
waiting tone as an example to introduce how to
change the tone play sequence.
1. View the corresponding tone elements of
different service tones. In general, English and the
native language are configured on different tone
elements during the office commissioning. For
example, two tone elements of the call waiting tone
are TC_EN_MSCTPBusyWait (as shown in Figure
1) and TC_MSCTPBusyWait (as shown in Figure
2). The corresponding tones on the tone board are
Tone110.wav and Tone130.wav. The names of tone
Figure 2. Tone Element Editing--tc_msctpbusywait
files are named tonexxx.wav in a unified manner,
where xxx is the number of the tone segment
that is the address label. The Tone Element Code
begins from 1, while the Tone Board Address label
begins from 0.
2. The tone play aims at different tone services,
determining and arranging the tone play sequence
of the tone files on the tone board according to
the software (the related table of the MP). For
example, the corresponding Tone Code of the call
waiting tone (as shown in Figure 3) in ICP Editing
is TONE_MSCTPBusyWait.
3. View the corresponding tone element of the
tone code. In this example, TONE_MSCTPBusyWait Figure 3. Icp Editing--tone_msctpbusywait
GSM Products 31
August 2007 Issue 55 Network Subdivision Eperience Exchange
contains TC_EN_MSCTPBusyWait and and then Tone130.wav.

TC_MSCTPBusyWait tone elements, as 4. Change the play sequence of the tone
shown in Figure 4. In this way, Tone110. elements in the tone editing. As shown in Figure
wav on the tone board will be played first, 4, select the tone whose play sequence is to be
changed, and click Modify. The corresponding tone
element is displayed in the list of the bottom right
of the window. Delete TC_EN_MSCTPBusyWait in
the first place from the list, and then add it again. It
ranks second. And then click Modify again. Adjust
a tone, and then synchronize the table to perform
the testing verification.
NOTE: For most offices having PPS
subscribers, the post-paid SIM card should be
used in the testing verification because some tones
are played at the IN side. After the test is passed,
change the play sequences of the corresponding
tone elements of other tones.
Figure 4. Basic Tone Editing
Configuration Method for

Preventing the PPS Subscriber
Data Call Service from
Being Triggered to IN
The data call service is enabled service to the intelligent network in the subscription
in Office A. Only some specified PPS information of these specified PPS subscribers.
subscribers can subscribe the onsite data In this way, the basic call and basic call service
call service. However, the carrier requires restriction in the case of no balance left of these
that these specified PPS subscribers can PPS subscribers will not be affected.
implement the data call even if they have 1. On the HLR agent, select Subscriber
no balance left. > Subscriber Intelligent Service to query the
To implement this requirement, use CAMEL subscription information of specified PPS
the method of not triggering the data call subscribers, as shown in Figure 1.
www.zte.com.cn
2. In Figure 1, select the TDP check box and

the Basic services check box in turn. Click the
Set button to pop up the Trigger criteria of basic
services dialog box, as shown in Figure 2.
3. On the upper right area of this dialog box,
select the speech service check box, and then
select the Telephone radio button, which means
that only the basic call is triggered to the intelligent
network. If the service item in the lower two areas
is selected, the corresponding service will not be
triggered to the intelligent network. At most five
items can be selected.
For example, the voice call service is set not to Figure 1. Camel Subscriber Information
be triggered to the intelligent network except the

basic call. The Voice group call service check box
on the lower left area should be selected. That is to
say, the basic call will be triggered to the intelligent
network normally, while such non-basic-call voice
call services as the data call service will not be
triggered to the intelligent network. In this way, the
requirement of the carrier is satisfied.
Figure 2. Trigger Criteria of Basic Services
GSM Products 33
August 2007 Issue 55 Network Subdivision FAQ
How to Implement the Active/

Standby Network Card?
Chen Yubin, ZTE Corporation
Answer network cards

1. Description On the MP main board, check the chips
At present, all MPs are configured DM9008F and FL1020 of the network card.
with two network cards. In fact, only one Each network card should be configured with
network card is used and there is only one these two chips. Therefore, two network cards
network cable. But in the dual-network should be configured with two pairs of these
system, both the active network card and chips. If there is only one pair of chips, only one
the standby network card are required. network card and can be used, and the dual
These two network cards are connected network cannot be implemented.
to two HUBs respectively. By logic, these Locations of MP dual network cards
two network cards share one IP. If one is For the socket sketch of the MP backplane, see
broken, the other will replace it. At present, Figure 1
all MP versions support the active/standby Note: One end of the MP network cable is
network card scheme. The details are as RJ45, and the other end is the 38 plug (22~29
follows. area in Figure 13). When there is only one network
2. Implementation of MP Active/ cable, the 38 plug is connected to 25 (a, b) and
Standby Network Card 26 (a, b), and the locations of the other network
Check whether the MP has two card are 23 (a, b) and 24 (a, b).
3. Method of making the network cable
For the corresponding relation between the 3
8 plug and the RJ45 connection line of the network
cable, see Table 1.
Make the network cables of the dual network
cards and of the MP according to the above
methods: one 38 plug leads out two RJ45 plugs,
which will be connected to two HUBs (these two
HUBs should be interconnected). During making
Table 1. Corresponding Relation Between the

38 Plug and the Rj45 Connection Line of the
Network Cable
RJ45 Network card 1 Network card 2
1 (RD+) 26a 24a
2 (RD-) 26b 24b
3 (TD+) 25a 23a
Figure 1. Socket Sketch of the Mp
6 (TD-) 25b 23b
Backplane
www.zte.com.cn
network cables, it is required to open the 38 plug, the communication becomes normal,
and connect the second network cable according which means the switching of the active/
to the above relation. standby network card is normal. These
4. Dual-network Test two network cards adopt the dual seizure
In the local area network, use another computer working mode. The one that successfully
to continuously ping the IP of the MP. After pulling connected first is the active, and the other
out the active network cable, it is found that the is the standby. There is no absolute active/
communication is interrupted. After 15 seconds, standby relation between them.
The Standby MP Gives an Alarm,

but It Works Normally in Fact
Question of the standby MP to the active MP

When the left MP is active, both the active MP through the alarm interface card on the
and the standby MP work normally. When the right main board, and then the active MP
MP is the active, the standby MP gives an alarm, but sends it to the background. So there is
it works normally in fact. How to solve this problem? something wrong with the alarm interface
of the left MP. Replace the MP to solve the
Answer problem.
The backplane bus sends the alarm message
The Network Board Cant Start

When the Left MP Is the Active
Question board cannot start up, and some DSNI

The switch works normally when the right MP is the boards have the communication interruption
active; but when the left MP is the active, the network alarms. How to solve this problem?
GSM Products 35
August 2007 Issue 55 Network Subdivision FAQ
Answer and the communication between the network board

In order to solve this problem, it is and the MPPP is abnormal.
required to know the working principles If the problem still exists after the cable and the
of the left and the right MPs. Both the left MPPP are replaced, it means there is something
and the right MPs have a set of data bus wrong with the MPPP communication port, that is,
connecting the board of the control layer. the slot. Because the switch works normally when
If there is something wrong with one set the right MP is the active, it means that the slot is
of the data bus, the communication fault OK. So it is sure that there is something wrong with
between this MP and the peripheral board the data bus connecting the left MP and the MPPP.
will occur. When the left MP is the active, some DSNI
When the left MP is the active, the boards have the communication interruption alarm,
network board cannot start, which means which means there is something wrong with the
that the communication between the communication between the MONI board and the
network board and the MP is interrupted. MP. After unplugging the MONI, the network board
The network board communicates with works normally, which means the MONI board
the MP through the MPPP, which further affects the data bus connecting the left MP and the
means that the communication between MPPP.
the network board and the MPPP is If the problem still exists after the MONI board
interrupted, or that the communication is replaced, it means there is something wrong with
between the MPPP and the MP is the MONI board itself. After checking the cable of
interrupted. Because the MPPP works the MONI board, it is found that a set of 485 bus in
normally, it means that the communication the socket is short circuited, which affects the data
between the MPPP and the MP is normal, bus connecting the left MP and the control layer.
Why the Active Indicator and

the Standby Indicator of the
Active MP Flash Every Several
Seconds?
Question Answer
Why the active indicator and the The reason is that when the active MP tries
standby indicator of the active MP flash performing the switching, it finds that there is
every several seconds? also something wrong with the standby MP. The

Maintenance Experience, Issue 55 (GSM Products) Change Tone Element PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Maintenance Experience, Issue 55 (GSM Products) Change Tone Element PDF

Hochgeladen von

Copyright:

Verfügbare Formate

Preface

In pursuit of the idea First-class service, Customer service, and in

Maintenance Experience Editorial Committee

Postal code: 518057

Contact: Song Chunping

Saving Error when

Symptom of MPMP and MPPP. Totally 118 time

Inter-BSC Handover Failure after

Communication Failure after

Symptom and background. It is found that the data of active/

Symptom Table 1. FacchCallInd is an 8-bit bitmap

Precaution for EDGE

Symptom deteriorated, such situation is even worse.

Network Cable from

Symptom interface on backplane. The network cable

How to Modify the IP

Symptom address set here is only used for originating link

Site Commissioning Failure

Symptom BSC directly and the problem is solved.

PA Over-heated Alarm in OB06

New Site Fails to Receive Calls

Figure 1. Calling Procedure of the Called Party

BTS Fails to Start up because

Symptom cabinet top is damaged. In case BTS self-

BSC could not Start up Normally

Symptom position with the standby CMM board to observe if

Help at OMCR Client

Symptom variable OMCDOC setting is correct.

variables button to check whether the environment

Symptom share dmemory("shared pool

SHARED_POOL_SIZE. If the large pool be equal to SHARED_POOL_SIZE. Restart

Symptom CI=1000-1004 (input the planned CI range)

Login Failure due to Incorrectly

Symptom incorrectly modifying properties of folders

Not Receiving Returned

Symptom to be F drive, causing OMCR client login

BSC Rack View Unable to be

Symptom The default resolution of OMCR rack view is

OMCR Client Login Failure

Symptom login fails either, with the same system prompt.

CBC Data Importing Procedure

Symptom tempstep number;

dbms_sql.v7); alterstr := 'alter sequence seq_smsid increment

How to Move ORACLE

Symptom be implemented through disconnecting network

The Inter-office Trunks

Symptom congestion, signal pass or no tone in two

in the same route group share the load, so all the

High Call Failure

Symptom had been modified at the BSC side recently, and

Clock Aging on the SYCK Board

Symptom all the clocks of the system circularly

Errors in R2 Incoming CLIP

Symptom where the MSC A office found the called

party at the MSC A side, but NDC90 (90 is the

and the maximum number length is eight digits.

Figure 5. Trunk Selector

The Subscriber Database

The IMSI Number Section in the

Symptom is required to back up the database before

delete from dynamicinfo where delete from scaddress where

delete from ggsnlist where delete from sscfsubaddr where

delete from o_trace where delete from sscuginfo where