Activating and deactivating subscriber tracing in VLR Activate subscriber tracing in VLR with the MWC command.

To display trace-activated subscribers and equipment in the VLR, use the MWL command. To check the trace settings of an individual subscriber, use the MWI command. The command displays both locally activated tracing cases and subscriber tracing cases activated in the HLR. The traced subscriber is identified with IMSI, MSISDN or Alternate Line Service MSISDN number (if available). To deactivate subscriber tracing in VLR, use the MWE command. Use the IMSI of the subscriber whose tracing you want to deactivate. Tracing is stopped only in the VLR where the deactivation is performed. If you need to deactivate a tracing case in several MSC/VLRs, you must do it separately in each of them. Before you start See Setting up the output I/O device . Steps Expand/collapse all 1. Define the call phases that produce a report See Defining the call phases that produce a report . 2. Set up the trace report transfer method See Setting up the trace report transfer method . Note You have to check the PRFILE parameter 2:386 setting and change it to transfer via CMIS in this case. Otherwise the setting in the PRFILE overrides the parameter <priority of tracing in MSC and BSS> . The report transfer method (FTAM or CMIS) is controlled by both parameter <priority of tracing in MSC and BSS> and the 2:386 PRFILE parameter. For more information see Trace report transfer . 3. Check and set up trace support in other network elements See Setting up trace support in other network elements . 4. Check the trace setting in the VLR (MWI) Check the trace setting with the MWI command in the VLR. If you need to modify an existing tracing case, you have to first deactivate the case with the MWE command . You can then modify the settings with the MWC command. 5. Activate subscriber tracing in VLR (MWC)

ZMWC:IMSI=<international mobile subscriber identity>:REF=<trace reference>,OMC=<operation and maintenance centre address>,MEVENT=<trace invoking event in MSC and BSS>,MTYPE=<MSC trace record type>,BTYPE=<BSS trace record type>,PRI=<priority of tracing in MSC and BSS>; Further information: Example: Activating subscriber tracing in VLR 1. Check the I/O device where the reports are output in each MSC/VLR.

ZIID::GSMME1PR; ZIID::GSMME1MG; 2. Change the I/O devices. The current I/O device is virtual display unit, change the ASCII reports to be output in line printer, and the binary reports in WDU. ZIIS::GSMME1PR:DEV=VDU-0:DEV=LPT-0; ZIIS::GSMME1MG:DEV=VDU-0:DEV=WDU-0; 3. Check the PRFILE parameter 9:36 which defines the call phases when a report is produced. ZWOI:9; 4. Change the value of the parameter so that the report is produced when the called subscriber answers, charging ends and a service is used. The binary number for the example is 000101100 which is 2C hexadecimal. ZWOC:9,36,2C; 5. ZWOI:2; 6. Change the value of the PRFILE parameter 2:386 to allow transfer of the reports via FTAM or CMIS according to the parameter <priority of tracing in MSC and BSS>. ZWOC:2,386,3; 7. Check if the BSS supports tracing in the case of a BSC whose name is ABERDEEN. ZEDB:NAME=ABERDEEN:FUN; 8. Change the BSS parameter for the BSSAP version 9 to support tracing if trace reports are to be generated in the BSC. Check the PRFILE parameter 2:386.

ZEDT:VER=9:F,34,1; 9. Check if, in inter-MSC handover, and in all location areas, the subsequent MSC supports tracing. ZEIO; 10. Change the location area parameters so that in inter-MSC handover the MSC supports tracing in the case of a location area whose code is 45531. ZEIM:45531:TRA=Y; 11. Activate local subscriber tracing of the subscriber whose IMSI number is 244041297264491. The trace reference is 100, there is no OMC address, the trace invoking events in the MSC and the BSS are all events, the MSC trace record type is basic, the BSS record type is basic and the trace records are transferred to the OMC by CMIS. ZMWC:IMSI=244041297264491:REF=100,PRI=Y; For the whole topic summary, see Subscriber and equipment tracing overview