2400ICS - outgoing caller ID problem

[phadobas]

I have several carriers, each with their own T1-s or ISDN PRI-s for my long distance traffic. Due to recent price changes, I decided to change the routing of my long-distance calls. They now go out on carrier B instead of carrier A now.

Carrier A had no problem sending my caller ID, but now the calls going out through carrier B won't show any caller ID. And a lot of people these days don't answer anonimous calls.

Carrier A had ISDN PRI-s, and I'm using the 24PRT-B cards for them. That's the setup that's working fine.

I connect to Carrier B with a T1 (instead of a PRI), using a 24DTR card. I called carrier B to fix my caller ID problem, but them being a long distance carrier, they told me to call my local carrier (verizon) since Verizon puts out the caller ID. I called Verizon, they said their database is fine. They wanted me to call their CO through this T1. I did. They didn't see caller ID data showing on their phone when I called. They said they would check. They checked, and said I should check my PBX to be sure it's sending them caller ID because they just forward what they get from me.

It's becoming too complicated for me. I checked ARTD for both the PRI (which shows caller ID) and for the T1 (which doesn't show the caller ID). I'm not sure how to test if I'm generating caller ID data, and if yes, where does it get lost...

Any help would be appreciated.

 

[billyd3]

This is a problem with your carrier. There are no settings on a 2400ICS T1 to send caller ID digits. The carrier needs to send the caller ID out on calls out of a NEC 2400 over a traditional T1. We can control digits over a ISDN PRI but not a traditional T1.

 

[HarrisD1200]

Unless I'm reading something incorrectly, Carrier B is really confused. There is no way to send outbound caller ID over a RBS (Robbed Bit Signalling) CASE (Channel Associated Signalling) trunk from the CPE. The Caller ID information is added at the Central Office based on configuration at the CO, then passed on to the outside world. I do configuration on DMS-100, DMS-250 (LD platform), and DMS-500 switches. This is definitely a Carrier B issue.

 

[phadobas]

It's solved. It was carrier B who since fixed the problem. Thank you for your advices.