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 bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Blocked Calls 1

Status
Not open for further replies.

Bunkerman

Technical User
Feb 21, 2008
15
US
I have a Meridian-1, Opt 81C, Release 25.47. Installed Two T1’s (regular DTI’s not PRI’s) to feed a Norstar system in another Building. I set up a DSC 9624430 to route calls to the T1’s. All outgoing and most incoming calls work fine. Some calls coming from outside the Meridian-1 Switch to 9624430 get blocked. They get my RAN “You dialed an invalid or unauthorized number”.
Most calls from NXX-836 are blocked, some are not.
443-9394gets blocked, but 443-9082 does not.
445-4098 gets blocked, but 445-4082 does not.
963-1000 gets blocked.
I spoke with the Switch Tech at the 443 Exchange who said that the COS on both phone numbers were the same and they both go out the same
Route. Can’t understand why one would be blocked and not the other.
Anyone have any insight into this strange dilemma?
 
Identifying all the ways the blocking is happening is going to be valuable. You could look at the LD21 REQ prt TYPE int
to see all the places you have that RAN assigned. It might prove that it is or isn't a certain call type.

The fact that it is sporadic is odd - to the point that it sounds like more is happening than meets the eye.

I'd be verifying that, for example "443-9394 is ALWAYS blocked, and 443-9082 is ALWAYS allowed".

If the "always" statement cannot be proven, then I'd be inclined to stat the DTI loops to see if they are going busy on you.




~~~
GHTROUT.com | Get the Input/Output Manuals | Tek-Tips FAQs | Recent Replies
 
post one route,

john poole
bellsouth business
columbia,sc
 
Not really sure what was going on. Odd that two phone numbers coming from the same place were treated differently. I changed the DSEL to VOD which corrected the incoming call problem from those particular numbers but it caused a problem on the outgoing calls. I guess putting in an extra digit. So I changed DSEL to 3VCE which fixed the Outgoing & Incoming calls. So far no problems. Oh yah, my Intercept went to RAN Rout 22 which was ACCD & NBLK. The only thing I could figure from this was the Incoming digits were messed with causing the Invalid number recording. Thanks for the clues, very helpful.
Here is the RDB.

REQ: PRT
TYPE: RDB
CUST 0
ROUT 34

TYPE RDB
CUST 00
ROUT 34
DES BLDG 937
TKTP TIE
NPID_TBL_NUM 0
ESN NO
CNVT NO
SAT NO
IDEF NET
RCLS EXT
DTRK YES
DGTP DTI
ISDN NO
DSEL 3VCE
PTYP DTT
AUTO NO
DNIS NO
ICOG IAO
PREM NO
SRCH RRB
TRMB YES
STEP
ACOD 3934
TARG 01
CLEN 1
BILN NO
OABS
INST
IDC NO
DCNO 0 *
NDNO 0
DEXT NO
ANTK
SIGO STD
STYP STDN
TIMR ICF 512
OGF 512
EOD 13952
DSI 34944
NRD 10112
DDL 70
ODT 4096
RGV 640
GRD 896
SFB 25
TFD 0
SST 5 0
NEDC ETH
FEDC ETH
CPDC NO
DLTN YES
HOLD 02 02 40
SEIZ 02 02
SVFL 02 02
DRNG NO
CDR NO
MUS NO
MANO NO
FRL 0 0
FRL 1 0
FRL 2 0
FRL 3 0


PAGE 002

FRL 4 0
FRL 5 0
FRL 6 0
FRL 7 0
OHQ NO
OHQT 00
CBQ NO
AUTH YES
TTBL 0
ATAN NO
OHTD NO
PLEV 2
ALRM NO
ART 0
SGRP 0
AACR NO

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top