2. Call Path Tracing
› Call Path Tracing allows the operator to trace M-MGw
resources involved in a call connection.
› Call Path Tracing can be initiated for a context of a VMGw,
and the operator gets the trace result for the VMGw including
information like termination type, end-point, board, subrack
and slot for the connection 。
Call Path Trace | Ericsson Internal | CBC-12:005050 Uen, Rev A | 2012-08-13 | Page 2
3. Call path tracing
Get Context ID From MSC
› In the MSC use the command CTRAI for the subscriber that will be traced.
› ctrai:msisdn=27832838432;
Phone Number
› TAG IDX MISCDATA
16 22 832838432
17 22 4
18 22 1
25 22 832838432
26 22 4
27 22 1
28 22 100
29 22 2
30 22 1
31 22 100
32 22 11
33 22 1
53 5 RBMGW1
53 8 RBMGW1
54 5 545262805
54 8 545262805
Context ID
Call Path Trace | Ericsson Internal | CBC-12:005050 Uen, Rev A | 2012-08-13 | Page 3
4. Call path tracing
Setp 1 Get Context ID From MGW
MGW> lh mesc mesc_info_fpif –busy / to find the context ID
$ lhsh 730200 mesc_info_fpif -busy
7302: Fpif CtxId 0x4020001
7302: RulingTerm1: 0x48009f22
7302: RulingTerm2: 0x48009f23
7302: OutstandingRCs: 0
7302: NrOfRcTries: 0
7302: status: 0x11b01058 TRFO_BREAK, INIT_REC,
7302: tfoStatus:
7302: TermId: 0x48009f22
7302: RCTriggeredTermId: 0x0
7302: initCodecs: 0x0
7302: gcpSM: SR
Context ID
Termination ID
Call Path Trace | Ericsson Internal | CBC-12:005050 Uen, Rev A | 2012-08-13 | Page 4
6. Call Path Tracing
Example in Moshell
MGW42> lhsh 000300 fro_call_path_trace <VMGW ID> <context ID>
When trace in Moshell, vmgw can not be auto detected,
vmgw ID can be found by command: fro vmgw
Call Path Trace | Ericsson Internal | CBC-12:005050 Uen, Rev A | 2012-08-13 | Page 6
7. Call Path Tracing
Example in Moshell
MGW42> lhsh 000300 fro_call_path_trace 2 0x4020001
Call Path Trace | Ericsson Internal | CBC-12:005050 Uen, Rev A | 2012-08-13 | Page 7
8. Call Path Tracing
Example in NM
We can use context ID to trace a call in NM, vmgw can be auto detect:
Call Path Trace | Ericsson Internal | CBC-12:005050 Uen, Rev A | 2012-08-13 | Page 8
9. Call Path Tracing
Example in NM
The trace result contains a device chain:
the contexts, the terminations belonging to the contexts,
and the resources belonging to the terminations.
In expand mode, we can see the codec, PCM number and related MO:
Call Path Trace | Ericsson Internal | CBC-12:005050 Uen, Rev A | 2012-08-13 | Page 9
Editor's Notes
Term/Resource Type--The first part has two values: T for termination and R for resource. The second value describes the functionality of the element. Possible termination types are the following:
AAL2-EXT: ATM external
AAL2-INT: ATM internal
TDM
IP
Connected To shows a list of elements that are connected to the previous element.
Mode shows the type of the connection (RO - receive only, SO - send only, SR - send and receive, IS - isolated).
Term/Resource Type--The first part has two values: T for termination and R for resource. The second value describes the functionality of the element. Possible termination types are the following:
AAL2-EXT: ATM external
AAL2-INT: ATM internal
TDM
IP
Connected To shows a list of elements that are connected to the previous element.
Mode shows the type of the connection (RO - receive only, SO - send only, SR - send and receive, IS - isolated).
Term/Resource Type--The first part has two values: T for termination and R for resource. The second value describes the functionality of the element. Possible termination types are the following:
AAL2-EXT: ATM external
AAL2-INT: ATM internal
TDM
IP
Connected To shows a list of elements that are connected to the previous element.
Mode shows the type of the connection (RO - receive only, SO - send only, SR - send and receive, IS - isolated).
Term/Resource Type--The first part has two values: T for termination and R for resource. The second value describes the functionality of the element. Possible termination types are the following:
AAL2-EXT: ATM external
AAL2-INT: ATM internal
TDM
IP
Connected To shows a list of elements that are connected to the previous element.
Mode shows the type of the connection (RO - receive only, SO - send only, SR - send and receive, IS - isolated).