T1, Toll Free, and ARS

[mcphelps]

Merlin Legend r7
T1= DNIS configured as Tie
Long Distance carrier = AT&T

Is it possible to place outbound toll free calls on a T1 line? I have all calls, local and LD, except the special numbers going out on the T1 (pool 890) using the ARS , but toll free numbers "can not be completed as dialed". I have currently created an ARS table to send toll free numbers out on the analog lines (pool 70), but I will soon be down to having just a single analog line for the special numbers, and have a large need for toll free access. Do I just have to drop or add digits, as I have had to do with the other type of calls?

Thanks!

 

[mrpeabody]

Sounds like a provider issue. I've never seen a case where there was a supertrunk that accepted Local calls but not Toll Free calls, although I can see theoretically how it is possible. It almost sounds like the local carrier is sending the Toll-Free calls to the LD company, and the LD company is not accepting it. It's hard to say which one has the problem (Local or LD provider), and I bet you they will be apt to point the finger to the other.

 

[franke]

Try inserting a "1" in your new table; normally AT&T did not require a "1" for toll calls, however they are switching over to DMS switches and now they are all discombobulated. Sometimes they want a "1" sometimes they don't. If that does not resolve the problem then I would verify with AT&T that they are pic'd for 800, 888, 877 etc. numbers

franke

 

[jgideon]

If the T1 is a Long Distane T1, they will probably not process calls to toll-free numbers. (They'll accept and bill for any 'normal' number, local included, but LD carriers do not ORIGINATE calls to a toll-free number.). However, if you send 'local' calls out your 'long distance' T1, you will usually be charged at your 'in state long distance' rate.

 

[fonetek]

FRANKE IS CORRECT
YOU HAVE TO PLAY A LITTLE WITH YOUR PATTERNS
TRY GIVING AN EXT A DIAL OUT CODE FOR THE POOL YOUR USING
JUST TO GO AROUND ARS. THEN TRY THE NUMBER WITH 2 1'S
OR NO 1'S THIS WILL TELL WHAT YOU NEED TO DO

FRANK C
CONSOLIDATED TECHNOLOGIES
AVAYA GOLD BUSINESS PARTNER

 

[Boomhauer]

Yes, it does seem the network is not getting the digits it wants to route the call properly. Who is the provider? Open a ticket and have them put up a "trap". They can tell you exactly what digits you're sending them and advise accordingly. It doesn't seem likely that the T-1 is restricted against toll-free numbers, lots of small businesses have 1 T-1 or PRI and rely on it for all their calls. The carrier is handing the call off (local/LD/toll/toll-free) to the appropriate LEC/LXC and there it goes.

Another scenario, your provider is translating the digits incorrectly. The recording may be coming from the company its being routed to, that means the two carriers must work in tandem to resolve a translations issue. I could go on but I'll spare you. Hopefully its not this complicated.

Good luck,
Eric (Ex-Verizon Switch Tech)

 

[GoKings]

Sounds like you have an LD T1. You CANNOT route toll free numbers out on an LD T1. The way that I can recognize the fact that you have an LD T1 is the fact that you said you are receiving DNIS digits. Local supertrunks will not route DNIS. If you are routing local calls across the T1, you are likely inserting your local area code. Additionally, you are likely paying intrastate LD charges for all local calls, when some of those calls would be zone 1 local calls, costing you much more to route over the LD T1. You should check your services carefully and make the necessary adjustments to your ARS.

 

[mcphelps]

Thanks for the replies. It appears that AT&T doe not offer outbound toll free to anything other than AT&T toll free numbers for this area. This is a feature that gets added to the area as customers request it, and evidently, I am the first customer who has requested it. I should have this capability in a 100 days...