Microcall is showing incoming calls as "INCOMING" instead of the numb

[dgr7]

hello,
In our office we use the Microcall software package with that pc connected by serial cable to a AT&T Definity G3 circa-early-90's PBX. On the reports in Microcall that show, for example, individual call data made for a particular employee both Incoming and Outgoing, the digits of the Outgoing dialed number are shown as well as city, state called, etc. However, the problem we're having is for *all* the Incoming calls, all that is shown is the text "INCOMING". There's no dialed number, city or state given, just the word "INCOMING" repeated in both columns of the report.
We need to get it where the number for incoming calls is shown just as it is now for outgoing. I tried calling Microcall today, but they're on vacation for Memorial Day. My manager thinks what needs to be done is a change somewhere in the settings of the Definity switch. I've tried looking through some .pdf manuals I have on the Definity as well as searching this forum and am not having much luck.

I was hoping someone on here knows what I need to do to get the incoming call number, city, state, etc. call data to display in the Microcall software?

thanks in advance,
david

 

[dfalken]

What kind of trunks do you have? If you don't have T1 PRIs then that is what you will get. If you do I would check with your service provider to see if they are sending you the ANIs

 

[chuck14]

did this work correctly before?

 

[dgr7]

We do have TI PRIs.
There's a person in the office with a Digital Line phone that has a LCD screen, and whenever someone from outside the office calls, she sees the full 10 digits of the number, so I would think that our service provider is transmitting the info to us.
So is there somewhere in the Definity that I need to change a setting for the Incoming on the Microcall reports to change to the actual ANI?
thanks,
david

 

[gblucas]

I don't have MicroCall since I changed jobs last year, but there is a place in MicroCall that you can see the raw data coming from the PBX and what it parses out to be placed into the database. I would check the raw data coming in to the MicroCall system first to see what the PBX is sending and see if the MicroCall system is not seeing the whole number and just using "Incoming" instead. It might even be a setting in the setup of MicroCall. I do know that it will read ANI numbers, because I had more than 10 MicroCall systems and it worked with all my Definity switches from version 6 to CM 3.

gblucas

 

[dgr7]

all,
thank you for your help! With the help of someone on another message board, I went to change system cdr and changed it from "printer" to "unformatted" (not sure why it was on printer to begin with) and now I'm seeing the Incoming phone numbers in Microcall, which I'm happy about. Now, however, I've noticed a different issue, in that when someone for example calls our main phone number, then puts in a 4-digit extension to reach someone's desk, that the Extension that comes out of the Definity is the Auto-Attendant extension, which makes sense, but not that useful. We really need to know the extension inside the company the call went to. I looked at the Raw call data on the Microcall pc (stored in a .txt file) and for the test call I made calling into the office, it showed the Auto-Attendant extension, not my desk phone extension.

Do I need to change from "unformatted" to a different output format? Do I need to make a custom output, and if so, what fields to I put on page 2 for it?

I also notied on that change system cdr screen there's several Y/N type paramaters that I'm not really sure if changing any of them would make a difference as far as getting the Incoming Internal Extension number due to my not understanding the terminology of some of them....

thanks in advance,
david

 

[mikeydidit]

It sounds like you are connectiong through a data module of some sort. I am using MicroCall but chnaged for the data module to the CLAN connection. Here is how that would be laid out and I will look for some of our old Microcall configs for you.

CDR SYSTEM PARAMETERS

Node Number (Local PBX ID): 1 CDR Date Format: month/day
Primary Output Format: expanded Primary Output Endpoint: CDR1
Secondary Output Format:
Use ISDN Layouts? n
Use Enhanced Formats? n Condition Code 'T' For Redirected Calls? n
Modified Circuit ID Display? n Remove # From Called Number? n
Record Outgoing Calls Only? n Intra-switch CDR? y
Suppress CDR for Ineffective Call Attempts? y Outg Trk Call Splitting? y
Disconnect Information in Place of FRL? n Outg Attd Call Record? y
Interworking Feat-flag? y
Force Entry of Acct Code for Calls Marked on Toll Analysis Form? n
Calls to Hunt Group - Record: group-ext
Record Called Vector Directory Number Instead of Group or Member? n
Record Agent ID on Incoming? n Record Agent ID on Outgoing? y
Inc Trk Call Splitting? n
Record Non-Call-Assoc TSC? n Call Record Handling Option: warning
Record Call-Assoc TSC? n Digits to Record for Outgoing Calls: dialed
Privacy - Digits to Hide: 0 CDR Account Code Length: 3

Hell, there are no rules here - we're trying to accomplish something.
Thomas A. Edison

For the best response to a question, read faq690-6594

 

[dgr7]

mikeydidit,

