there is a kms article for trace
Title
EX how to capture the equivalent of EDT trace for Mivb
Objective
Use the following steps to capture what the Pri link is seeing on the Mediatrix side of the solution.
How to capture the equivalent of L2L3 trace on the EX controller
The EX does not support the edt trace tsp L2L3 like the MXE3 and CX(i)2’s do as there are no physical plids or trunk numbers.
We need to capture the trace on the Mediatrix side to see what is coming in on the Framer/T1 Module with regard to ANI and DNIS
Environment
EX controller
Mivoice Business
ISDN
Pri
Procedure
1-Login to the EX (Mediatrix) side
2-Under System/Event log
3-The Remote Host will be the IP address of the Laptop or PC which will be running Wireshark
4-For Diagnostic Traces, select Enable
5-For Filter, click on Edit
6-A new box opens, and you will select what it is you want to trace
7-Since we are tracing only ISDN, leave that as the only Module you wish to capture.
NOTE: the next phase of the call routing is SIP so there may be a requirement to enable SIP as well to validate that the DNIS of the Pri is the same as what the invite toward the Mivb contains.
8-Click on apply
9-Click on apply again when you revert back to the previous page.
10-With Wireshark running, make your test call.
Once you have your capture, you need to find the IsdnStackL3Msg for the following categories:
IE Display, IE Calling Party Number, IE Called Party Number
IE Display will show you the NAME
IE Calling Party Number will show the ANI
IE Calling Party Number will show the DNIS
One completed, best practice is to disable the Diagnostic Traces.
If I never did anything I'd never done before , I'd never do anything.....