So close I can taste it..... 4

[MagnaRGP]

Howdy all. Seems to be a lot of NARS questions floating around, and I am no exception. This is related to one of my previous threads which you all helped with, but I'm missing the final piece of the puzzle.

CS1kE 5.0 SA split between 2 NPAs (416 and 905). Some NXXs in 905 are local to 416, but not 905 (example 905-686-aaaa).

Users in 416 should be able to dial 9,905-686-aaaa and the call will pass, 905 users would get a telco intercept. So, I've managed to modify the RLI successfuly as follows:

RLI 9
ENTR 0
LTER NO
ROUT 9
TOD 0 ON 1 ON 2 ON 3 ON
4 ON 5 ON 6 ON 7 ON
CNV NO
EXP NO
FRL 1
DMI 0
FCI 1
FSNI 0
SBOC NRR
CBQ YES

ENTR 1
LTER NO
ROUT 10
TOD 0 ON 1 ON 2 ON 3 ON
4 ON 5 ON 6 ON 7 ON
CNV NO
EXP NO
FRL 1
DMI 0
FCI 2
FSNI 0
SBOC NRR
CBQ YES

ENTR 2
LTER NO
ROUT 9
TOD 0 ON 1 ON 2 ON 3 ON
4 ON 5 ON 6 ON 7 ON
CNV NO
EXP NO
FRL 1
DMI 0
FCI 0
FSNI 0
SBOC NRR
CBQ NO

ISET 3
NALT 5
MFRL 1
OVLL 0

Where rt 9 = 905 site PSTN and rt 10 = 416 site PSTN, FCAS 1 denys NXXs (including 686) and FCAS 2 allows those same NXXs. It works fine. BUT.....

I don't want the users in 905 to change their dial pattern, so I need to accommodate dialing for 9-1-905-686-aaaa such that it will recognize the NXX, deny the call on rt 9 (initially), strip the 1 (DMI 30 = del 1) attempt the call on rt 10 as above and if ATB, place the call on rt 9 giving authcode stutter tone (FRL 2 = stutter tone).

I've mucked about with it for a while now, and despite wearing a hard-hat (this is a construction site) I have a headache from beating my head on the wall.

Heeeeellllp. (please)

Thanks.

 

[johnpoole]

there's nothing wronge with your dial plan BUT why send anyone to telco intercept? that takes a trunk and waste users time, give them switch reorder, it's free...

as long as your ld 90 is built right the rlb's should work..

if i send all calls ac1+905 216 to rlb x, then enter 0 handles most of my calls, i give ncos 2 to users that are allowed that call set entry 0 frl 2.. i've got the allow side done AND anyone ncos 1 or 0 will get reorder.. i can add an entry but that is usually just for adding access to a trunk not blocking...

for me to use entry 1, if my senior staff needed special access, they would be ncos 5, my entry 1 would be set to frl 4 and they would have a second route, even if i had to dmi the call out ld...

the only other reason i would add a second entry is for a back up route.. here we have two providers for ld, if the 1st route is busy or down, it steps to the second route and blocks all users ncos 2 and below...

if we have a major problem, fire, weather etc.. er personal and it can still have two way service... the other 7000 people can wait for a ld trunk..

john poole
bellsouth business
columbia,sc

 

[MagnaRGP]

Agreed with most of what you say.

I kinda goofed with my explanation. Before I added the 416 site, NARS was basic. All calls went out rt 9. Anything without a 1 was allowed, and telco intercept told users that the call was LD. Kinda assuming that users know what is LD and what is not. The occasional telco intercept was fine due to relatively low call volumes. All calls of FRL 2 or higher receive stutter tone for switch authcodes and authcode NCOS dictates caller ability (LD versus international).

Now, with the addition of the 416 site, some previously LD calls can be local if facilities are available. I don't want to change the 905 user's dialing pattern because the next thing they will want is an up to date list of what is LD and what is not. If the site was just 416, it would be easy.

Anyhoo, there IS an inherent simplicity in what I'm attempting. If the trunks are available, you get the 1-905 call free, if not, you get stutter tone and you can decide if the call to your wife warrants the LD charge to your dept.

 

[MagnaRGP]

So I did some more testing.... dialing 9-1-905-686-aaaa

Here is the synopsis. MFRL 2 = stutter dialtone prompt for authcode. Set is ncos 1 and ncos 1 = frl 1.

So I tried the following on RLI 19.

MFRL 1

Entr 0 -- Rt 10 (PSTN local to 905 686), FRL 1, FCI 2 (allow 905 686) DMI 30 (del 1 ctyp nchg)
Entr 1 -- Rt 9 (PSTN LD to 905 686), FRL 2, FCI 0 DMI 0

