PRI Call being rejected

[hawks]

New PRI and when I call in the call gets rejected and the following is the message I get.

DCH 3 UIPE_IMSG CC_SETUP_IND REF 0002 CH 0 TOD 15:53:50
CALLED #:5573 NUM PLAN: UNKNOWN
PROGRESS: CALL IS NOT END TO END ISDN
CALLING #:7275765001 NUM PLAN: E164

 

[johnpoole]

and 5573 is a good number in the switch? not a dsc or something else across a trunk? the msg does not look like a rejected call, not isdn end to end is on almost every call.. num plan unknown looks more like the switch can't find 5573 or it's forwarded to a restricted number

john poole
bellsouth business
columbia,sc

 

[hawks]

The 5573 is an extension that we put on a phone for testing. When trying to dial out over the circuit I get a re-order tone and the following message. (there are numbers where the x's are)

DCH 3 UIPE_OMSG CC_SETUP_REQ REF 0017 CH 2 23 TOD 16:25:46
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:3484 NUM PLAN: E164
CALLED #:1xxxxxx2027 NUM PLAN: E164

DCH 3 UIPE_IMSG CC_RELEASE_IND REF 0017 CH 2 23 TOD 16:25:48
CAUSE: #101 - MSG NOT COMPAT WITH CALL

 

[a12ozbottle]

could be interface type...what type of co switch are you connected to and what is the ifc on the dchannel

 

[a12ozbottle]

If you are connected to a nortel co switch like a dms100 then you must use d100 and the co must use the sl1 interface type.

 

[hawks]

I'll check that. I went ahead a changed the RCAP to ND2 just to what happens. Now when calling in I get the following.

DCH 3 UIPE_IMSG CC_SETUP_IND REF 0002 CH 0 TOD 16:54:24
CALLED #:5573 NUM PLAN: UNKNOWN
PROGRESS: CALL IS NOT END TO END ISDN
CALLING #:7275765001 NUM PLAN: E164

DCH 3 UIPE_OMSG CC_REJECT_REQ REF 8002 CH 2 1 TOD 16:54:24
CAUSE: #31 - NORMAL UNSPECIFIED

 

[markbellot]

Post the route data block. Check DSEL in the RDB.

 

[hawks]

Mark I tried changing the DSEL but I get this error code when I do.
SCH6177 = (TDN or VOD can only be selected for PRI

When I prt the RDB it does not even show the DSEL prombt, one thing I forgot to mention is this is RLS 21 software. Although I did not know it should make any difference.
Anything else to look at, right now I have the RDB set up as DID should I try it as TIE? The span is up and running with no errors until you try to put a call on it. If anyone still would like to see the RDB I'll be glad to post it.

 

[hawks]

Ok here is the RDB and TN information can anyone see anything I'm missing? Thanks for all the help.

TYPE RDB
CUST 00
DMOD
ROUT 0
TKTP DID
M911_ANI NO
NPID_TBL_NUM 0
SAT NO
RCLS EXT
DTRK YES
DGTP PRI
ISDN YES
DTC103
MODE PRA
IFC NI2
SBN NO
PNI 00001
NCNA YES
NCRD YES
CHTY BCH
ISAR NO
PTYP PRI
AUTO NO
DNIS NO
DCDR NO
ICOG IAO
RANX NO
SRCH LIN
TRMB YES
STEP
ACOD xxxx
TCPP NO
TARG
BILN NO
OABS
INST
TIMR ICF 512
OGF 512
EOD 13952
NRD 10112
DDL 70
ODT 4096
RGV 640
FLH 510
GRD 896
SFB 3
NBS 2048
NBL 4096
NRAG 30
TFD 0
DRNG NO
CDR NO
MUS NO
MR NO
RACD NO
EQAR NO
OHQ NO
OHQT 00
TTBL 0
PLEV 2
MCTS NO
ALRM NO
ART 0

PAGE 002

SGRP 0 (this is where the prt stops again I think it is because of it being RLS 21)

TN 002 01
TYPE DID
CDEN SD
CUST 0
NCOS 0
RTMB 0 1
B-CHANNEL SIGNALING
NITE
STRI/STRO OWK OWK
CLS UNR DTN WTA LPR APN THFD HKD
P10 VNL
TKID
DATE 17 NOV 2006

 

[hawks]

Ok after more changes and working with the carrier it turns out to be the CLID that is stopping inbound. If the CO sends name or number the call will not complete. But if the CO turns off name and number info then the call will complete. My problem now is changing the CLID info on RLS 21. The oldest books I have are for RLS 25 and you don't get some of the same prombts.

 

[janaya]

Did Release 21 support NI2 format?

I believe there were some limitation on Release 21 regarding the type of card you had to use, and also I think you have to have a downloadable Dchannel to get it to work.

NI-2 functionality didn't really start getting good until Release 22, but you were limited to Release F QPC720's.

Are you using QPC720s or are you using NT5D12's

John

 

[hawks]

I'm using the NTAK09 with the NTBK51 (downloadable Dchannel card) on an Option 11. I get the calls to come in now but with no caller ID information. I still have not been able to call out I get the following error from my D-Channel Message. Thanks for the help

DCH 3 UIPE_IMSG CC_RELEASE_IND REF 0017 CH 2 23 TOD 16:25:48
CAUSE: #101 - MSG NOT COMPAT WITH CALL

 

[a12ozbottle]

Did you ever find the fix for this?
If so, what was it?

 

[vztech]

Who is the carrier ?
Try this in LD 90 prt the NPA you are trying and find the RLI( make a Note)
Ld 86 create a DMI Delete 0 Insert 0 CTYP make National
add the DMI to your RLB in LD 86

and make the call on a set that is UNR in CLS
Dial the ACOD of that Route
and make sure Targ is none (which I see it is in your RDB prt out)

It's only dialtone-VZ

 

[jjinkins]

Do you have a CLID table set up? Many carriers won't allow outbound dialing if you aren't sending a number that matches one in their database.

 

[hawks]

sorry guys I posted the results in thread798-1306368 turns out it was the carrier...

All is right in the world now thanks for all the help. It turns out (like normal) the carrier had something set wrong. They swore that they were set as NI2 and were seeing problems so then they set it as DMS 100 and everything cleared up. So I re-programmed my side as DMS 100 then everything would not work again. Then I switched mine back to NI2 and now we are running clean for about 30hrs. John the calling number ID does work with Rls 21 thanks again.