In bound ANI on definity one T1

[maineflyfisher]

I have a Definity One switch that was installed approx 10 months ago. We use an AT&T T1 for all calls (accept for local outbound). The T1 has 2 truck groups and AT&T swears they are sending ANI down for each call coming in on the T1. When the calls come in all I get for a display on the phones is the group name for the trunk-group the call came down (i.e., trunk-group 1).

AT&T swears it’s being sent and my vendor has never had to change the default settings to make it work so I’m stuck! (BTW, I’m a Computer Network guru not a PBX guru ). I went in and changed one of the trunk-groups and set Incoming Tone (DTMF) ANI from no to both of the available settings (*ANI*DNIS* and ANI*DNIS*), no luck. What's cool is that when I changed the setting and called in to my DID number I got a long pause and then what sounded like an analog dial tone. I quickly change it back. I also noticed a setting on the same page that said, “connected to CO?” and it’s set to no.

Anyone have any idea what I’m missing here? I’m paying $1200 per month for the caller ID and it’s not working.

 

[WHCARon]

Afternoon,

Assuming the T1's are ISDN-PRI then there is nothing in the PBX to control (allow or deny) ANI from being sent to the station.

Hope that helps, WHCARon

 

[maineflyfisher]

Nope, it's not an ISDN-PRI, it's a straight T1 from AT&T with 2 trunk-groups. Thanks.

 

[pduarte]

I believe that inorder for you to have caller ID.
the T1 has to be an ISDN PRI.

 

[dwaings]

Good afternoon...let me preface this by saying I'm not an Avaya person and I work in the Long distance world, primarily on Nortel DMS-250s...and I'm fairly certain that if your local or long distance carrier says they're sending ANISP on all calls, they are probably doing it. The trouble could be with the format it's being sent or in the format you're handling...typical inband DTMF DAL trunk groups are set up by the carrier to transmit *ANI*DNIS...sometimes the PBXs want it *DNIS*ANI,..and typically the carriers can't do that...perhaps calling AT&T and asking them what format they're giving it to you on might help

 

[ScoTTeL]

I think it is possible to configure the definity to show caller Id with T1, but it depends on which circuit pack you are using. The TN767 series does not offer this unless configuring PRI. I believe one of the other boards does. The other thing is your software has to have it enabled. This is part of the customer options setup usually ordered at install, or pay avaya to turn on later through the inads line. I hope this throuws confussion in the arena!! LOL

 

[tadiman]

I'm not an Avaya tech either but I've had similar experiences with an issue similar. First, I have had AT&T tell me that they are sending ANI however that was because the tech looked up the order in the sales databease when he looked it up in the switch, guess what? The other issue I have had happen on three different PBX's is, do you have touch tone receivers available. Again I'm not sure how Avaya works but the caller ID and DNIS are sent as DTMF, so the switch needs DTMF receivers to decode this siganl. One other point, I have 4 T1's in three different locations all with DNIS and caller ID and don't pay anything for caller ID (Qwest).

 

[PBXJay]

The only cost we pay for the Caller ID is the cost of the PRI Ts carrying the D-channel.

 

[NewbieCarol]

MainFLyFisher:

We have a Definity G3siR9 system. We have 3 T1 tie's coming into our switch into one trunk group. They are not ISDN-PRI lines. We just recently started to have the ANI sent down the lines (just the phone number not the name) and it doesn't cost us anything. All we had to change was the Incoming Tone (DTMF) ANI field for that trunk group to *ANI*DNIS* format. BUT that information had to come from our carrier before we knew which format they were going to send it to us in. And, the change was made at the same time the carrier was making the change on their end.

I hope this helps.

Carol