If I do this, the call fails to process and returns fast busy. If I change the MFRL to 2, I get prompted for authcode.

I am now at a loss as to what the [expletive deleted] is going on.

Any thoughts?

 

[a12ozbottle]

Try changing the npa on your fcas to 1905 instead of 905.

 

[acewarlock]

You should use FCAS tables to ALOW local NXX's on ENTR 0 and non-local NXX's will be denied, then creat another FCAS table to ALOW the LD NXX's and it will deny all other's.


Go here for a traing cource, this may help you out.

http://www.ghtrout.com/bars/

This is a Signature and not part of the answer, it appears on every reply.

This is an Analogy so don't take it personally as some have.

Why change the engine if all you need is to change the spark plugs.

 

[MagnaRGP]

12oz...I didn't think of that. I'll give it a try.

ace -- I did create FCAS allow and deny (see original post), but under NPA 905 not 1905.

Did the NARS tutorial, but FCAS isn't covered to the level that I require.

I'll update post test.

 

[a12ozbottle]

Is route 10 a tie to another site if so you might have to reinsert the 9.

 

[MagnaRGP]

Just tried to create the FCAS for 1905, does not allow it. Only 3 digit NPA accepted.

Rt 10 is a PSTN that is local to 905-686. Rt 9 is PSTN LD to 905-686

Back to square 1....

 

[a12ozbottle]

If you have PRIs try turning dch messaging on for your locals then you should be able to see if your getting past the RLI.

 

[a12ozbottle]

I dont see anything else that would block you. Except maybe the ctyp on your dmi.

 

[acewarlock]

Did you creat the NPA 1905 first?

I program both 1NPA and just NPA in LD 90, so both ways the customer tries to dial will work. you need to creat CFAS and DMI tables so you can manipulate the numbers without the user having to hangup and redial the right way.




This is a Signature and not part of the answer, it appears on every reply.

This is an Analogy so don't take it personally as some have.

Why change the engine if all you need is to change the spark plugs.

 

[a12ozbottle]

He said he was getting stuttered dial tone when he changed the mfrl so it sounds like he has 1905 in ld 90.

 

[acewarlock]

This is the reason I asked.

Quote:
"Just tried to create the FCAS for 1905, does not allow it. Only 3 digit NPA accepted."

You can't creat an FCAS for an NPA unless you created it first.




This is a Signature and not part of the answer, it appears on every reply.

This is an Analogy so don't take it personally as some have.

Why change the engine if all you need is to change the spark plugs.

 

[MagnaRGP]

correct. all of my NPAs are 1NPA except for 416, 647, 905 and 289 which are built both with and without the 1. Everything that is local to 905-624 (my customer's head office location) is local to the 416 and 647 NPAs (overlaid . However there are 905 NXXs (686 is but an example) that are local to 416/647 that are LD to 905-624.

The bizarre thing is that when I change my RLI back to 1, I get stuttered dt properly. I've done a stare-and compare and had another pair of eyeballs look at RLI 1 and 19 and he can't see anything wrong.

I'll try to get the ESN info and post it. Maybe someone can spot something that I haven't.

 

[a12ozbottle]

Try to temp remove the fcas table on the rli and dial then you can rule out fcas.

 

[a12ozbottle]

have you check dch messages?

 

[a12ozbottle]

Looking at your first post on rli 9 you have an entry 2 that doesnt restrict anything are you sure those calls are going out your local trunks. You might want to trace to verify that.

 

[acewarlock]

I have to agree with a12ozbottle that ENTR 2 will alow any thing that ENTR 0 and 1 Block, which defeats the purpose of having ENTR 0 and 1.




This is a Signature and not part of the answer, it appears on every reply.

This is an Analogy so don't take it personally as some have.

Why change the engine if all you need is to change the spark plugs.

 

[MagnaRGP]

Explaining the post:

Entry 0 FCI 1 denies 9,905-686 on rt 9. This results in a telco intercept about the call requiring a 1.

Entry 1 FCI 2 allows 9,905-686 on rt 10. This is a local call to the site where rt 10 PSTNs are.

Entry 2 was put in by a colleague for reasons unknown to me, but is irrelevant as the call goes out rt 10 as expected. This was tested and confirmed by trac 0 DN dev.

This is all and good. The plan is to intercept 9,1-905-686 calls that would normally route out rt 9 (correctly, as the first choice for 1905 calls is rt 9), strip the 1 (by use of DMI 30) and send the call out rt 10 as 9,905-686. If those trunks are busy, then the call should process as dialed out rt 9.

I'll post the RLI for 1905.