SMDR error

[pea123]

Have just installed an Mxe & need to check call logs.Have set the SMDR Options Assignment & CoS for both Stations & Trunks.My problem is that the calls do not show when the following command is used:-

logs read smdr all

logs read smdr newest ...

The system response is:-

FILE ERROR: BAD PATH

Can anyone tell me were Im going wrong with the SMDR to log calls.
On command prompt >telnet 192.168.1.2 _1752 the calls show.

 

[Mitelmatt]

logsys read smdr .......

so newest do logsys read smdr newest x

 

[bobcheese]

what about if you open a telnet session to <ip adress of controller>:1752 and make some test calls. If your programming is correct then you should see output.

Not sure if you still need to program application logical port assignment also, depends on how you are collecting the data i suppose.

Also make sure SMDR real time is not set in sys options assignment as when this is set the system doesn't copy the smdr into syslog.

 

[UncleRalph]

AS bobcheese pointed out the real time option is the fix for this as long as the rest of the SMDR options is enabled.

But, jumping on this thread for another reason while speaking of SMDR issues, has anyone else seen the problem in version 9 where the SMDR stops and only spits out the day of the week? i.e. Mon, Tue, Wed etc

At the same time, MiTai stops.
Requires a reboot of the controller to fix.

We've had a handful of sites do this but Mitel says it's not a known issue.

Ralph

 

[slapin]

Running CCM with version 9. Have not seen anything like this.

 

[pea123]

Turning off real time reporting has solved the issue.Smdr now logging fine & sending to the external buffer connected through the printer port.Thanks for all the tips.I have learnt something new about Smdr.