Author Topic: Logsys...smdr  (Read 7912 times)

Offline evan631

  • Sr. Member
  • ****
  • Posts: 228
  • Karma: +1/-0
    • View Profile
Logsys...smdr
« on: October 19, 2010, 03:27:31 PM »
Could you tell me what some of these entries mean in the SMDR logs

If there is no call timer as in the second entry...what does that mean?

Where the trunk ID is listed...What does the "A" signify?  not all entries have the "A".

Lastly what is the alpha numeric code listed under the trunk signify?

10/19 14:34:15  0000:02:20 6304         1570xxxxxxx               A T120       
                           002   26304                                   E002442
2 A                                                                             
 10/19 14:33:18             6304         1570xxxxxxx             T118       
                           002   26304                                   K002305
0 A                                                                             
 10/19 12:19:04  0000:00:59 T101    0016 6304 2500                   2506       
                           002   570xxxxxx           6300               Q002414
6 A M0020273                                                                   
 10/19 12:18:33  0000:00:15 T101    0001 6300 2500                   2504       
    X 6304                 002   xxxxxxx           6300               M002027

What are some other logs i can look at to troubleshoot problems?  Specifically i am trying to figure out why intermittantly calls are being dialed, but not connecting.  If they hang up and dial again, the call goes through.


Thanks for the help. 
-Evan


Offline bluewhite4

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1041
  • Country: us
  • Karma: +20/-0
    • View Profile
Re: Logsys...smdr
« Reply #1 on: October 19, 2010, 03:32:42 PM »
I thought the A stood for answer, but if you look at SMDR in the help file, it will go over the various colums and their meanings.

What type of trunks are they? I've seen this with CO lines where the system picks-up and out-pulses before the carrier is ready. I usually add a 1 second pause to my digit modification to try and avoid this issue.

Offline evan631

  • Sr. Member
  • ****
  • Posts: 228
  • Karma: +1/-0
    • View Profile
Re: Logsys...smdr
« Reply #2 on: October 19, 2010, 03:39:16 PM »
The lines are PRIs.  Not sure what a CO line is. 

I am not really fluent in the Tele-Com thing.  I basically got thrown into it becuase of the IP phones.

There was a previous post of mine that discussed the issue, but im reviving it.  http://www.mitelforums.com/forum/index.php/topic,1104.0.html  .  I think we left off with doing a reso on the line while it is happening, but unfortunately we cannot do this as it happens to quickly and i am at a offsite from where the issue is happening.

It is happening on various trunks, so tonight we are rebooting the system to see if that helps.




Offline ralph

  • Mitel Forums Admin
  • Hero Member
  • *****
  • Posts: 5767
  • Country: us
  • Karma: +469/-0
  • Published Author: http://amzn.to/2dcYSY5
    • View Profile
Re: Logsys...smdr
« Reply #3 on: October 20, 2010, 08:33:03 AM »

Quote
10/19 14:34:15  0000:02:20 6304         1570xxxxxxx               A T120       
                           002   26304                                   E002442
The "A" in this field means Answer Supervision - the call was answered and a signal was sent back to the 3300 that it was.
In general, this only happens on PRI circs.


                                                                       
Quote
10/19 14:33:18             6304         1570xxxxxxx             T118       
                           002   26304                                   K002305
With a blank in the call duration it means the call was not answered.

                                                                           
Quote
10/19 12:19:04  0000:00:59 T101    0016 6304 2500                   2506       
                           002   570xxxxxx           6300               Q002414
Call came in on trunk 101 with digits 5304, was forwarded to 2500 and answered on port 2506. (Voice Mail?)
The originating caller was from your 570xxxxxxx number.


                                                               
Quote
10/19 12:18:33  0000:00:15 T101    0001 6300 2500                   2504       
    X 6304                 002   xxxxxxx           6300               M002027
Call came in on trunk 101, dialed 6300, forwarded to 2500 and answered on port 2504.   
From there it was transferred to 6304


I reread your original post.   Be sure that internal SMDR is turned on for all phones and trunks in their COS.

Ralph
www.university-music-on-hold.com


Offline evan631

  • Sr. Member
  • ****
  • Posts: 228
  • Karma: +1/-0
    • View Profile
Re: Logsys...smdr
« Reply #4 on: October 20, 2010, 09:15:58 AM »
Thanks Ralph...info is greatly appreciated.

The interesting thing here is of these calls that have 'dead air' and echoes of dialers own voice are showing the 'A'.  I have to see what happens tonight as i believe Mitel reboot the system during the night.



 

Sitemap 1 2 3 4 5 6 7 8 9 10