TN767 -> TN464/TN2464?

[Moshimoshi]

Hey, my setup is a Definity G3r backed by Dual S8700's (note: not s8710/s8720) and CM2.1.1, and we're looking at setting up PRI, I might have asked this before, but can't remember and couldn't find the thread.

Am I going to have to replace all of my current DID circuit packs to get D-channel Caller ID on the new PRI trunks Qwest is setting up?

Current packs are variants of TN767 it looks like. Is getting TN464 and/or TN2464's a requirement?

Also would like to replace our single-pair copper CO Trunks so that some (most) are able to pull Caller ID data as well, and I'm assuming there we move from TN747's to TN429D?

Thanks in advance, sorry if this is a repeat of something I asked earlier.

 

[Mitch672]

you are correct on both issues.

You need TN464's of some version to support the ISDN D-Channel, once you move to an S-Series server.

You also need TN429's to support Caller ID.

You could add some G700 or G350 media gateways to your system, and use MM711 cards, which will probably cost less than buying TN429 circuit packs, MM711 also supports Caller ID This assumes your switch is IP enabled (you have 1 or more TN799DP CLANs, and 1 or more TN2302AP MEDPROs)

Mitch

AVAYA Certified Specialist

 

[Moshimoshi]

Monetary constraints have been imposed, so trying to pick up some new G350's probably won't float for right now.

Note also we're not using the DIOD trunks as a replacement for analog caller ID, just to trunk lines from the CO that support sending that information so that it gets into our system...

there's a TN analog card, who's number escapes me that supports User-Analog Caller ID, the plan was to get all the CO/TIE and DID into a position its able to pull CallerID and 911 data (two-way) so digital all got caller id from outside, people outside got caller id from inside, and we could add some limited support of analog caller-ID from within the pbx.

Or am I missing something...

 

[Mitch672]

First of all, Analog Caller ID is Horribly, Horriby slow. It will delay each call answered by about 10 seconds.

2nd of all, Analog CallerID is not a substitue for a PRI, PRI's are much faster, and the Calling Party Number arrives digitally, so its much faster.

Like I said, you could put your POTS lines on TN429 cards, however, last I checked they where $2400 each. Of you could use G700's or G350's and use MM711's card for the same job. They are more affordable, and frankly they are the direction AVAYA is moving in (H248 Media Gateways and MM cards)

And yes, you need TN464s of some type to terminate ISDN PRI's, TN767s won't cut it.

Mitch


AVAYA Certified Specialist

 

[Moshimoshi]

Mitch,

Thanks for the feedback - I understand that the Analog Caller ID process is slow, we don't have many POTS/CO copper terminating to CO Trunks as it is, and the price for the

Also I wasn't talking about using Analog Caller ID as a substitute for PRI, I was looking our existing trunks to equipment that supported Caller ID with our existing hardware. TN429d's seem to be floating around in the $800 area right now, so I'm not to concerned there, and they're 'adhoc' to the overall request of moving our DID to PRI.

So the summary was...

Swap 767s to 464's
Swap 747s to 429d's

and I was wondering if anything needed to happen with TN722B's for that matter.

Hope we're on the same page now!

I'm in a crunch to get some numbers around for capital budget before Friday

 

[Mitch672]

TN722B's I don't think support CallerID (ability to SEND this to an internal phone), I thnk you wuold need to get TN793B or TM793CPs for that, that would be my best guestimate. However, do you really need the ability to SEND CallerID to analog phones internally?

Mitch


AVAYA Certified Specialist

 

[Moshimoshi]

I must be confused on something fundamental here.

Everything in this thread is about interfacing with our CO properly to get CallerID from them and what hardware we need for that data to flow into our system.

It was my understanding that PRI would feed this data on a D-channel for all of our DID stuff. So thats taken care of by updating to PRI capable 464s

We have several numbers that terminate a single pair of copper to a CO Trunk as they come in, which currently can't accept a caller-ID and broadcast it inside at all, so that people inside our PBX, receiving a call from one of these CO-trunked numbers, cannot see who is calling, thats not what we want, we want to see the 'rest of the world' so to speak, hence the initial suggestion of changing our 747's to 429d DIOD

The last item were we have two 722B's acting as a feeder service from sprint in our system as "Sprint/Sprint Zero+" that provide incoming services from Sprint, we also don't get any ID on those calls as they come in, we want to be able to see who is calling from them.

Essentially, if someone can call in, we want to be able to see the ANI if its available from the CO provider.

However it sounds like you're talking about swapping 722B TIES to 793B/CP analog trunks, and now I'm afraid I'm completely lost.

Haha..well this wasn't supposed to be so confusing so I apologize. What do I need to change to make inbound caller ID (and Outbound Caller-ID) happen on all of our numbers flowing in, and all (or most) of them flowing out?

 

[Mitch672]

Ah, my bad, I thought TN729 was an older analog station card. Turns out its an older T1/DS1 card... so again, that would have to be replaced with TN464's, but, unless those circuits are converted over to PRI's, you won't be getting any CallerID from it.

TN793 can GENERATE CallerID, if you have Analog phones internally with CallerID, and you want to pass the information through to them, that's what the last post was about. Ignore that if you have all digital phones internally.

Mitch


AVAYA Certified Specialist