Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Unable to call out on a new PRI

Status
Not open for further replies.

sromero

IS-IT--Management
Mar 13, 2002
15
US
Your help will be appreciated!

I have an Option 61C with two working PRI's for local DID inbound and outbound traffic.

We recently changed carriers but I have not been able to complete the cutover, when we try to cut the carrier is able to complete the call using a test DID number that they provided but I am unable to call out, I immediately get a reorder tone.

I’m using the same PRI cards, same loops and route, the only thing I did was change the interface cables at the smart jack from one carrier to the other.

I know this is a lot for a first question but I’m desperate.

The new T1’s are configured:
T1 FRAMING/CODING ESF/B8ZS
CO PROTOCOL ATT
DIGITS DELIVERED 4
PULSE TYPE: DTMF


TN 025 01
TYPE TIE
CDEN SD
CUST 0
NCOS 7
RTMB 2 24
B-CHANNEL SIGNALING
TGAR 0
AST NO
IAPG 0
CLS UNR DTN WTA LPR APN THFD HKD
P10 VNL
TKID
DATE 19 JUN 2000

TYPE RDB
CUST 00
ROUT 2
DES MCIPRI
TKTP TIE
ESN NO
CNVT NO
SAT NO
RCLS EXT
DTRK YES
DGTP PRI
ISDN YES
MODE PRA
IFC ESS5
SBN NO
PNI 00000
SRVC NNSF
NCNA YES
NCRD YES
CHTY BCH
CTYP UKWN
INAC NO
ISAR NO
TGAR 1
BCOT 256
DSEL VOD
PTYP PRI
AUTO NO
DNIS NO
ICOG IAO
SRCH LIN
TRMB YES
STEP
ACOD 7002
TCPP NO
PII NO
TARG
CLEN 1
BILN NO
OABS
INST
IDC NO
DCNO 0 *
NDNO 0
DEXT NO
ANTK
SIGO STD
ICIS YES
TIMR ICF 512
OGF 512
EOD 13952
NRD 10112
DDL 70
ODT 4096
RGV 640
GRD 896
SFB 3
NBS 2048
NBL 4096
TFD 0
DRNG NO
CDR YES
INC YES
LAST NO
QREC NO
OAL YES
AIA YES
OAN NO
OPD NO
NATL YES
MUS YES
MRT 8
FRL 0 0
FRL 1 0
FRL 2 0
FRL 3 0
FRL 4 0
FRL 5 0
FRL 6 0
FRL 7 0
OHQ NO
OHQT 00
CBQ NO
AUTH NO
TTBL 0
PLEV 2
ALRM NO
ART 0
SGRP 0
AACR NO

TYPE TLS
TKTP TIE
ROUT 2
DES MCIPRI
TN 024 01 MBER 1 MCIPRI trough TN 025 23 MBER 46 MCIPRI
 
I suspect the new carrier is not set up as: IFC ESS5

[©] GHTROUT.com [⇔] Resources for Nortel Meridian/CS1000 System Administrators - You Can Hire Me Too
 
Have you tried using just the ACOD 7002?. Also check in LD 60 against the loop that all channels are IDLE or do e.g. a trace in LD 80 TRAC 0 7002 etc.




All the best

Firebird Scrambler
Meridian Programmer in the UK

If it's working, then leave it alone!.
 
I have with new carrier in LD 60 all channels are idle.

Using the access code 7002. I get dial tone, I dial a local number NPA/NXX xxxx I imediatly get a reorder tone.

LD 80 I use TRAC and the TNB of the set I'm calling from but I only see the set information the number dail and no Loop/Channel information.

I have not tried TRAC 0 7002.

Thanks for the prompt response!


 
Hi,
The problem may be the FRL mapping in the route data block. At the moment everything is mapped to 0. If NCOS 0 is set to internal only, or not setup, this may stop calls out.
You could try setting the FRL as 1 to 1 e.g 0 0, 1 1, 2 2 etc.
 
Thanks…. what puzzles me is that the current configuration is working with my current carrier,
The only variable here is the new carrier T1’s .
 
Try turning DCH messaging on. This will show you what is being sent to line and also maybe the carrier reject code.
 
We all go through this when we switch carriers it seems. Someone at the carrier says it's provisioned one way, yet they configure it another way.

Not FRL, since it worked on the other carrier.

However, you might have better luck going from DSEL VOD to 3VCE

[©] GHTROUT.com [⇔] Resources for Nortel Meridian/CS1000 System Administrators - You Can Hire Me Too
 
Thanks guys for the tips,

I have a scheduled cutover next Thursday, this will be my 3rd attempt.

I'll turn DCH messaging on and I'll give DSEL 3VCE a try.
 
Verify the signaling with the new Telco. I had the same issue and I had the D-channel set up differently than telco.
 
Thank you kat0118, I'll check with the carrier.
 
The existing configuration is ATT NI1 custom (ESS5)
I would guess the new PRI is NI2 standard.
Verify with your vendor what the correct D channel configuration should be.
If it is NI2 standard you will need to out the B channels,route and D channel and rebuild.
Most local service is set up in the switch as either CBCT ot 2 way DID not tie lines.
 
All,

I just found out that the current working spans are 4ess and not 5ess as my documentation indicated. I'll change the type and see if it makes a diference.
 
remember for the incoming DID calls:
the LDN (OVL 15)must be define as the same lenght as the DID in you case 4 digit
JF
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top