SMDR

[SCNIPOffice]

Hi,

Calls logged in SMDR records that include queuing have an entry like the following:

2010/10/04 13:11:07,00:00:09,0,2155551212,I,!$Queued;Hunt Group Name,1,0,!$Queued;Hunt Group Name,1,0,,0,1002632,0,E5200,Hunt Group Name,T9001,Line 1.0,0,0,,,,,,,,,,,,,

Compared to:

2010/10/04 13:09:12,00:02:07,2,92125551212,I,5100,2550,,0,1002630,0,E1108,User1,T9001,Line 1.3,0,0,,,,,,,,,,,,,

The issue is that !$Queued;Hunt Group Name,1,0 appears to be the value in the Called Number field, however the value contains commas that make the CSV output useless for these lines. Any ideas on how to squeltch these or handle this issue?

What do others do with SMDR files to csv?

 

[SCNIPOffice]

How do most SMDR applications handle these records? Is this a unique situation that doesn't compare to what most people do with SMDR?

 

[hairlessupportmonkey]

need some more info?

version switch? version delta server?

 

[TomMills]

make sure your delta server is the latest version, otherwise you'll be partying like it's 1899.

http://www.twitter.com/tem1985

ACSS-SME
fo shizzle ma nizzle.

 

[SCNIPOffice]

IP office is 500 v 2, we're looking at the raw SMDR records. No delta server.

 

[SCNIPOffice]

FW 6.0(14)

 

[SCNIPOffice]

I'm thinking that what I'll need to do to get usable records is first import the SMDR output into a temp table and then check the value for each row for a queuing entry.

If there's an entry, manipulate the values to get them in the correct column.

It seems surprising that no one else has encountered this, but maybe CCR deals with this automagically and that's how most installs use SMDR data if at all?

 

[Bas1234]

On the HuntGroup / Announcements is the option "Flag call as answered" ticked? Try to untick the option.

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged
___________________________________________

 

[SCNIPOffice]

No, VM pro isn't setup to flag the call as answered when the queue start point fires.

 

[Bas1234]

Not in VMPro...in the Avaya Manager.

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged
___________________________________________

 

[SCNIPOffice]

Also no there. Incidentally, from the help:

Note that a call becomes connected when the first announcement is played to it. That connected state is signaled to the call provider who may start billing at that point. The call will also be recorded as answered within the IP Office SMDR output once the first announcement is played.

 

[Westi]

seems that the field that has teh information in it is number 6 and the knowledgebase says the following

6. Called Number
This is the number called by the IP Office. For a call that is transferred, this field shows the original called number, not the number of the party who transferred the call.

• Internal calls: The extension, group or short code called.

• Inbound calls: The target extension number for the call.

• Outbound calls: The dialed digits.

• Voice Mail: Calls to a user's own voicemail mailbox.
then you see the next entry is the same

7. Dialled Number
For internal calls and outbound calls, this is identical to the Called Number above. For inbound calls, this is the DID of the incoming call.

look how you send these calls to the voicemail or huntgroup and you might be able to change the way the SMDR prints it out
the knowledgebase shortcut is here

http://marketingtools.avaya.com/kno...office/mergedProjects/manager/smdr_fields.htm

Joe W.

FHandw., ACSS

insanity is just a state of mind

 

[SCNIPOffice]

Thanks Westi,

This happens just by enabling queuing on the huntgroup. Are there multiple ways to deal with queuing?

 

[Westi]

not really queuing is just the checkmark, I have not had this because only few customers are actually using SMDR.
I guess you could try to open a ticket with Avaya or if you have the possibility test it on different releases to see if it is the same on all of them.


Joe W.

FHandw., ACSS

insanity is just a state of mind

 

[SCNIPOffice]

I'm writing code to parse the values of the affected columns, split by the commas to see if they contain queuing information. If so, I combine the next two columns back with the original.

I wonder how Avaya's software uses SMDR data. Maybe they use some sort of proprietary communication instead.

Or maybe it's just not tested?

 

[IPGuru]

I suspect not tested
Avaya do not produce a call logger app.
I suspect the developer who added the queue information did not think about how it would affect the applications that read it


I do not Have A.D.D. im just easily, Hey look a Squirrel!