bobcheese

what specifically do you need to trace using CCS trace? the command to turn it on is 'ccs trace ena cont' and when you wish to stop it type 'ccs trace dis'.

Tone_the_phone

Thanks Bob
Probably a bit of everything, We have two main sites each with an SX2000 Light set up as a normal PABX, and two set up as transit switches, one on each site. I have been asked to follow inbound DDI traffic from its entry into one site through the transit to the other site to identify which trunks it uses.

bobcheese

then ccs trace is what you need. however, the output is quite confusing as there is alot of data outputted and also it will trace all activity so if 10 call come in at the same time you will have to trawl through the whole output to find the data that refers to your call. Normally the best this to do is to do this out of hours so the switch is less busy and you have less output to search through. Think the is a TIB on mitel on line explaining the CCS trace output.

teltek

You will want to limit the use of this command. It uses an enormous amount of resources. It is meant truly for the d-channel tracing between systems to determine fault conversations for failing calls.

be wary of using this function ongoing ... crash boom bah can go the switch.


***better method is using smdr enabler to a text collector*** this method will allow for vital inter-switch call patterns and with latest feature enablers can identify all voice calls with a master call identifier and sub sequence identifiers for each stage of the call. This is safer and more likely what you would need than ccs trace functions.

hope this helps,
Cheers [[]]D

Tone_the_phone

I had a go at CCs trace and you are right it is very confusing but I couldn't find any reference to analysing it on the Mitel site.
I have seen smdr used for looking up phone numbers that have been receiving or making dodgy calls, from what you say it looks like it can be used for trunks as well as phone numbers.

bobcheese

Found it!

Tone, PM me your email address and i will send you a copy. It was under 3300 docs but is a 3300/sx2000 manual.

Take what Teltek says into account as he obviously knows what he is talking about. I have only ever used it in short sharp bursts so cannot comment on its resource usage.