Remote site Tie with PRI can't complete LD but can Local

[viper222]

Basically we have a third party switch connected to the Opt 11 with a PRI using NI2 to connect them. We can complete station to station calls, we can complete Local calls from the 3rd party switch thru the Opt 11 switch and complete through the PSTN PRI. When we try to complete LD calls the fail. I have posted the IVR systems RDB and then a completed local call and a failed LD call. Any ideas?? It shouldn't have anything to do with Restrictions because I have made an ACDN on the Opt 11 and called it from the 3rd Party switch and it completed to an LD number.

TYPE RDB
CUST 00
DMOD
ROUT 6
DES IVR
TKTP DID
M911_ANI NO
M911_TONE NO
NPID_TBL_NUM 0
SAT NO
IDEF NET
RCLS INT
VTRK NO
DTRK YES
BRIP NO
DGTP PRI
ISDN YES
MODE PRA
IFC NI2
CBCR NO
NCOS 3
SBN NO
PNI 00000
NCNA YES
NCRD YES
CHTY BCH
CPFXS YES
CPUB OFF
DAPC NO
BCOT 0
INTC YES
DSEL VCE
PTYP PRI
AUTO NO
DNIS NO
DCDR NO
ICOG IAO
SRCH LIN
TRMB NO
STEP
ACOD 8706
TCPP NO
PII NO
TARG
CLEN 1
BILN NO
OABS
INST
IDC NO
DCNO 1 *
NDNO 1
DEXT NO
ICIS YES
TIMR ICF 512
OGF 512
EOD 13952
NRD 10112
DDL 70
ODT 4096
RGV 640
FLH 510
GRD 896
SFB 3


PAGE 002

NBS 2048
NBL 4096
DRNG NO
CDR NO
MUS YES
MRT 100
EQAR NO
FRL 0 0
FRL 1 0
FRL 2 0
FRL 3 0
FRL 4 0
FRL 5 0
FRL 6 0
FRL 7 0
TTBL 0
ATAN NO
PLEV 2
MCTS NO
ALRM NO
ART 0
SGRP 0
AACR NO

DES IVR
TN 006 01
TYPE DID
CDEN SD
CUST 0
TRK PRI
PDCA 1
PCML MU
NCOS 3
RTMB 6 1
B-CHANNEL SIGNALING
NITE
STRI/STRO OWK OWK
AST NO
IAPG 0
CLS UNR DTN WTA LPR APN THFD HKD
P10 VNL
TKID
DATE 20 JAN 2007
>
Completed call Local
DCH 9 UIPE_IMSG CC_SETUP_IND REF 0000003A CH 6 12 TOD 11:48:38 CK AD65ED0D
CALLED #:98245333 NUM PLAN: UNKNOWN TON: UNKNOWN
CALLING #:7275515787 NUM PLAN: E164 TON: NATL

DCH 9 UIPE_OMSG CC_PROCEED_REQ REF 0000803A CH 6 12 TOD 11:48:38 CK AD65ED4A

DCH 9 UIPE_OMSG CC_ALERT_REQ REF 0000803A CH 6 12 TOD 11:48:38 CK AD65ED51
PROGRESS: INBAND INFO OR PATTERN IS AVAIL

DCH 9 UIPE_IMSG CC_DISC_IND REF 0000003A CH 6 12 TOD 11:48:44 CK AD660FAA
CAUSE: #16 - NORMAL CALL CLEARING

DCH 9 UIPE_OMSG CC_RELEASE_REQ REF 0000803A CH 6 12 TOD 11:48:44 CK AD660FB3

DCH 9 UIPE_IMSG CC_RELEASE_CONF REF 0000003A CH 6 12 TOD 11:48:44 CK AD66101


Failed LD Call

DCH 9 UIPE_IMSG CC_SETUP_IND REF 0000003C CH 6 14 TOD 11:48:58 CK AD66875A
CALLED #:918133126402 NUM PLAN: E164 TON: NATL
CALLING #:7275515787 NUM PLAN: E164 TON: NATL

DCH 9 UIPE_OMSG CC_REJECT_REQ REF 0000803C CH 6 14 TOD 11:48:58 CK AD668776
CAUSE: #1 - UNASSIGNED NUMBER

 

[pbxn]

IS it just that area code your having an issue with or all LD calls?

 

[viper222]

All LD, actually, it seems 7 digits work it I recieve from the 3rd Party 9xxxxxxx and it works but if I recieve a 10 digit number, which I send out exactly the same via LD 90 RLI , it doesn't work, also if I do 11 digits ie: 91xxxxxxxxxx it doesn't work. But 7 digits works every time. Looking with a TBerd it appears that it isn't trying to even setup the call to the PSTN, it seems to be blocking it AS SOON as it gets the info for the call.

 

