09-11-2012
04:34 PM
- last edited on
03-25-2019
09:05 PM
by
ciscomoderator
Prior to upgrading to x7.2 I could set the log levels varying from 1 (least verbose) to 4 (most verbose), where "4' would give me all the call details - which is what I need - whereas after upgrading to x7.2 all I get is the equivalent of "1" - which is not very helpful at all.
Did I miss something - or is this a bug ?
Edit: looks like it's a bug, so guess I'll be downgrading to x7.1
cheers jens
Solved! Go to Solution.
09-13-2012 01:43 AM
Hi Jens,
I've reproduced this and raised a bug. Once it finds it's way in to CDETS I'll make the number available. I've also had a quick chat to the developers about it.
Thanks,
Guy
09-12-2012 04:22 AM
Hi Jens,
I am getting the call details as well. see the below. i am also getting messages related to provisioning and syncing operation between the VCS and TMSPE.
cheers
Alok
09-12-2012 07:51 AM
Hi Jens,
You saw there is also a bug related to X7.2 not showing call detail records in TMS?
So if its TMS not showing the logs, its not related to any log levels on the VCS.
Where do you look, in the logfiles on the filesystem of the vcs, syslog or the webinterface like Alok.
Do you have an example of x7.1 vs. x7.2 and what you lack (and maybe how you use it?)
Please remember to rate helpful responses and identify
09-12-2012 03:28 PM
No, I think you guys have misunderstood me, I'm not talking about "regular" event log" per see, nor CDR in TMS.
When you look at either active calls, or call history on the VCS status, there is the option to view call summary, and on that page you have the options to:
"View media statistics for this call"
"View all details of this call"
"View search details of this call" and the most important one of all (at least for me)
"View all events assoiciated with this call" - which gives you all call details including H.225, Q.931, H.245 signalling etc etc etc
This level of information depends on what the log level has been set as; from 1 to 4 (least to most verbose), depending on how deep you want to get into the call - at least it did prior to x7.2.
I could in x7.2, only get the very basic call information regardless of what the log level has been set to.
I've just downgraded to x7.1 again and the call event log is now back to normal, giving me all the info I need, which happens to be level 4 (most verbose).
/jens
09-13-2012 12:10 AM
Hi Jens,
Could you post examples of the output from X7.1 and X7.2 and what setting you are changing to change the log level. Then I'll go talk to the developers about it and report back.
Cheers,
Guy
09-13-2012 01:34 AM
Log level is set here:
I normally leave this as 4 as I need the details this setting gives me.
Example below of call with log level set to 4 in x7.1 - this is also what I expected to see in x7.2.
Call made with log level set to 1 in x7.1 - this is also all I get in x7.2 with log level set to 4, what I should see is the equivalent detail as above.
/jens
09-13-2012 01:43 AM
Hi Jens,
I've reproduced this and raised a bug. Once it finds it's way in to CDETS I'll make the number available. I've also had a quick chat to the developers about it.
Thanks,
Guy
09-13-2012 01:56 AM
Thanks Guy, that is very much appreciated.
I've downgraded to x7.1 as those logs are invaluable to me, the VCS-E one in particular.
cheers jens
09-13-2012 02:57 AM
No problem, CDETs is CSCuc13370
09-13-2012 03:18 AM
Brilliant
/jens
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide