Interpreting smdr string 3300 CX MCD 4.0 sp1

[Jakt99]

Hi All

We have a 3rd party app syslog that is monitoring call traffic on a 3300. Trunking on 3300 is basic rate ISDN only so have supervised answer and release signalling. No snalog pstn lines involved. And negates fake answer supervision yes??

The company who has setup syslog has asked why the differences for an outgoing unanswered calls. Sample srings below (sanitised). Call one is the confusing string.

It shows that x944 made a sucessful call to 0415123456 for 9 seconds yet the "A" marker prior to trunk 10 (T010) is not shown.

And call 3, is what I'd expect for an unanswered call, no call duration or "A" marker prefixing the trunk number.

Note I have removed a few spaces from smdr strings so to fit strings on one line (assist with clarity).

1/ O/G call answered or unanswered??
12/06 16:52 00:00:09 944 0415123456 T010

2/ O/G answered call to mobile
12/06 16:57 00:02:54 950 0415123456 A T012

3/ O/G unanswered call mobile:
12/06 16:59 900 0415123456 T013

Any ideas. Am I interpreting strings correctly??

 

[kwbMitel]

When all else fails RTFM.

Call Completion Status (Character 65):
External SMDR (Outgoing Calls): This reports the completion status of an outgoing call in so far as the system is able to determine it. When an outgoing call fails toll-deny checking and is dropped, this field contains a " T". When the trunk group is programmed to receive "Answer Supervision" and a supervision is received, an "A" is reported. When the trunk group is programmed for "Toll Reversal" and a supervision is received, a " T" is reported. A "P" means the call ended because it was preempted by an MLPP call.

A= answer supervision (outgoing)
B= called party busy (incoming)
E= caller error (incoming)
T= Toll-denied (outgoing), TAFAS-answered (incoming) or pickup-answered (incoming)
I= internal call
P= MLPP Preemption

**********************************************
What's most important is that you realise ... There is no spoon.

 

[bobcheese]

I have had this previously with SMDR companies that rely on the 'A' to charge for a call. However, everytime I have looked into this I always gat stuck at the same point. 'A' is not guarenteed from the service provider, even on an answered call.

 

[Jakt99]

Hi Gents

Thanks lads for feedback.

Problem is 99.9& it works perfect Answered OG calls generated in log, are flagging "A" and call duration and 99.9% of unaswered O/G calls don't generate call duration. All BRIs are in the outgoing TG and problem occurs across all individual trunks.

Its the odd call that is confusing the syslog and as bobcheese pointed out the syslog app is relying on "A" being generated to determine an answered call.

Oh and I forgot to mention, sorry big point and should be shot......Problem only occurs on O/G calls to mobile / cell phone calls as far as I can see through the log.

KwbMitel
RE RTFM I like that...Not seen it before....In my Wang days way back in the 80s it used to be RTFS... Found a listing of character fields easy enough on system help but an explanation of values....Not. I tried eng guidelines, tech manual MOL search in knowledge base but drew a blank. I know its somewhere, in front of nose probably and didn't look deep enough......Where did you extract it from.

 

[sarond]

Try the online help.

System Applications/General Business Solutions/SMDR/Description/Summary of Fields Tables

Or you could try the direct file if you have Help install locally.

./sysadmin/features_optional/smdr_summary_of_fields_table.html

This is very useful for any third party developers wanting to create SMDR applications for the 3300.

 

[bobcheese]

Jakt99, it was always mobile calls the caused a problem for me too. I refer you back to my previous post.
Hate to sound defeatest but as I see it not alot you can do.

 

[Jakt99]

Yhanks all

Sarond:
Found the summary of fields, Have on line help loaded on notebook. Obviously missed it....

bobcheese:
hmmmmm Curious only mobiles as well??? Some one else suggested it could be related to a mobile not answering and caller is deverted iys mobile voicemail service or info message which intern plays message and hangs up and the caller isn't charged.

Somewhere along the way the answer / release supervision doesn't play ball in the traditional process sense and I suppose the only way to figure it out what is occuring is monitor with CCS trace or check the monthly telco bill to see if call was registered and charged.

 

[bobcheese]

Jakt99, i doubt the theory about vmail answering because this is still an answer. In my case we decided to put a limit on duration and decided to charge for any call with a duration longer than 10s.

 

[Jakt99]

Bobcheese

Thanks again, your probably right, have asked the client to review the telco bill to confirm if call was in fact charged. At least we will know then if the problem worth perusing or writing off and implementing a work around and as you suggested ignore short calls under a finite time.

I'm having a frustrating debate with the syslog provider, they are insisting that I turn off showing call during for unanswered calls which they don't seem to get it, that I can't...I'm trying to say lets work together on this and determine why its showing up in the 1st place and work a solution.

Every other smdr recording provider I work with, pass along config details as to how they want the mitel smdr options and COS set so they don't have issues. On this occasion the client went out and purchased this system, the provider connected to the 3300 (telnet) without my knowledge. And now complaining to me the mitel's not providing the right info...Fix it...I have asked what smdr options they require set, but as yet have received naught.

I installed the system 12 months ago and configured smdr basically to capture calls to HD, with none of fancy features activated. So as to at least have some trail / diagnostic audit available.

Anyway case closed on my forum question, I have enough info and you lads have been great as usual.

cheers