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

Force an outbound route

Status
Not open for further replies.

OpethBWP

MIS
Jan 20, 2006
160
US
I have a situation where I need to force specific area codes dialed to go out over my LD route.

So for example area code 123 currently goes out over route 5 (local dialing), anytime anyone dials 123 going forward I need to force it out over route 6 (LD).

What is the correct way to accomplish this?
 
Please use the real NPA and post what it shows in LD 90.




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.


 
Change ENTR 0 to show Route 6 in LD 86. In LD 90, you can print the current NPA, go to LD 86 to change your current RLI
 
In fact post all NPA from LD 90

REQ PRT)
CUST 0
FEAT NET
TRAN AC1 or AC2 depending on which your using.
TYPE NPA
NPA ALL or Enter, I don't remember which one it is.


And POST here




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.


 
I don't like making assumptions, sometimes the questions don't match what is already programmed.




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.


 
then change the npa 123 to the same route as a working ld npa..

if the user is dialing an nxx(7 digit), and you want to send it out over a ld route.. build a new dgt that deletes 0 and inserts 1123 then point that to the route.. that turns the local 7 digit to a ld 10 digit... assuming your carrier wants the 1... i do that here in reverse.. people dial orangeburg as an ld, i delete 4 (1803) then drop it on the locals.. in the same manner, if you dial an ld in the 803 as a local i insert the 1803 and send it ld..

we have a very deverse customer here, users try dialing the same dial pattern as there home phone, so i adjusted the database to compensate... we have extended area dialing for around 100 nxx's so they are ld from a local number but local from my switch..

john poole
bellsouth business
columbia,sc
 
there is not a dialing pattern that you can not handle in bars

john poole
bellsouth business
columbia,sc
 
So based off what was said here I compared the NPA for a LD call and changed the RLI to match.

LD 90
NPA for 1716
NPA 1716

NPA 1716
RLI 2
DENY 976

SDRR DENY CODES = 1
ITEI NONE

Compared this to another LD NPA and switched RLI. Now the calls goes out over the LD circuit.

The add on question for me becomes this..now the site has an Toll free number that they need to force out the same way. I have the whole TFN and need to force that over the same LD circuit..any suggestions on that one?




 
Thanks for the help everyone!

Checked my SPNs and I see the entry for 1800 with the local RLI. No problem I can change that to LD and that will force any TFN dialed out over the LD route .

lets say though I wanted to specifiy a number. I tried to add a new entry for that specific number 1800 227 4000(was happy I remember spacing in there!) obviously that is not going to work because their is already an SPN for 1800 ..

What is the correct way for me to specify a TFN while leaving the general SPN for 1800?
 
Because there is already a SPN starting with 1800 and you can't have 2 seprate SPN's starting with the Digits, but you can have Alow and Deny in a SPN.

OpethBWP: if your already allowing 1800, why do you want to make a 1800 227 4000?




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.


 
The primary reason was I wanted to just force this speicifc Toll free number to go over LD circuits.

Call volume is low enough on site though that I am just going to enforce it for all TFNs
 
Why do you want Free 800 calls to go out on LD trunks?




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.


 
The main reason for this was because our local circuits are passing outbound CLID info as per FCC regualtions. A specific client has a requirement with no outbound info.

Easiest way I could think of to do it was just route this over the LD circuit.

 
The place I worked last if we sent a 800 call over the LD trunks, we had to pay $.02 per min just like any other LD call.




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.


 
Agreed ACE..its not the most cost effective approach but it is what they are requiring for compliance.

So where I currently am...Changed the SPN for 1800 to the RLI for LD, user tries to dial a TFN now and gets a wave off.

So I start looking at the route, FRL on the route is 5 and the user has an NCOS of 6..Unless I am way off, higher should allow the call to get through?
 
That's a good question. If I have a user dial the ACOD1800... that would be the quickest way to test without bringing in my billing team right?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top