Shown below is some data received from a Partner system. The real-time format. Could someone assist me in understanding all the fields. Specifically the codes in the 1st column.

Thank you.


R 05 09/16 10:42:54 5701234567 UNAVAILABLE 000000
A 05 15 09/16 10:42:59 5701234567 UNAVAILABLE 000005
G 05 15 09/16 10:43:07 5701234567 UNAVAILABLE 000013
F 02 10 09/16 10:50:15 000000

O 02 10 09/16 10:50:25 973328 000010
G 02 10 09/16 10:50:27 973328 000012
F 01 10 09/16 10:50:27 000000
G 01 10 09/16 10:50:28 000000
F 02 10 09/16 10:50:28 000000
R 05 09/16 10:50:40 9731234567 UNAVAILABLE 000000
G 02 10 09/16 10:50:40
G 02 10 09/16 10:50:40
F 01 15 09/16 10:50:41 000000
D 05 09/16 10:50:42 9731234567 UNAVAILABLE 000002
G 01 15 09/16 10:50:43 000002

Good day
Thank you for visiting ,kindly complete your profile so we Know who we are helping.

When you say real time do you mean that the system has an API card in it?

ttech
I think hes looking for an explanation of the codes like the alpha A/F/G etc then the meaning of the rest

The date time is obvious and i could only find f meant speed dial ,i assume the next is co line /then it looks like timer phone #

How are you obtaining this data? Using the API card or just the standard output from the SMDR port?

Thanks,

-jr

>How are you obtaining this data? Using the API >card or just the standard output from the SMDR >port?

I am obtaining this data via the API card (which I believe is a PCMCIA card?)

Thanks,
Terry.

Thanks. I think the only way you will be able to determine this (if Avaya doesn't have a document which describes it, I couldn't find one) is to just watch the output and start making phone calls, interacting with the system.

-jr

>Thanks. I think the only way you will be able to determine this (if Avaya doesn't have a document
>which describes it, I couldn't find one) is to just watch the output and start making phone calls, interacting with the system.

I couldn't find anything from Avaya... and my problem is compounded that I'm on the west coast and the phone system is on the east coast.

Terry.

Perhaps they should use an Avaya dealer in their area rather relying on you.

-Hal

>Perhaps they should use an Avaya dealer in their area rather relying on you.

We tried that first but the dealer knows nothing... (just getting the data to a COM port was a challange)

The lack of documentation from Avaya is no help either.

Thanks again for everyone's response.
Terry.

Ahh but there is documentation. Look under SMDR. Question is why are you getting the jiberish that you have? Check that your communications parameters are set properly. It's in there!

-Hal

I don't think that is jiberish. I think it is just newline seperated records. If the comm params were off it wouldn't be the ascii characters with dates, the word UNAVAILABLE, etc.

I've looked under SMDR, called Avaya been passed around to 5 different people and no joy.

If anyone can provide a link do a documentat which says what the record types are it would be helpful.

My analysis so far is:

First column is some type of type code. This
likely defines the other columsn in the record.

The second file the CO line?

For the "A" type (answered maybe?) the 3rd field
appears to be the extension.

Date/time obvious.
called id is obvious.

The last field I have no clue.


R 05 09/16 10:42:54 5701234567 UNAVAILABLE 000000
A 05 15 09/16 10:42:59 5701234567 UNAVAILABLE 000005
G 05 15 09/16 10:43:07 5701234567 UNAVAILABLE 000013
F 02 10 09/16 10:50:15 000000

O 02 10 09/16 10:50:25 973328 000010
G 02 10 09/16 10:50:27 973328 000012
F 01 10 09/16 10:50:27 000000
G 01 10 09/16 10:50:28 000000
F 02 10 09/16 10:50:28 000000
R 05 09/16 10:50:40 9731234567 UNAVAILABLE 000000
G 02 10 09/16 10:50:40
G 02 10 09/16 10:50:40
F 01 15 09/16 10:50:41 000000
D 05 09/16 10:50:42 9731234567 UNAVAILABLE 000002
G 01 15 09/16 10:50:43 000002

Are the calls being answered by Auto Atten. by chance? They kind of look like AA codes to me, I don't recognize them either and can't find anything on them in the SMDR manuals just I=incoming and C=outgoing

Starting at page 9-34 in the Partner ACS R6.0 and earlier documentation. "Station Message Detail Recording (SMDR)".

Yes, looks like your communications are OK but the information is not according to the documentation. Columns from left to right should be:"C" for outgoing or "I" for incoming, date, time, number, duration, line, station, account.

There can be different ways the number can be displayed depending on whether it is outgoing, marked speed dial or CID on incoming but what you show is nothing like what it is supposed to be. The letters in the first column should only be "C" or "I" for instance.

The thought does occur, are you absolutely sure that this is a Partner system?

Hey Tommy, does this look like the SMDR output of a Legend or Magix?

-Hal

Hal
As far as I know the Legend uses I and C also, I have no idea what his letters mean. TTT or gkar may chime in and enlighten use
all.

Hey guys, James tells us that it is a Partner with the API card installed. That means that this stuff is coming out of the SMDR port at the BEGINNING of the call. The purpose is to get the incoming caller ID send to some kind of server and provide a screen pop for whoever answers the call. That way, they will have the customer's info on the screen when they answer.

That's the theory behind it, but never having seen it in real life (and apparently no one at Avaya has either), it's going to take experimentation on James' part to figure it out.

The greatest problem is geographical, with James being located on the west and the operating switch on the east.

James, since it isn't doing anything for the customer at this point, perhaps they could pull the card, ship it to you to put in a test system, and you would have a chance to corrolate the info produced with test calls? And once you figure it all out, you're in a great position to be a consultant for this type of application.

I'd be happy to track down the specifics. I am going to be ordering in a partner system here shortly. I guess I can also try and get the API Card too.. Once I have that in hand I can set it up on the bench and start watching the output and making calls.

Sure would be easier if someone at avaya could just tell us what they mean though.. afterall they wrote it. :-)

-jr

I've been talking with Avaya re: obtaining the format for this output, and they say that..

"At this point, an SDK has not been made available by our product teams
to the Developer Community or DevConnect Program, so joining at a higher
level will not provide you with any value for this situation."

So, I guess that means that the format of the output is not yet available.

owell. I tried.

-jr