TAC have recommended I activate logging, traces and run a few debugs to troubleshoot an issue I'm having. However whilst I'm comfortable with most of the traces and debugs there are three debug commands to be activated on the CVP VoiceBrowser's that I haven't activated previously.
The debugs in question are to be added onto the CVP VoiceBrowser and are:
- setcalltrace on
- setinterfacetrace on
- seth323trace on
Can anyone tell me just how intensive these are to run in a production environment for a Contact Centre taking approx 8000 calls a day? Would it prudent not to run these during normal working hours (which obviously limits the impact of running them in the first place!)?
With a BHCA around 1600, you should be quite OK - those Voice Browser traces are not too bad. They are binary traces into the .ems file, so unlike Call Server (App Server) traces which are text, you get reasonable performance. I would not have a problem with this.