Hi all, below is the check list to track silent call.   Silent call tracking procedure (one-way or both-way):

1. Packet Loss Alarm checking and troubleshooting accordingly(A party and B party Both MGw)

2. Open Fullflow trace and track the context used in this call.(A party and B party Both MGw)

3. DSP CTXINFO to query for the TID used by the caller and the callee on the UMG8900(A party and B party Both MGw)

4. DSP TERMINFO: CID=XXXXX, TIDX=Y; to query for the information about the IP termination, including the local and remote IP addresses, of the call(A party and B party Both MGw)

5. Run PING to ping the remote IP address. Check the traceroute result.(A party and B party Both MGw)

6. If end to end ping and traceroute fails, involve IPTS in the troubleshooting(A party and B party Both MGw)

7. DSP IPIF to check the end-to-end port attributes of A and B party MGw matches or not

8. Match LST PAYLOADTYPE, LST RFC2833 and LST TCPARA command output results(A party and B party Both MGw)

9. Get the Peer end BSCs Payload IP and run ping from all HRB boards of both MGw

10. Check LST BSC for Codec types and Bearer type

10. Check LST UPPARA output result of both MGw

11. Check LST CODECCFG in MSC server and check if there is any mismatch with MGw Payload and BSC Payload Type

12. LST SFP:P13=bit7,8=1

 

 

if you have any suggestion plz add here...

This document is very well done

well described.

good doc to track silent call

nice share

great document for silent call

thanks for the info

good doc for troubleshooting silent call

good doc for troubleshooting silent call

thanks for the share