I want to allow for 0+ dialing for collect calls.my lec says its my equipment restricting that from happening.if i dial my acod to directly access the trunk , o gives a fast busy.how can i see how 0 calls are routed?
nothing on the user side has changed, we lost the 0+ ability after moving to PRI trks. maybe routing for 0+ is still pointed to copper routes.I need to know how to print out how the switch handles 90 calls.
When you dial the access code, I assume you are dialing it for the PRI trunks? If so, are you sure the switch is providing the reorder tone and not the carrier?
You can check LD 19 (Code Restriction) but I am not 100% sure that will provide the info you are looking for. That would just be for direct trunk access.
For BARS/NARS calls (90) look in LD 90 and print your SPN. It will be defined there. You would look for 0 or 011 (for international).
LD 90
REQ prt
CUST 0
FEAT net
TRAN ac1
TYPE spn
SPN Hit enter.
It will print all of your SPN definitions. "0" will likely be the first one. It will provide you the RLI and any deny codes. Then go to LD 86 and print that RLI to find out what routes are being chosen.
the acod plus 0 may be blocked in nfrl, ld 49, i can look up the prompts tomorrow if you need. arch gave you the code for finding 0 in your spn table, the rlb.rli needs to point to your new route with a frl lower or equal to the ncos of the stations that need 9+0 access. if you changed carriers, not all carriers provide operator service
Johnpoole was correct on LD 49 for your direct access treatment as I am getting old (bad excuse for mistake) and memory is fading.
That being said....
With the information you posted, RLI 9 indicates it is using Trunk Route 6, which I assume is your old trunk route. If it is your new trunk route, then your new provider may not provide operator service and your reorder tone may be coming from them and not the switch....or....if it is your new route, I see there is a Digit Manipulation table being applied to any call using this RLB and there could be a conflict.
Do you know if route 6 is your new or old trunk route?
TYPE RDB
CUST 00
ROUT 6
DES SBC_DID
TKTP DID
NPID_TBL_NUM 0
SAT NO
RCLS EXT
VTRK NO
DTRK YES
BRIP NO
DGTP PRI
ISDN YES
MODE PRA
IFC NI2
CBCR NO
NCOS 0
SBN NO
PNI 00000
NCNA YES
NCRD YES
CHTY BCH
CPFXS YES
CPUB OFF
DAPC NO
BCOT 0
INTC NO
DSEL 3VCE
PTYP PRI
AUTO NO
DNIS NO
DCDR NO
ICOG IAO
RANX NO
SRCH LIN
TRMB YES
STEP
ACOD XXXX
TCPP NO
PII NO
TARG
CLEN 1
BILN NO
OABS
INST
ICIS YES
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
DRNG NO
CDR YES
INC YES
LAST YES
QREC YES
PAGE 002
OAL YES
AIA YES
OAN YES
OPD YES
CDRX NO
NATL YES
MUS YES
MRT 20
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
TDET NO
TTBL 0
ATAN NO
PLEV 2
MCTS NO
ALRM NO
ART 0
SGRP 0
AACR NO
I would like to believe the problem lies with the carrier, but the say the problem is my switch. Same old song and dance. Supposed to set up a meet with both vendors and Im sure that will please $$ administration.From what Ive posted does it seem the problem is carrier?
nope, you print a dgt, then it ask for the dmi number, just reread the post, in your rli, change dgt to 0, that removes it, don't know why someone is making that an npa call, either that or a safre bet is to build a new rlb x, point it to the same route frl 0, return all other prompts.. then i will agree with you
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.