Analog caller ID vs. T1 1

[speechguy]

I have analog w/caller ID ang get CPN/ANI, i.e. Company Name (in first 26 characters of the 8434 display) and the ANI after (408XXXXXXX)

I don't remember seeing the CPN/name of the caller on T1. I only saw the ANI..


Should I always expect to get CPN/ANI from analog? And should I expect to only get the ANI from T1?

I have not found a way to manipulate analog caller ID on the G3 once it is set for Bellcore. Is there?

I'd like to be able to filter the analog trunks to only display ANI within the first 15 characters of the 7434/8434 set for my integration.

I'm familiar with the ISDN numbering tables T1's. But are'nt they for outbound caller ID?



AT&T/Inter-Tel/Octel/Lucent/Avaya and so on and so on...does it get any better?? ;-)

 

[jgideon]

The NI2 isdn protocol can provide Calling Party Name and Calling Party Number, assuming it is correctly configured and both the PBX and CO will support it. Any number delieverd on a 'plain' T1 (non-isdn) will only display number.

 

[speechguy]

Is calling party name controlled by "US NI Delayed Calling Name Update?" on the trunk group form?

AT&T/Inter-Tel/Octel/Lucent/Avaya and so on and so on...does it get any better?? ;-)

 

[jgideon]

Sounds right... i've always understood that the 'name' appears after the call is answered--the PBX talks to the CO for the lookup after the call actually answers. (I've not actually configured it myself, but have talked with several who have--i'm surprised no one else has chimed in.) Your carrier would have to configure to allow 'name' also.

 

[speechguy]

This is a lab, and I am setting up an integration to the Dialogic card. I see the name/number appear as the call is ringing at the station. I need to manipulate it so that the name would appear after the number because we read the first 24 characters of the display.

Do you know how you could reverse the display to show the number first, then the name?

AT&T/Inter-Tel/Octel/Lucent/Avaya and so on and so on...does it get any better?? ;-)

 

[jgideon]

I don't know that you can. With analog CallerID lines (like in a residence), the receiving CO gets the call setup message, does the database dip to get the name (if there is a billing agreement in place between the two carriers), sets up the voice path, and then rings the subscriber line. The CallerID FSK data is transmitted between the first and second rings as a single message. With ISDN-PRI trunks to a PBX, there is an inbound d-channel message from the CO (or the LD carrier if it is dedicated toll-free inbound), and the Calling Party Number is in that call setup message. It is my understanding that the 'name' retrieval is handled in 'additional information' messages that go between the PBX and CO after the call is actually established. This may happen very quickly (so as to appear to be 'immediate', but I'm not sure what the timing issues are. I would suggest getting a carrier engineer involved. Is the dialogic card going to be provisioned directly to a carrier CO, or is there going to be 'customer' equipment (i.e. a pbx) in between?

 

[jgideon]

You know, this stuff might be in bellcore/telcordia/whomever specs for the NI2 ISDN protocol standards. I don't have access to them, and the cost $$, but maybe you've got funding for that sort of documentation.

 

[TivoNut]

I have an NI2 PRI from SBC (Pacific Bell) in Southern California. SBC can deliver Name over PRI, but it must be PRI-ISDN. I've had it working for over a year on my Definity. When I first configured it, NAME did not appear until the call was answered. However, I quickly figured out that setting:

US NI Delayed Calling Name Update? y

to es (on page 2 of the trunk group screen) caused the name to display while the phone is ringing. Of course, if the number is blocked or restricted, nothing shows on the screen.

 

[speechguy]

jgideon, TivoNut,

Thanks for the feedback/info! The server will always be in an enterprise behind a pbx. I am waiting for SBC to install my T1's, so I don't have them to test yet.

Don

AT&T/Inter-Tel/Octel/Lucent/Avaya and so on and so on...does it get any better?? ;-)