sundance-communications.com/forum Forums TDM Business Telephone Systems Avaya - Lucent Telephones & Systems Caller ID Output Basics

After searching Google it seems that there's much knowledge on this, here on this forum... I am in need of getting Caller ID info OUT of a Partner ACS 3 system for custom PC Caller ID software, and it seems that this is really more than one issue. I can't find the whole story in one place. So here goes...

1. In my case, is a hardware upgrade needed? Seems like yes, but to what? Is this a card upgrade or a whole unit/module upgrade? Is a firmware upgrade possible (I'm not a Partner expert, and I saw a R6 firmware upgrade available from 1 vendor)

2. I found info on a Partner API PCMCIA card (for R6,7). Seems like it replaces the std backup card and reprograms the SMDR output. Is this necessary, and part of the overall hdwr upgrade? or is it something else?

3. Where does the signal come from? I assume SMDR port and not the RS232 on the Partner Mail module. I tried the pinout info that I saw on this forum, hoping to see at least SOMETHING coming out after a 10-sec phone call as a sanity test... but nothing! So I am also questioning that whole part of the deal. Most serial ports are DB9, so why not a simple SMDR to DB9 pinout spec or adapter. Can't even find the pinout spec for the 355.

4. Is part of this a phone system settings issue? Partner manual info implies I should be getting at least a signal out after a 10-sec phone call.

5. Have had no problems with other phone systems in getting the signal out and in getting SMDR -> DB9 pinouts. In the rest of the inductry this is std information available from the mfr. Seems to be a great mystery with the Partner system (which happens to be our current system!). What am I missing, here?

I am a software developer and not afraid of using a soldering iron, and the lack of a white paper on this topic is a deafening silence. Falls into the "you would think..." category. Help would be appreciated. When I get to the bottom of all this I'll have to write one. Thanks, Greg

Not positive on your question. But here is a stab.

First of all the smdr port I don't think will get you caller id name no matter what the software release number on the Partner. Will have number,time of day.ext,what line,and ect.

The info I have on the smdr output on Partner is:

1200 baud
8 data bits
Xon / Xoff
line feeds
No parity
2 stop bits
Carriage return

But I think I know what you are looking for.

And what you could do is grab that dial tone (asuming you are talking about 1fb's) before they go into the switch.

And reguest that info from your local service provider.

Hope this helps,

Greg:

Are you just trying to capture caller ID information to a printer or to a file using terminal emulation?

If so, this has nothing to do (formally) with the Partner system. You can parallel-connect a caller ID scanner to the CO lines connected to the Partner. Lots of manufacturers make them, but the only part numbers that come to mind are Vodavi's 1480-00 or 7480-00. They have a DB9 connector and will interface with anything.

If you are trying to process caller ID within the Partner system, then I can't help you, though I think your options are limited.

Most serial ports are DB9? I sure see lots of DB25's out there on phone systems, but honestly, some of them are older.

You are correct that the Partner API PCMCIA card will cause the SMDR port to spit out the CID information at the beginning of the call.

And, you will need to flash your R3 to an R6 to be able to use it.

The API card was designed for developers to add "screen pops" for agents. Don't think it has ever sold well, if at all.

Avaya/Lucent/ATT has always used the 355A or 355AF adapter to go from their 8-pin SMDR and/or Programming ports to DB-25. You supply your own 25 to 9 pin adapter if that is what you need.

And if you do a search on this very forum, you will find several messages with pinouts of the 8-pin "RJ-45" to DB-9 adapter.

Thanks for the feedback.
OK, so I need to flash R3->R6. But where does that flashed memory reside... inside the PCMCIA card that I'm replacing with the API card (wouldn't make much sense)? or inside the module itself?

More clarity on what I'm doing...
We have a CallerID integration software package that (among other things) handles screen pop with integration to multiple databases (ie ACT, QuickBooks, SQL/ODBC etc). It works with any TAPI device connected to a PC that has CallerID info(most newer modems, VOIP/SIP) and with devices such as "Whozz Calling" to handle 2-8 phone lines. Yes, the device connects directly to the phone lines. For that situation we have one PC connected to the device which transmits the incoming call info over a TCP/IP port to all listening workstations. No problems - very reliable - and has nothing to do with Partner or any other phone system.

The limitation of that compared with a full CTI system is that the incoming call info cannot be specifically directed to a single extension based on where the call is going. That's where my interest in the Partner SMDR output lies. Other systems spit out messages with info in effect like "call from 856-234-5678, Tom Jones, on Line 2, directed to Ext 14."

So I am sitting at square 1 with Partner ACS because I first need to get SOME SMDR output (on receipt of call - not upon termination) to see what content it has, and when it sends out messages. I would think that ALL of that info would be readily available, as it is for other phone systems, but alas...

This comment by Michael concerns me: "First of all the smdr port I don't think will get you caller id name no matter what the software release number on the Partner. Will have number,time of day.ext,what line,and ect." If that's true, then the Partner Caller ID info isn't even as good as the freeby CallerID devices from Verizon!

Thanks for the help. Will get to the bottom of this with your feedback.

Listen to what Tommy has told you.

-Hal

Tommy,

re: "And if you do a search on this very forum, you will find several messages with pinouts of the 8-pin "RJ-45" to DB-9 adapter"

Thanks - yes I did read them and I tried wiring that way with no success at all - no output from SMDR even after a 10-sec call. The posts I saw were a little ambiguous, though. Not sure if they were specifying the DB25->DB9 wiring or the overall RJ45->DB9 wiring. Will reread.

re: "The API card was designed for developers to add "screen pops" for agents. Don't think it has ever sold well, if at all"

Yes, that's exacly what we're doing. The difference is that our software is not dedicated to a specific back-end database. Most dedicated CallerID fucnctionality embedded into vertical market apps is not extension-specific (doesn't get sent specifically to the workstation receiving the call). For that reason, it is much easier to use a WhozzCalling or similar device because all this hastle isn't worth the couple hundred bucks that the device costs. That's probably why it hasn't sold very well.

But... even if the SMDR content is lame, and extension forwarding info is missing, it's a shame that customers who have bought a several K phone system have to go out and spend even more for such a device just to get CID info out!

The Avaya IP Office has what you are looking for built into it.

Will do pop screen off of caller ID to person you want the call to go to.