CS1000 caller ID not being sent outbound local trunks

[issdar]

Hello all,

It has been like pulling teeth working with TELCO. The problem we have is when calling one 1800 number in specific I get a fast busy right away and they call doesnt connect. I was told by the long haul carrier Verizon that the SS7 is rejecting the call because no call presentation.

From Verizon:
Other Comments: Resolve ---worked with tony cust trapped calls.......advised him the calls are being rejected by the far end term end user because his equipment is set up to restrict the calling party number parameter...which is essentially being sent as private or unknown. cust will need to set up his equipment to allow cpn or calling party number parameter if cust wants to call this tf term end user. we cannot force the term end to accept these type calls that are private or restricted unknown.

should show: Address Presentation Allowed

When calling out our local trunks the caller ID displays blocked/unknown. This seems to be the problem of not being able to reach the single 1800 number. So my question is this a problem with the LEC AT&T not outpulsing caller id? I was told we are paying for the caller id service. Calls out the FTS trunks/long distance caller ID displays fine. Is there a setting in the route/rli I need to check that would prevent caller ID from being outpulsed?

Any help would be much appreciated, I am pulling out my hair here

 

[issdar]

I did find this information on

http://www.pbxbook.com

--------------------------
Call Party Name Display (CPND) over a PRI.
For example, on tandem PBX's, the CPND should still work when between stations. Check the RCAP (remote capabilities) in the ADAN DCH, and change it to ND1 (Network Name Display). RCAP is often blank, disabling the feature.

Further information: Calling Line Identification (CLID)
---------------------------

After checking our setting for adan dch 2 which is the local trunks it does not have a value for RCAP. I will try to change this settings after hours.

 

[issdar]

I was told that the RCAP settings is only for Nortel to Nortel systems...I did a enhanced call trace when dialing the 1800 number and the route it takes are attached to post.

 

[issdar]

Issue has been resolved thanks everyone for the help.....

There was two problems,

1. The far end 1800 number had a setting in there IP PBX to not allowed restricted numbers through.

2. After working with the LEC AT&T for a while, they found a setting in there equipment that blocks the outbound caller ID. It was called INCLID and set to Supress.

Now all local trunks have caller ID enabled and can reach the far end 1800 number.

-Tony