Opt 61 Call routing

[sljulian]

I currently have an Opt61 that you have to dial 9 for local calls and 8 for LD. When you dial 8 it goes out a separate T-1 than if you dial 9. If you dial 9-1 the call fails. I am having the local PRI picked for our LD carrier with forced account codes. My question is how do I change the routing so I can dial 9-1-XXX-XXX-XXXX and also put in the pick code for the LD carrier? I have been told to have my PRI picked for my LD carrier is going to take 7-10 business days and I want to start using the local PRI today or at least by Monday. I guess I need to say that I am very new to the Opt 61 for that matter any Nortel systems. I am an NEC and Mitel tech.
Thank you for your help.

 

[GHTROUT]

A BARS overview is in order - this is a start:

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

--
Nortel Resources at GHTROUT.com
--

 

[sljulian]

I have looked over the BARS 101 and think I have a fair idea. What I cant figure out is this.
Rout 1 is for local only and Rout 2 is LD. I want to send callers with a Class of service of 4 and an frl of 4 to call LD over rout 1 but add a pic code? I have created a DMI 12 that adds 1010XXX. but I cannot see when they dial 9-1-xxx-xxx-xxxx the rout 1 denies the call? If I dial 9-xxx-xxxx it goes out rout 1. Do I have to change LD 90 NET to have it look for something else? or because the way it is currently set up no LD calls are allow to use Rt 1 as LD is there somewhere else the call can be denied system wide?
I know this is hard to diagnose with out being onsite but I appreciate your help. If it would help to attach any printouts just ask and I will post. I am just not sure which ones would be most useful

 

[GHTROUT]

I think you need to get a picture of your BARS:

http://www.ghtrout.com/ghtrout/files/Print_Out_BARS.html

You want all callers dialing Long Distance to attempt the LD route. You just want to limit callers with a certain NCOS to be "allowed" to overflow to the local route as well as the LD route.

This sentence does not make sense:

"but I cannot see when they dial 9-1-xxx-xxx-xxxx the rout 1 denies the call?"

Please rephrase.






--
Nortel Resources at GHTROUT.com
--

 

[sljulian]

That is correct, it is only about 50 users that I specifically want to be able to dial 9-1-xxx-xxx-xxxx the rest will still dial 8-xxx-xxx-xxxx and will have to enter their auth code which is required by the carrier. This is so I can send the 50 users out the PRI and give out a caller ID that is for this department. Currently when you dial 8 the carrier provides the number. Dialing 8 accesses a T-1 and dialing 9 accesses a PRI. We get a better rate for dialing 8 but this project is only for a short time so changing the circuit to a PRI to allow the functionality will take too long.
The statement "but I cannot see when they dial 9-1-xxx-xxx-xxxx the rout 1 denies the call?" What I meant was that currently when you dial 9-1-N the call goes to an error tone? But in LD 90 9-1206 is allowed. So I cannot find out where that is being stopped. According to my program my phone is in COS 3 with an FRL 3 and the RLI has 1206 in there?
I will follow your direction and complete all of the print outs and look again.

 

[GHTROUT]

I see. This might steer you closer

1--Identify the matrix between that NCOS and the FRLs in LD87 NCTL. Confirm that NCOS0=FRL0 all the way to NCOS7=FRL7.
2--Look in LD90 at 1206, an NPA I assume. Identify the RLI
3--View or print the RLI out in LD86
4--The first ENTR should show ROUT 2 - What is the FRL?
5--Now Look at a phone's TN - check the NCOS.

Does the NCOS of the phone meet or exceed the FRL of the ENTR you spotted in step 4.

Does the NCOS of the phones you do not want to dial LD fall below the FRL you spotted in step 4.



--
Nortel Resources at GHTROUT.com
--

 

[sljulian]

I have been able to complete a LD call! Now I am trying to build LD 90 NET AC1 for 1 NXX XXX XXXX calling. Do I have to add all the area codes? I have been trying to incert wild cards but it will not take them? I basicly need to open this up to nation wide calling.

 

[GHTROUT]

If you do not have any BARS to speak of today, use my "abbreviated method" using all SPNs

http://www.ghtrout.com/ghtrout/files/MINI_BARS_-_Super_Small_BARS.html

--
Nortel Resources at GHTROUT.com
--

 

[nessman]

Check with your carrier to determine which area codes and exchanges (NPA's and NXX's) are local, intra-lata and long distance from your location. The downside is you'll always be playing "catch up" with the carriers as they add more area codes and exchanges. This gets especially dicey in areas where you are in an area code overlay, and adds to the frustration of the user who has to figure out what's long distance and what's not by dialing 8 or 9. It becomes and administrative nightmare.

On the other hand, just about everyone has a cell phone with free long distance - so toll fraud isn't what it used to be for businesses - and you can easily block international calling to most people using SPN, FRL and NCOS (see GHTROUT's excellent tutorial).

If you're paying more than 3-4 cents/minute for long distance, you will want to shop around for a better deal... or consider lower cost alternatives such as SIP trunking if have the $$$ for a switch upgrade, or VoIP carriers with unlimited local/long distance.

 

[sljulian]

Thanks to everyone for your help!
I have it worked out Kind of! My LD carrier for AC2 does not require a 1 so everybody is accustomed to dialing 8-XXX-XXX_XXXX and putting in their account code. I set up SPN for AC2 as 12 13 14 and so on to go out RT 1 and with the higher COS it works for my test calls.
Now for the new problem I have a specific number that needs to be displayed for these callers of an 800 number. I programmed it in a CLID table and it worked for LD and local calls. But now when I call 911 they no longer get my info because I am not sending the correct caller ID. Can you have a different caller ID for 911 than a regular call?