[acewarlock]

Where is it blocking, in the originating switch or the tandam switch. Which is the originating switch????

 

[viper222]

The originating switch is the 3rd party. It sends it to the Nortel, and then the Nortel is blocking it immediantly.

The nortel is taking the call from the 3rd party, then tandeming it to the PSTN BUT!!!!! from what it appears, it isn't even trying to tandem the LD calls, just the local 7 digit calls

 

[acewarlock]

What do you dial to make an LD call at the Nortel?

DO you dial a 1?

What NCOS/FRL do you need to make an LD call?

What is the NCOS of the trunk from the 3rd party switch?

 

[viper222]

NCOS for a call is 3, NCOS of the 3rd pary switch is a 3 (if I knew the name, I would tell you, different vendor)

I did a test and made it call an extension the I had forwarded to an LD number, it went thru
I also built a ACDN and had the 3rd party call that number, it then dialed off site and worked LD properly, so wouldn't that mean that my trunks have the sufficient NCOS and also not a conflicting TGAR/TARG. FYI I checked that anyway, the RDB has no TARG so that isn't it.

 

[acewarlock]

is the 3rd party switch sending all the digits needed to make a call off the Nortel?

in other words if you need to dial a 1 on the nortel is the 3rd party switch required to dial a 1 and does it send it to the Nortel?

 

[viper222]

Yes, If I turn on MSGI and MSGO in LD 96, I see 918135551212 for example, I would need to dial 918135551212 from a phone to connect to this number. If I call 98245553 I recieve on my DCH 98245553 which would need to be dialed if using a station. The 7 digit version (98245333) works and completes to this number.

 

[acewarlock]

Is this what you dial from the 3rd party "I see 918135551212 for example, I would need to dial 918135551212 from a phone to connect to this number" ???

I'm confused in what your saying.

What are you dialing where?

What ever you need to dial from the Nortel to make a call, then that's what the other switch need's to dial and pass over the tie to the Nortel plus the 9.

 

[viper222]

Yes, acewarlock, on the distant switch they are dialing 918135551212, then adding a 9 and giving me 918135551212,(I can also see this via the DCH messages)
DCH 9 UIPE_IMSG CC_SETUP_IND REF 0000001B CH 6 4 TOD 15:00:00 CK AEC44D97
CALLED #:918135551212 NUM PLAN: E164 TON: NATL
CALLING #:7275515787 NUM PLAN: E164 TON: NATL

then the call fails, I get this on the Messages:

DCH 9 UIPE_OMSG CC_REJECT_REQ REF 0000801B CH 6 4 TOD 15:00:00 CK AEC44DB6
CAUSE: #1 - UNASSIGNED NUMBER

If I have the distant switch dial 98245333 they insert the 9 and give me 98245333 (also seen on the DCH messages) then the Nortel completes the call fine.

 

[informidicate]

Could you post the RDB and trunk printout for the outbound
PRI on the OPT 11, also the D channel info for both PRI's.

 

[acewarlock]

Then the nortel doesn't want the 1, so you need the 3rd party switch programmed to stop sending the 1.

 

[acewarlock]

Or programm the Nortel LD 90 NPA's to include a 1

you now have LD 90 NPA's entered without the 1 so you need to build new NPA's with the 1

ie: exisiting 824
new NPA 1824 and if your LD vendor doesn't want or need the one, you'll need to to build a DGT /DMI to delete the 1.

all my NPS's except my local NPA's which I have 3 of, all have a 1 in front.

 

[viper222]

UPDATE::: Changing Gears-----

After all of this, I find that it actually has nothing to do with LD versus Local at all. The Local number I was testing with was a DID for an extension in this switch. WHen I called it, the last 4 digits were 5333 so when it rang ext 5333 I thought I was calling out to the DID.

What I have found is I can call (from the IVR unit, which turns out to be using Sip trunks to an AudioCode Gateway) any number 11, 10, 9 or however many digits I want, as long as the last 4 digits is a valid number in the Meridian, it will send my call to that extension. Some reason it is only looking at the last 4.

Now, I can build a ACDN of some extension and set NCFW to an outside number either Local or LD and it will complete.

Basically now I just have to find out why it won't look at all the digits it receives.

Does anyone maybe have a print of their RDB and a Trunk of a working Tie using NI2?? I think that is my problem, the only way I can program the NI2 T1 is DID. COT will work, but won't use the digits coming in to route the call, if I make it TIE it asks CBCR and then wants a RTN and I'm not quite sure how to set that up. Any help is greatly appreciated. Sorry about the wild goose chase from before.

 

[viper222]

Since this has evolved to a different issue, I have reposted so here is the link, if you would like to continue helping, Thanks.

http://www.tek-tips.com/viewthread.cfm?qid=1329483&page=1