thank you for the helpful Sys Paramaters layout.
I went into our Definity's system paramaters and here's how I have it set since late yesterday afternoon, I put in parentheses some notes.
Some of the entries I didn't have on my screen so I removed them below to show that.
Unfortunately the changes that I made didn't make the internet extension show up in the Raw Call Detail on the Microcall PC. I pasted below what the raw call detail looks like. 843-123-4567 is my cell phone that I'm calling in with. 3334 is the Auto-Attendant extension. What I'm looking for is my desk extension, 2005. I looked at several entries below & above this one in the raw call detail and couldn't find anything refering to 2005 or similar incoming data.

Do you know what further changes I need to make on the Definity PBX for my 2005 extension to appear in the Microcall data?

CDR SYSTEM PARAMETERS

Node Number (Local PBX ID): 1 CDR Date Format: month/day
Primary Output Format: expanded (was unformatted) Primary Output Endpoint: CDR1 (choice not available, left as eia)
Secondary Output Format:
Use ISDN Layouts? n
Use Enhanced Formats? n
Record Outgoing Calls Only? n Intra-switch CDR? y
Suppress CDR for Ineffective Call Attempts? y Outg Trk Call Splitting? y (was N)
Disconnect Information in Place of FRL? n Outg Attd Call Record? y (was N)
Interworking Feat-flag? y (was N)
Force Entry of Acct Code for Calls Marked on Toll Analysis Form? n
Calls to Hunt Group - Record: group-ext (I left as member-ext, thought that was closer to the type of output I want, but maybe I'm wrong about that??)
Record Called Vector Directory Number Instead of Group or Member? n
Record Non-Call-Assoc TSC? n
Record Call-Assoc TSC? n Digits to Record for Outgoing Calls: dialed
Privacy - Digits to Hide: 0 CDR Account Code Length: 3 (was 2)
---------------------------
Microcall pc raw call detail:

0x00000020 [MT]"06/01/07 10:33","SerialPortCollection","AVAYA "
0x00000010 Raw Data:
0x00000011 1027 0008 9 3334 8431234567 0 05 0 704 1 0 0 0 |
0x00000020 AVAYA 24 WORD EXPANDED ISDN G3I INCOMING - Pos1: 1 Pattern1: ddddbddddb?bbnnnbbbbbbnnn
0x00000010 Status: RECORD ACCEPTED
0x00000010
0x00000010 Date/Time Duration Extension Trunk Dialed Number Dir. Call Type Place Called Account Code Authorization Data Source
0x00000010 ----------------- -------- --------- -------- ----------------- ---- --------------- -------------- ----------------- ---------------- --------------------
0x00000012 06/01/07 10:26:12 00:00:36 3334 704 843-123-4567 IN INCOMING ANI CHARSTN SC SerialPortCollection
0x00000010
-----------------------

thanks,
david

 

[mikeydidit]

There are differences between the IP connect and the older data modules connections or serial connected. I looked though what I have from Micro call and it does not show how this PBX is administered. I have a friend that may still be connected like you are. I have a call into him to see if he will send me the CDR screen for you.

Hell, there are no rules here - we're trying to accomplish something.
Thomas A. Edison

For the best response to a question, read faq690-6594

 

[dgr7]

mikeydidit,

thank you for the info and calling your friend. I look forward this his & your assistance.

thanks,
david

 

[mikeydidit]

thread690-1074457

thread690-1355697


These two threads should get you there. I still haven’t heard anything from my friend but I think they have a lot of moves to do today.


Hell, there are no rules here - we're trying to accomplish something.
Thomas A. Edison

For the best response to a question, read faq690-6594

 

[mikeydidit]

Here is the config from my friend. This should get you there. He is running this through a data module.

CDR SYSTEM PARAMETERS



Node Number (Local PBX ID): 1 CDR Date Format: day/month

Primary Output Format: expanded Primary Output Endpoint: 1089

Secondary Output Format:

Use ISDN Layouts? n

Use Enhanced Formats? y Condition Code 'T' For Redirected Calls? n

Modified Circuit ID Display? y Remove # From Called Number? n

Record Outgoing Calls Only? n Intra-switch CDR? y

Suppress CDR for Ineffective Call Attempts? n Outg Trk Call Splitting? y

Disconnect Information in Place of FRL? n Outg Attd Call Record? y

Interworking Feat-flag? y

Force Entry of Acct Code for Calls Marked on Toll Analysis Form? n

Calls to Hunt Group - Record: group-ext

Record Called Vector Directory Number Instead of Group or Member? y



Inc Trk Call Splitting? y Inc Attd Call Record? y

Record Non-Call-Assoc TSC? n Call Record Handling Option: warning

Record Call-Assoc TSC? n Digits to Record for Outgoing Calls: dialed

Privacy - Digits to Hide: 0 CDR Account Code Length: 2


Hell, there are no rules here - we're trying to accomplish something.
Thomas A. Edison

For the best response to a question, read faq690-6594