Call not going through.

[Spzy78]

Ok.. This is bizzare, I have a customer that has a CS1000S running 4.50W software and a single PRI (NI2).

They have ONE number that when they call the phone just disconnects as if it went back on hook. Its a local 552 prefix number. ANY OTHER 552 number, even ones that are pointed to this one particular location's trunk group, go through.. But just this one 552-xxxx number will not. I can dial 552-abcd and it goes through just dandy, but 552-xxxx does not, yet I can call it from a cell phone and it goes through just fine and when called from other locations on our network the calls go through.. The circuit that this number is handed off to also resides on our network so its not like we are going between different provider networks and ciruits. I had the C.O. trace this number but they say they couldn't see us grabbing a BCH on the circuit yet I get DCH messaging to capture the info on the failed calls so I don't see how it can not be grabbing a BCH? Anyways, below I have done a copy and paste of the DCH MSGO info on this particular number. ANY info will be of great help! Thanks!

DCH 15 UIPE_OMSG CC_SETUP_REQ REF 000008D4 CH 12 19 TOD 11:07:58

CK 3A9D1B17
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:371xxxx NUM PLAN: E164 TON: LOCL
CALLED #:552xxxx NUM PLAN: E164 TON: LOCL

DCH 15 UIPE_OMSG CC_RELEASE_REQ REF 000008D4 CH 12 19 TOD

11:08:00 CK 3A9D2256


DCH 15 UIPE_OMSG CC_PROCEED_REQ REF 00009DA8 CH 12 9 TOD 11:08:00

CK 3A9D243C


DCH 15 UIPE_OMSG CC_ALERT_REQ REF 00009DA8 CH 12 9 TOD 11:08:00

CK 3A9D244C
PROGRESS: INBAND INFO OR PATTERN IS AVAIL


DCH 15 UIPE_OMSG CC_SETUP_RESP REF 00009DA8 CH 12 9 TOD 11:08:02

CK 3A9D3711

PROGRESS: TERMINATING END IS NOT ISDN

 

[hskrdean]

We had a similar problem, except it was with dialing a vendor that changed their PBX. Suddenly calls would hang or we would get one-way audio. Our problem was corrected by changing the trunk type in the RDB from VOD to 3VCE.

I've also seen problems like this resolved when you change the DCH class.

 

[Spzy78]

Thanks for the thread!

I would look into those issues (circuit type in RDB and DCH class) BUT, I tested with a PRI tester connected directly into the T1 smart-jack interface thus bypassing the phone system and we get the same results from calling directly from the PRI Tester. I even had a CO tech jack into the DSX panel at our central office and he was getting the same results. He did find some ISDN Protocol 100 error or something to that effect and is going to investigate what he found.

Thanks!!