rls 16 may not accept nxx x0x or x1x, due to nanp being out on the nest rls.. they did write a patch that allowed the new npa's/nxx's to work but finding that is next to impossible. i did a rls 14 a few years back and used nfrl instead of bars.. the old way was to make local acod 9 and ld 8 the use 49 to allow or deny 1st digits... not a lot of control, but that with tgar/targs worked before bars came out
I want to use BARS/NARS because I installed a new DTI2 with a Carrier but the carrier doesn´t give me dial tone when I take tha Rout, Is there a way to make the Meridian generate a dial tone?
If you are using BARS, you would not ever hear the dial tone "from the carrier trunk route"...the dial tone users hears on BARS is unrelated to the route.
If you mean you do not hear dial tone after dialing 9, that is activated in LD86, the "ESN" data block, at the DLTN prompt
Johnpoole, But in this old software Is It possible to route calls depending on the digits dialed (select different routs) If It´s so, could please tell me the LD´s and prompts That I need
that is a default table, all frl's are pointed to table 0, if i point frl 3 to table 3 then give a user ncos 3, and init crno 3 to allow all, (1st digits only) that gives ncos 3 a value after the acod... if that is a ld/loc outbound route, the acod is 9, my ncos 1, frl 1 points to crno 1, one is and allow table with deny equal to 1, then i can dial 9 plus any number except first digit 1... ie no ld... if my ncos is 3 i dial 9, because frl 3 (on that route) is an allow table with all 1st digits allowed, i can dial any number after the 9....
very basic pre bars, but i don't have a switch with that setup in it now..
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.