讲义说明成果callpathtool-presentation

1、Call Path TracingContentsUser GuideSystem Administration Overview User GuideThe Call Path Tracing feature provides the ability to trace a call across one or more MSCs and the M-MGw used by these MSCs, in a given call. The resulting trace information is output in a way that enables the user to identi

2、fy the network elements (NEs) and resources used in the traced call. The tracing information is retrieved from the MSC using the MSC command CTRAI and tracing information is retrieved from the M-MGws over the MOCI interface. To activate the feature the user must know the MSISDN and the MSC network e

3、lement that this MSISDN is connected on either the originating or terminating side of the call to be traced.Note: The call must remain live throughout the process of call path tracing application.The following information is provided to the user: Identities of all the MSCs and M-MGws connected in th

4、e traced call as well as the identities of the ing and Outgoing devices in the MSCs. The Call Path Tracing printout from each of the MSCs connected in the traced call. Call Path Tracing (CPT) results from each of the M-MGws involved in the traced call.The feature can be used in both the Layered and

5、Non-Layered Architecture, in the latter case the identities of all the MSCs connected in the call chain and the CTRAI printout from each MSC will be provided.Call Path Tracing GUILaunching the Call Path Tracing GUIThe Call Path Tracing GUI is launched from the OSS Network Explorer (ONE) GUI : Launch

6、 the ONE GUI From the menu select Tools, then Core Network Tools, then Call Path TracingIt may be also launched by executing the command: cd /opt/ericsson/Job_Manager_Scripts /callpathtracing/bin ./start_callPathTracing.sh &Running the Call Path Tracing GUI The Call Path Tracing GUI is now launched:

7、 Select the network element, which the trace is to be run against, using the Search button, which opens an MSC Node Selection Panel: Enter the MSISDN number in the space provided and then start the trace. Progress is indicated by the Progress Bar. The status of a job can be checked by clicking the C

8、heck Job Progress button. When the trace is completed choose the View Trace Results button which will return the Summary Results to the text area. If the trace fails the error log will be displayed.Tracing ResultsMSC Tracing ResultsThe Call Path Tracing printout received from the MSC is presented to

9、 the operator in the MSC Tracing Results file.ExampleM-MGw Tracing ResultsThe following data is presented in the M-MGw Tracing Results file :traceId The unique identity of the requested trace for the Call Path Trace. rowId The row number for the Call Path Trace result. Range: 1.maxNoOfRows resultCod

10、e The following enumerated result codes for the Call Path Trace are possible: 0 : SUCCESSFUL 1 : UNSUCCESSFUL 2 : NOT_READY_YET maxNoOfRows The number of rows in the output window for the Call Path Trace result. Type column shows the type of an element. Type consists of two parts. First part has two

11、 values: T for termination and R for resource. Second value describes the functionality of Element. Possible termination types are: AAL2-EXT: ATM external (Asynchronous Transfer Mode) AAL2-INT: ATM internal TDM (Time Division Multiplexing) IP (Internet Protocol)Possible resource types are: AMR (Adap

12、tive Multi Rate) TS (Tone Sender) CS (Continuity Check) DTMF-SEND: DTMF sender (Dual-tone Multifrequency) DTMF-REC: DTMF receiver EC (Echo Canceller) IM (Interactive Messaging) MPC (Multiparty Call) CSD-DIGITAL (Circuit Switched Data) CSD-MODEM UP-MFH (User Plane Media Frame Handler) CSD-GSM-MFH (Ci

13、rcuit Switched Data - Global System of Mobile Communications - Media Frame Handler) INMARSAT GTT (Global Text Telephony) IPB (IP Bearer) CDMA-SC-DTMFSIdentity column shows the identity of an element. It starts with R if it is a resource and T if it is a termination. For resources the identity consis

14、ts of two parts separated with a dash (for example R12-3456): The first part is the server identity and the second part is the resource identityConnected To column shows a list of elements that have a connected to relationship to the previous element. If the element has no connections, then this col

15、umn contains value (undetermined). Mode column shows the type of the connection (RO - receive only, SO - send only, SR - both, IS - Isolated). Subrack column shows the name of Subrack, for example 222A where 222 is the name of the cabinet and A is the slot position in the cabinet. Slot shows the slo

16、t number 1-32. Port/DSP # shows the line number 1-8 (in case of ET board) or DSP number 1-16 (in case of MSB board). In case of ETMC41 board the port value is always 1 as there is only one physical port in ETMC41 board. AESA/SUGR AESA shows the ATM End Service Address (for example af 01 df 78 45 9d

17、ff ff ff 45 78 90 45 ed ff 00 00 00 00 00), SUGR shows the Served User Generated Reference (for example 30 ff 00 ed). There may be one AESA/SUGR per termination, maximum 20 per context. Usage State shows the status of Multiservice Switching Forum (MSF) device Busy or Idle. TDM Group shows the name o

18、f the TDM Termination Group. PCM System shows the number of the Pulse Code Modulation (PCM) system between 0 and 2097151. TS shows the time slot 0-31. IP Addresses Orig shows the originating IP Address. Range of the IP address is 0.0.0.0 - 255.255.255.255. IP Addresses Dest shows the destination IP

19、Address. The range of the IP Addresses Desination port is 0 - 65535. VPI shows the value of Virtual Path Identifier between 0 and 65535. VCI shows the value of Virtual Channel Identifier between 0 and 65535. CID shows the value of Connection Identifier between 0 and 255. Summary FileThe Summary file

20、 lists for each MSC involved in the traced call: the identity of the MSC the identity of the ing and outgoing devices for the MSC the identity of the M-MGw connected to the MSC which is used for the traced call.Errors During TracingThe MSC_Mapping script must be executed before the main tracing scri

21、pt can be executed. The resulting flat file is used by the main tracing script to determine the next or subsequent MSC to continue tracing on. The mapping script must be re-run if there are any changes to an MSCs route or device configuration or if any new MSCs are added in the operators sub network

22、.The printout Next MSC could not be found is received in the MSC Tracing results file indicating that the mapping script needs to be re-run.System Administrator GuideCall Path Tracing TasksCall Path Tracing consisits of two tasks grouped under the task category CallPathTracing.Table: Tasks included

23、in Task Category CallPathTracing Task NameTask DescriptionCallPathTracingThe CallPathTracing script which performs tracing of all the MSCs and MGws involved in the call. The tracing is performed using the normal MSC tracing functionality, mand CTRAI, and the tracing function defined by the VMGw Managed object in the MGwMSC_MappingMaps SPC/BCIC to Device to MSC identity for all or specified MSCs. The resulting flat file is used by the CallPathTracing task to identify the next MSC to continue tracing onThe CallPathTracing task is the main script of the featur