Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SMDR call record missing extension number

Status
Not open for further replies.

PREPAPBX

Programmer
Jul 10, 2009
17
PR
We have several NEC 2400 IPX switches interconnected with T1's. All PBX's are programmed so that all the call info is sent to the centralized PBX (via CCIS) that is connected to the call accounting system. All is working fine except for the internal incoming calls within the PBX network. The report shows all call info (time, length, route, trunk, etc.) but not the extension number that called. After examining the raw data send by the PBX we noticed that it just doesn't include the extension number Also, is it possible for the PBX to generate call records for calls made within the same PBX? Thanks.
 
Internal (station to station SMDR) is set up with ASFC, SFI 58 = 1, and ASYD Sys 2, index 3, bit 7 = 1
 
Thanks for the quick response.

All PBX's have ASFC, SFI 58 = 1, and ASYD Sys 2, index 3, bit 7 = 1

Maybe something in ARTD?
 
Our CCIS routes have smdr 1 and 2 (CDN 10 and 16 in ARTD) flagged as 1 and it works for us.

"However beautiful the strategy, you should occasionally look at the results." Sir Winston Churchill
 
Same here. All CCIS routes have SMDR1 (CDN 10) and SMDR2 (CDN 16) flagged as 1 in ARTD, including the Least Cost Routing (LSR) Route (Rt. 63 in our case).
 
Here are some more areas to check:

Before you change any settings i would highly recommend documenting your current settings in the ASYD and ASYDL indexes referenced below.

**33. In a CCIS environment if a node has a PHC and IPTRK coexisting that node cannot be the centralize point
for call accounting.

[Common Data]
ASYD System Data 1 Indexes 32, 34
System Data 2 Index 3
ASYDL System Data 1 Index 576 Assign Bit 2 = 1, when using LAN interface for SMDR.
[Node A]
ASYD System Data 1 Index 180 Assign the PC of Node A.
Indexes 288 Assign when RS-232C output is used.
ASYDL System Data 1 Index 577 Assign 00H.
Indexes 578 Assign when LAN output is used. (Bit 4** of each Index)
** Note: When using LAN Interface for SMDR, a TCP/IP LAN Address, Subnet Mask Address, and Gateway
Address must be assigned to the Active CPU. Use either ASYDL, Sys-1, Indexes 515 through 526 to assign these
addresses or the ADTM command.
[Node B]
ASYD System Data 1 Index 180 Assign the PC of Node B.
Index 182 Assign the PC of Node C.
Indexes 288 - 295 Assign all 00H.
ASYDL System Data 1 Index 577 Assign 00H.
Indexes 578 - 581 Assign all 00H.
[Node C]
ASYD System Data 1 Index 180 Assign the PC of Node C.
Indexes 288 - 295 Assign when RS-232C output is used.
ASYDL System Data 1 Index 578 Assign when LAN output is used. (Bit 4** of each Index)

If you would like we can compare settings in asyd and asydl.

"However beautiful the strategy, you should occasionally look at the results." Sir Winston Churchill
 
Thanks for the info. I'll work on this on Monday and give feedback. If this doesn't work, I'll make a file for the ASYD and ASYDL commands so we can compare. Thanks again.
 
Sorry I was gone for so long. I programmed everything NECPBXtech30 suggested and we are finally getting the call records within the same PBX (station to station). Incoming extension info from the PBX network was not working. I contacted NEC's tech support and after working with them for a couple of days, they stated that it couldn't be done. So, the call accounting company created the records from the outgoing call record. All is good. Thanks for all your help.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top