Beruflich Dokumente
Kultur Dokumente
Table of Contents
Table of Contents
Chapter 9 Troubleshooting for Voice .......................................................................................... 9-1 9.1 Overview ............................................................................................................................ 9-1 9.2 Fundamental Knowledge ................................................................................................... 9-1 9.2.1 Transmission Format of Voice Signal ..................................................................... 9-1 9.2.2 Transmission Path of Voice Signal ......................................................................... 9-2 9.2.3 Concepts ................................................................................................................. 9-4 9.2.4 Common Operations ............................................................................................... 9-5 9.2.5 Supplement ............................................................................................................. 9-7 9.3 Processing of Voice Troubles ............................................................................................ 9-8 9.3.1 Analysis ................................................................................................................... 9-8 9.3.2 Procedures to locate faults...................................................................................... 9-9 9.4 Locating Trouble .............................................................................................................. 9-10 9.4.1 Single Pass and No pass ...................................................................................... 9-10 9.4.2 Echo ...................................................................................................................... 9-12 9.4.3 Voice Discontinuity ................................................................................................ 9-14 9.4.4 Noise ..................................................................................................................... 9-15 9.4.5 Cross-talking ......................................................................................................... 9-17 9.5 Examples ......................................................................................................................... 9-18 9.5.1 Cross-talking Resulting from Improper Data Configuration .................................. 9-18 9.5.2 Voice Discontinuity Resulting from BCCH Carrier Mutual-assistance .................. 9-19 9.5.3 Single Pass Resulting from MS Fault.................................................................... 9-20 9.5.4 Noise Resulting from Poor Contact of E1 ............................................................. 9-21 9.5.5 Voice Loopback Resulting from Outgoing Cabling ............................................... 9-22
Note:
The transmission path is for multi-module environment. For the single-module environment, no board on the AM/CM module is provided, such as E3M etc.
MSC (when a signal doesnt go out of a SM, it is destined to the corresponding GNET. Here, the SM and GNET are parts of MSC): DT(HW)GNETGOPT(Optical fiber)GFBIGCTN See Figure 9-2 for details:
Radio Link
GCTN HW
E1 BIE HW
(BM1)
E3M
E1 E1
Transmission Equipment
HW
E3M
E1
GOPT GFBI
E1 BIE
HW GNET
HW
E3M
TCSM
E1
HW E1 HW
(BM2)
E3M
E1
BIE
GNET HW DT
E1
E1
HW
(SM1)
DT
E1
GCTN
E1
GFBI GOPT
GNET HW DT
E1
E1
PSTN
EC DT HW
(SM2)
HW
DT
E1
E1
Figure 9-2 Transmission path of GSM voice signal 1) Timeslot interchange is implemented in BTS, which is not illustrated in the figure above. BTS2X BIE or BTS3X TMU implements switch between TRX time slots and E1 time slots, which are in a definite one-to-one relationship. 2) 3) 4) BIE implements mapping between E1 time slots and HW time slots, which are in a definite correspondence relationship. GNET at BSC BM implements mapping between HW time slots and A interface time slots, which is dynamic. The mapping of each call is different from others . GCTN at BSC implements interchanges between 2.048%16Mbit/s HW time slots in GFBI and those in E3M, which are not in a definite correspondence relationship, and each call is different from others. 5) 6) E3M implements interchanges between HW time slots and E1 time slots, which are in a definite one-to-one relationship. GNET at MSC implements interchanges between two A interface circuits (i.e., calls between two MSs in the same SM), between HW time slots in DT and those in GOPT (i.e., calls between two SMs in the same MSC) or between local circuit and outgoing circuit (e.g., calls between MSs in the local SM and local fixed-line phones, or between out-of-town fixed-line phones and MSs). 7) GCTN at MSC can implement interchanges between HW time slots in two FBIs only when the call between two SMs is originated.
Note:
The above analysis doesn't include the prepaid MS. For such MS, the outgoing route is needed even if the call between two local MSs is originated.
GMPU is not illustrated in the above figure. However, actually the allocation of circuits GMPU accomplishes and request for layout of GCTN transferred by GMCCS both are relevant with the interchange between voice signals. A E3M or a TCSM may not serve the BM controlling and maintaining it, but for the A interface circuit occupied by the call under the BM, such relationship doesnt apply. That is, the call under BM1 doesnt always occupy the TCSM circuit configured by BM1. Actually, the TCSMs configured by a BM usually belongs to different SMs. A interface circuits are allocated by MSC, consequently, it is possible the A interface circuit occupied by the call under BM2 corresponds to the TCSM belonging to BM1, and at this time, GCTN takes the responsibility of implementing the overlap between HW in GFBI of BM2 and that in E3M of BM1.
9.2.3 Concepts
Full rate service: Full Rate encoding/decoding (FR), and the algorithm Regular Pulse Excitation-Long Term Prediction (RPE LTP) is adopted. Encoding process: TC frames the voice signals received from MSC based on the principle of 20ms per frame. A frame of data contains 160 PCM sampling points, each of which is 8 bits long. The parameters output after encoding contain 260 bits totally, which plus the synchronization header and control parameter is a 320-bit TRAU frame. Decoding is contrary to encoding: After receiving a TRAU frame sent from BSC, TC restores it into the voice data according to the decoding algorithm and sends it to MSC. DTX: Voice Activity Detection (called VAD for short) and Silence Descriptor (SID) are applied to Discontinuous Transmission (DTX) in GSM. When TRAU detects the data received from MSC is a non-voice message via the VAD functional module, the voice flag bit in the TRAU frame formed after encoding shall be cleared. After discriminating the flag bit, BTS disconnects the downlink until the flag bit is set. Similarly, when receiving an uplink frame, TRAU discriminates the SID flag and set of the flag means the MS is in an interim state. To make the receiving end feel the GSM network is keeping serving it, TRAU injects a comfortable noise into the uplink through the substitute technology so as not to make the subscriber consider the conversation is interrupted. DTX is applied to TRAU, which may lower the transmission power of BTS and MS, reduce intra-frequency interference among radio interfaces and weaken the sensitivity of the GSM voice signal to exceptions occurring to radio interfaces.
9.2.5 Supplement
1) Only when a valid uplink TRAU frame is received can TC be started. Therefore, in case a fault or a severe bit error occurs to the uplink 16kbit/s link, which causes the situation that TC is not able to receive the valid TRAU frame, TC cannot be started. And no matter a conversation over the faulty link is originated between two MSs or between an MS and a fixed-line phone, both parties cannot hear each other. If a downlink 16kbit/s link gets faulty, it only impacts on the downlink voice signal. When a MS over the faulty link communicates with a fixed-line phone or another MS over a normal link, the MS over the faulty link cannot hear the opposite party. Such situation is called signal pass. If both the downlink 16kbit/s links of the channels occupied by the two MSs are faulty, they shall not be able to hear one another. 2) As what is transmitted over the transport line is the signal multiplexed by many time slots, all the time slots over the line shall get faulty if the line is faulty or connection error occurs. Only in the devices where processing is made by time slots may parts of time slots fail, such as the boards implementing switching: BTS2X BIE, BTS3X TMU, BTS3X BIE, BTS3X GNET, BTS3X GCTN, BTS3X E3M, MSC GNET and MSC GCTN etc. Such faults may be caused by board failure, incorrect data configuration, host program error, poor contact of the line, bad quality of stub or electromagnetic interference. If the EMC protection capability of a board is not good enough, parts of its time slots may get faulty. 3) Same BER may impact the 64kbit/s link less than the 16kbit/s link. If bit error occurs to the 64kbit/s link, the generated noise shall be relatively even without obvious fluctuation. Even when the noise submerges the voice due to overhigh BER, it still can remain even. However, for the 16kbit/s link, even if the original bit error is symmetrical, since the 16kbit/s compressed signal should be decoded to become the voice signal, the bit error shall become uneven for the voice signal after decoding, and bubble, voice discontinuity and metallic sound may occur.
Besides the transmission equipment, boards and cables, the slots accommodating these boards, backplanes, stubs and connectors should be checked as well. For convenience of description, all above are called boards and cables hereafter.
other than the BIE group No., and switch over the group of BIEs. If single pass remains, proceed the following operations. If the trouble disappears, the trouble may be caused by BIE. Switch over them back for further test. 8) Use the test MS to implement forced handover. Hand over the MS to the cell of another adjacent site controls and check whether single pass disappears. If possible, inter-BSC switchover test can be implemented.
II. Analysis
As per voice circuit procedure in the system, the two type troubles may be caused by: 1) Radio problem
Radio environment, e.g., imbalance between uplink/downlink levels resulting in voice of poor quality and interference to one party. 2) BTS fault
Hardware: Board (e.g., CDU, TRX, TMU etc.) fault, error of the switching network table of TMU. Software: Data configuration error. For instance, TS number in [Radio Channel Configuration Table] are configured incorrectly. Site BIE mode ID in [Site BIE Trunk Mode Description table] are inconsistent with those in [Site BIE Configuration Table], which causes the situation that the cascaded BTS cannot converse normally. 3) Abis interface fault
Poor quality devices between BTS and BIE (including the trunk transmission equipment in the middle), connectors and cables as well as bit error of transmission line may cause voice of poor quality to one party. 4) BSC fault
Hardware: All boards and cables between BIE and GCTN (including the backplane). Software: Time slot and HW configuration of BIE. 5) A interface fault
Hardware:
z z
Board fault: Including the boards such as E3M, MSM, FTC, DT at MSC etc. Cable fault: Including the cables such as crossover cable and crossed pair of cables. Setting error of DIP switch: There are DIP switches on 12FTC and 13FTC setting whether these FTCs are multiplexed, and MSM also carries a DIP switch used for setting the time slot occupied by the maintenance control message of FTC. If these DIP switches are set incorrectly, it may cause single pass or no pass.
Software: CIC configuration. CIC is for setting whether A interface trunk circuit is available. If 12FTC is put into use, EFR service cannot be configured, otherwise single pass may occur when a MS originates a call to a fixed-line phone or no pass may occur when a MS originates a call to another MS. For the group of TCSMs during multiplexing, the four time slots that are used for bearing signaling and correspond to four FTCs should be set to be unavailable. And the last time slot of the last FTC that is used as the maintenance time slot should be set to be unavailable as well, otherwise both parties involved in a conversation may not be able to hear each other. 6) MSC
Hardware:
z
The boards such as DT, GNET and GCTN are faulty or in poor contact with backplanes, or the backplanes or slots get faulty. Cable damage or in poor contact. For instance, the HW cable between DT and GNET, optical fiber between SM and AM and outgoing trunk cables are damaged or in poor contact.
Software: [Semi-permanent Connection Table] or data of outgoing trunk is configured incorrectly. Sometimes a faulty MS may cause such troubles.
9.4.2 Echo
I. Description
Generally echo indicates when a digital MS originates a call to another digital MS or a fixed-line phone, one party can hear the voices from itself besides those from the opposite one. Voice loopback indicates when a digital MS originates a call to another digital MS or a fixed-line phone, one party only can hear the voices from itself while the other party can hear nothing.
II. Analysis
1) Echo occurring in case of conversation between two MSs
Such echo is a kind of acoustic echo. As the acoustic isolation performance of some MSs cannot meet the requirement of GSM protocol, the voices received by the receiver can be sent to the microphone easily. Then these voices are sent to BTS after decoding, and finally to the opposite MS. Such echo is caused by the local MS and brought to the system, and finally heard by the opposite MS. Acoustic echo has nothing to do with time slots of FTC, carrier time slots of BTS and reloading of data but is related to MS type. 2) Echo occurring in case of conversation between MS and fixed-line phone
Such echo is a kind of electrical echo. Impedance mismatch of the hybrid converter at PSTN causes the situation that the transmitted signal is coupled to the receiving line, thus echoes occur at the 4-wire end. 3) Voice loopback
If an intra-office call is looped back, usually it results from hardware loopback owing to wrong connection of A interface trunk cable. If a outgoing call is looped back, it may be caused by hardware loopback occurring to the outgoing trunk. If GNET or GCTN of BSC or MSC gets faulty, time slot switching error even loopback may be caused.
Acoustic echo is related to the voice propagation environment in which the MS is located (e.g., background noise, surrounding barrier, space size and climate etc.). Therefore, echoes dont always occur to the MS that may generate echoes.
The following method can be used confirm the opposite MS generates acoustic echo: Adjust the tone of the opposite MS and the local party can feel the change of echo tone apparently. 2) Echo occurring in case of conversation between MS and fixed-line phone
During conversation between a fixed-line phone and a digital MS, if the MS can hear large quantities of echoes, such kind of echo is called acoustic echo, which may result from lack of Echo Cancellor (EC). Search the corresponding route data of the call to ensure the data is correct. If correct, check whether the EC of the corresponding mobile network equipment is configured accurately according to the principle that EC is placed near PSTN, so as to guarantee EC works normally. Occasionally, echoes of high volume may occur when a digital MS originates a call to a fixed-line phone. That is because the hybrid coil at the fixed network doesnt measure up and the volume of echoes generated exceeds the processing capability of EC, which results in echoes of high volume occurring at the digital mobile network. As soon as a call is set up, EC shall perform adaptive matching of echo cancellation dependent parameters. If parameter search is too slow or unsuccessful, temporary echo or continuous echo may occur just after the call was set up. Unfrequent occurrence of such phenomenon is normal. 3) Voice loopback
According to the numbers of the calling and the called parties and time when a loopback occurs, search the corresponding CDRs in MSC and confirm whether the calls looped back went through the same route, and then check whether the trunk cable corresponding to the route is connected incorrectly. When a intra-office call is looped back, block the A interface circuit and make 32 circuits of only one trunk idle. Then perform dial-and-test on each trunk of the A interface in sequence to check whether loopback exists. If it exists, check whether the corresponding trunk is connected incorrectly as per the No. of the CIC occupied by the call. If only the outgoing call is looped back, perform dial-and-test on the outgoing trunk to check whether loopback exists. If it exists, check the corresponding trunk is connected incorrectly as per the No. of the CIC occupied by the call. If all trunks are connected correctly after the above operations, (however, it cannot be ensured that other offices corresponding to the outgoing route are connected correctly), the trouble still remains. Try to switch over GNET and GCTN at MSC. If the trouble still cannot be eliminated after the above operations and it is confirmed the outgoing call was looped back, check whether the equipment and cables of other offices involved in the outgoing route are in a normal state.
Huawei Technologies Proprietary 9-13
II. Analysis
The causes resulting in voice discontinuity are as follows: 1) Frequent handover
Since GSM system supports hard handover. The handover from a source channel to the destination channel can cause loss of Abis interface downlink voice frames, so voice discontinuity resulting from handover during conversation is inevitable. Sporadic handover is not attention-getting, while frequent handover occurring at cell edges or due to cell overlap may cause discontinuity of conversation. Such trouble can be avoided by optimizing the network, adjusting obliquity and height of the antenna and configuring the parameters interference handover uplink/downlink quality threshold and emergency handover uplink/downlink quality limit threshold. Location method: Use a test MS to check the channel occupied by the MS changes continuously during a conversation. 2) Radio link interference
Interference may increase the BER over the radio link and cause voice discontinuity. In addition, the conversation may be of poor quality owing to signal fluctuation at cell edges. Location method: Perform a road test through a test MS to analyze and check whether radio link interference exists with the help of Ant Pilot network optimization software. 3) BTS transmission fault
Check whether all connectors (including connectors on DDF) are in good condition. For fiber optical transmission, check whether fiber connectors are clean and whether BER is high, and microwave transmission may be impacted by climate. It should be noted that the 75: coaxial cable laid from the transmission interface boards (such as 42BIE, TMU) to the BTS cabinet top in BTS cabinet may be of poor contact due to long time use. If the connectors in the cabinet are dusty, it may impact the conversation. If both microwave transmission and fiber transmission are adopted, make sure these types of equipment are matched in interface transmission impedance.
Location method: Check whether the transmission alarms, such as BTS BIE remote alarm, LAPD link alarm, are given from the alarm system. Furthermore, testing whether bit error occurs to the transmission path is the most effective and convenient method.
Caution: Sending pseudo codes and using the clock in the BER tester could guarantee the result of the BER test completely reflects the quality of the link.
4)
Location method: Use a test MS to check whether the channel or frequency occupied by the MS changes continuously during a conversation and whether the frequency and time slot are fixed in case that no voices are transmitted.
9.4.4 Noise
I. Description
Bubbles, clicks and metallic sounds heard during a conversation are called noises. In worse condition, only noises instead of voices can be heard.
II. Analysis
Generally, noises are caused owing to bit error. Besides the fault of any board, connector or cable on the path via which voice signals go through, grounding error, interference, clock fault or wrong setting of DIP switch may result in bit error. Interference on radio link can cause bit error, while clock unsynchronization shall lead up to slip frame or loss of frames. Wrong setting of DIP switch may bring about errored bits, although such mistake happens occasionally. Different errored bits may cause different impacts. The errored bits on the line from A interface to MSC impact on PCM sample, as a result, the noises generated are relatively even because the noises and voices are in a overlap relationship. The
Huawei Technologies Proprietary 9-15
errored bits on the line from A interface to BSC impact on the compressed voice signals which should be decoded before being heard although these bits are also well-proportioned. Consequently, the noises generated, such as bubbles, sense of discontinuity and metallic sounds, fluctuate greatly, and make some sentences cannot be distinguished clearly. Slip frame or loss of frame caused by clock unsynchronization is regular in time, therefore, noises appear regularly during a conversation.
Possible causes:
z z z z z
Trunk transmission bit error TRX fault, including version incompatibility of TRX software and hardware. FPU fault CDU fault MCK fault, which may cause instability of BTS clock frequency, thus impact the quality of conversation. Interference on radio channel Antenna fault
z z
Location:
z z z
Perform dial-and-test by using a test MS Check whether the related alarm is given Tracing messages or check signal quality and whether inference exists from the MS Use an antenna tester to test the antenna system Check whether the grounding system is wrong. Perform a transmission bit error test Test the clock signal of the faulty BTS. BIE related noise
z z z z
2)
Possible causes:
z z z
BIE fault HW fault between BIE and GNET Transmission error from BIE to BTS.
Location:
z z z
Check whether the related alarm is given (PCM alarm) Perform a transmission bit error test Replace the BIE
Huawei Technologies Proprietary 9-16
Connect the BTS to another BIE Check the HW and E1 cable of the BIE Switch over the GNET BM related noise
3)
Possible causes:
z z
Switching network board (GNET and GCTN) fault Optical fiber interface circuit fault.
Location:
z z z
Check the connection of optical fibers and related connectors Check HW of GNET Switch over GNET or GCTN. Intra-office noise
4)
Possible causes:
z
A interface dependent board & cable fault (E3ME1MSMinternal HWFTCE1or trunkDTHWGNET at MSC) Inter-module circuit fault: Optical fiber interface circuit, GCTN at MSC
Location:
z
Enable GSM user interface trace at MSC and perform dial-and-test on A interface circuit. Analyze the trunk occupied by the faulty call based on the interface message and calculate the corresponding board, and then check the related boards and cables (including all boards, cables and backplanes from E3M to GNET
If trunk equipment is in the way between BSC and MSC, test the equipment. (Check whether errored bits exist in it and whether the grounding system is correct)
z z
Check whether the related alarm is given If inter-module forwarding at MSC is implemented for the faulty call, check the associated connections and connectors. Switch over GCTN at MSC if necessary. Outgoing noise
5)
Based on the outgoing route, check the related outgoing trunk equipment and cables.
9.4.5 Cross-talking
I. Description
During a conversation, the voices from the third party, besides those from the opposite party can be heard, or only the voices from the third party can be heard. Such phenomenon is called cross-talking.
II. Analysis
Generally cross-talking occurs when the call passes through the outgoing route. Wrong data configuration (e.g., CIC) or incorrect hard connection (e.g., E1 cable of A interface) may cause cross-talking accompanied with single pass or no pass.
9.5 Examples
9.5.1 Cross-talking Resulting from Improper Data Configuration
I. Description
Single pass/no pass accompanied with cross-talking occurred during conversations near a BTS.
III. Analysis
The Circuit number in the [Radio Channel Configuration Table] is used to deliver TMUs of BTS (BIEs of BTS20) for switching of time slots of a carrier. Since the carrier signaling adopts the data in the radio channel connection table, it is normal. However,
Huawei Technologies Proprietary 9-18
as TCHs for bearing voices are configured repeatedly, the TCH assigned to the carrier shall be switched to the corresponding TCH of TRX9, thus result in single pass. If the corresponding TCH of TRX9 is being used for conversation, the uplink voices of TRX 9 may be switched to the corresponding time slot of the TRX, thus cross-talking occurs.
III. Analysis
The channel configuration of the first carrier is changed because carrier mutual-assistance was implemented for the under-power alarm, and the power amplifier is disabled as well. The second carrier has been configured with BCCH and
Huawei Technologies Proprietary 9-19
SDCCH and the conversation is handed over to the second carrier. Based on the judgement principle of under-power alarm, the power amplifier shall be enabled every ten minutes after the alarm occurs and will implement detection in 10 ms. If no alarm signal is detected, it should be considered the alarm disappeared. In this way, as the first carrier has disabled the power amplifier after ten minutes and no conversation is made, the first carrier fault will be considered to be recovered after the detection 10 ms later. As per the cell BCCH mutual-assistance procedure, the original BCCH carrier will make BCCH mutual-assistance switchback to reconfigure channels after recovery. However, the active TRX will serve to send power, generate under-power alarm and implement cell BCCH mutual-assistance, consequently handover between the two carriers will be ceaseless. In this way, as it has no time to hand over a call that has been handed over to the carrier whose power amplifier was enabled just now back to the second carrier during second-to-first handover, conversation discontinuity will occur.
III. Analysis
After used for a long while, especially crashed, the parts in the MS may be loose. Therefore, once single pass occurs, check the quality of the MS first.
Voice signals became faint (without discontinuity or distortion. These signals can be considered to be normal if these noises could be regardless), while noises got loud (the type of these noises are similar to that of white noise), and the voice signal and the noise were overlapped. RQ in the test MS was 0. When the MS served as the calling party, loud noises appeared as soon as a ringback tone was returned. 2) Popularity
The result of dial-and-test on the faulty BTS showed that the noise was irrelevant to the place where the BTS resided, BIE the BTS belonged to and the transmission path between the BTS and the BIE. And such noise existed in all cells of all BTSs. 3) 4) Downlink Random occurrence. The occurrence probability increases with the augment of traffic.
Based on the above features, it can be concluded that: According to features (1) and (4), it could be known that the noise was caused by fault of the circuit from A interface to MSC. (The noise and the voice signal were overlapped. The noise could be caused by bit error of PCM sample or of 64kbit/s link, and its occurrence probability is relevant with polling of A interface circuits.
As per feature (2), the faulty point should be in the range from BIE of BM to MSC. GNET and GOPT were switched over, and optical fibers and fiber connectors were unplugged/plugged and cleaned. GCTN was switched over again for the line from A interface to BSC, and the noise didnt disappear at all. A interface circuit allocation principle: Provided that the call signaling from BSC arrives at a module in MSC, this module shall be allocated with circuits preferentially. Only when the circuit occupancy in the module reaches the stated threshold can the signaling be transferred to other modules for circuit allocation. If the A interface circuits are not congested too much, the signaling is hardly transferred among modules and the A interface circuits are almost allocated sequentially in the module. For the single-module MSC, A interface circuits are allocated sequentially.
Huawei Technologies Proprietary 9-21
2)
BSC and MSC have four modules respectively, whose A interfaces are in a one-to-one relationship, as a result, it is impossible the signaling from multiple BMs reaches the same SM. Furthermore, as the A interface circuit has sufficient space, usually signaling transfer doesnt occur at MSC. Also, dial-and-test should be performed between two MSs under the coverage of the same BTS, therefore, it almost can be concluded that the A interface circuit from BM to MSC, namely FTCDTGNET of SM1, gets faulty. By performing dial-and-test on the A interface circuit between BM1 and MSC, the corresponding trunk circuit (with DT No. of 11) of FTC No. 87 was confirmed to be faulty. After FTC and DT were switched over in turns, the trouble still remained. A trunk alarm was given by tightly touching the E1 cable near the connectors at the back of the two boards to indicate the E1 cable is of poor contact with the plug of the DTM backplane. After unplugged and the plugged, the E1 cable was tested again, and the trouble disappeared.
III. Analysis
If the noise is superimposed, usually it indicates the line from A interface to MSC is faulty. If it is random and ruleless, the line from TC to BSC may be faulty.
III. Analysis
As the physical uplink and the physical downlink of radio interface are separate by frequency, and those of Abis interface are unsymmetrical, it is impossible that loopback occurs between Abis interface and BTS. Also, frequency hopping cannot cause loopback.
Huawei Technologies Proprietary 9-22
The data configuration was correct after scrutiny. Voice loopback is possibly caused by loopback on the physical layer, and may occur in the following cases: 1) 2) 3) As most of voice loopback exists in the outgoing call, it may occur to the trunk between local MSC and tandem exchange. Loopback may occur to the trunk between local MSC and TMSC. Loopback may occur to transmission equipment.