You can use a maint command to look at the SMDR logs (you will have to ensure that the appropriate log has been turned on though - Report outgoing calls set to yes- I think this is found in the SMDR options assignment form, or something to that effect). The command will be:
Logs read sndr all match xxxx (xxxx being the extn)
Aside from this I think a dedicated call logger will be best
Thanks very much that looks to be working great. Where can I find out what the headings of the columns should be and what the various letters stand for. It seems to be that incoming calls are on two lines and external are on a single line.
06/24 09:51A 00:00:18 T008 003 800 0 T 807
xxxx427071 800
06/24 09:51A 00:00:03 807 xxxxx427071 T002
06/24 09:49A 00:00:04 T007 005 807 807
xxxx427071 807
06/23 01:27P 00:00:03 807 xxx651 A T001
06/23 12:23P 00:00:03 807 123 A T001
06/23 12:22P 00:00:03 807 123 A T001
06/23 12:09P 00:01:49 807 xxx322 A T001
06/23 11:31A 807 425388 T003
06/20 04:05P 00:04:07 T008 003 800 T 802 T 807
For reports i think you need call accounting software
ACA - Implement IP Office
ACS - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
If you don't have a Mitel online account then you might not be ablt to download it. I got my MOL account by joining the user group which is free for the first part year...
I know this thread is old and apologies for bringing it back.
I was looking for a free call logging system a while back (we are a high school with very limited funds) so in the end I set about writing my own.
If anyone would like to try it, its available at
(no its not commercial software and yes I own the site, sorry for the advertising!) It may work for you or it may need tweaking to work, I've only had our 3300MX to test with so it may fail miserably as the settings will most probably be different.
Hi, i have another question:
When opening a telnet-session to port 1752 (or a direct serial connection) we get real-time call logging. BUT when the telnet session accidentally gets closed, data gets lost because the next time the telnet session is opened we don't get the buffered call logging data. Now is it possible to access the internal buffer through a telnet connection instead of collecting the data through the logsys command or through the OPS?
Thanks for your answer J.
Hi kwbMitel,
The issue is that when the telnet session gets disconnected for whatever reason, the data gets lost because there's no buffer. The data is sent real-time on port 1752.
So i wonder if the call logging data is buffered somewhere on the MITEL and if we can access this buffer through telnet. J.
You may have the Real-time SMDR options enabled.In the web admin go to System Administration > System Options > SMDR Assignment and check if SMDR Real Time Reporting is set.
Not sure if that is the problem but it cant hurt to check
You say the Mitel buffers up to 20,000 records and once they are collected via port 1752 they are removed from the Mitel.
The problem is I can't access these buffered records by port 1752!
When i make a connection to port 1752 i don't get the buffered call records but ONLY the real-time call information?! Am i doing something wrong here?
J.
Hi, after lot of testing I found the problem.
We programmed in Application Logical port Assignment:SMDR Logs => continous => LPR1 and then apparently ONLY real time reporting is done...
When removing this line, we can acces the buffer next time we make a connection to the port 1752.
Thanks all for your help!
Regards, J.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.