Author Topic: T1D4 Call trace translation  (Read 1269 times)

Offline mszodiac

  • Sr. Member
  • ****
  • Posts: 232
  • Country: ca
  • Karma: +7/-0
    • View Profile
T1D4 Call trace translation
« on: March 08, 2016, 09:29:04 PM »
Hi everyone!

We have a site that uses both ISDN and T1D4 circuits.  T1D4 is used for outgoing calls only, and the ISDN for incoming.  I've familiarized myself with CCS trace command when troubleshooting the ISDN circuit.  However, I cannot make sense of the EDT TRACE TSP CC <PLID of T1D4> command.

For example, stat on the PLID shows ID "7 0401".  Can I correlate this ID to the TSP message? I was hoping "Msg ID 0x102" would be the same as the call ID.

I am trying to figure out why outgoing calls are intermittent.  Say I make a call, only 3 out of 5 calls work.

Are there other commands I can use to troubleshoot the T1D4 circuit?

Here's a sample out put of the PLID stat, and the TSP.  Thank you all for your input, as always.

Location       | Device                  | State         |  Owner     | ID   |Status   
----------------------------------------------------------------------------   
 5 1  2   1 19| Universal T1         |Busy           |Call Proc    |7 0401|Wait     

2016-03-08  20:58:15   T1d4Stack->T1d4Wrap id=UAPI_CONNECT_INDICATION   pra[3]  cid= 0xe1e2  Msg ID: 0x102 
Private len: 4
IE(0xff00)  Len(0x01)  0x01
Public len: 0




 

Sitemap 1 2 3 4 5 6 7 8 9 10