|
Joined: Aug 2005
Posts: 908
Member
|
Member
Joined: Aug 2005
Posts: 908 |
We have an Axxess in our main building and a 5000 in an adjacent building. The 5000 routes all local and toll free calls through the Axxess. Toll Free calls are being refused by the Telco. We receive a message "Your call did not go through....". I can complete the call from the Axxess. Local calls work fine. Any ideas?
|
|
|
Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.
|
|
|
Joined: May 2005
Posts: 526
Member
|
Member
Joined: May 2005
Posts: 526 |
I had a similar issue with project codes not being seen. I played with DTMF Digit Duration on the 5200 side and got it to see the tones. I set it from 60 to 130, Inter-Tel said to go to 70 then 80 then 90 and shouldn't pass 120 I had to go to 130 to get every call to work was at about 80% success with the default and got better as I went up Not sure if this will help but might be a good start Randy
|
|
|
|
Joined: Aug 2005
Posts: 908
Member
|
Member
Joined: Aug 2005
Posts: 908 |
I tried 100 and 130. No change.
I may have another clue. Our provider does not require a 1 for toll access. Inter-Tel needs the 1 for routing purposes. So we have to strip the 1 before it reaches the trunks. The 5000 has a long distance T1. So LD calls are routed to it. Local calls go through the Axxess. There is no way to route to specific trunks on another node. Calls are sent to the remote node and it determines how to route them. So, I created a new route group for toll free numbers without the 1. No good. I get the same result. But do you think I'm getting closer?
|
|
|
|
Joined: May 2009
Posts: 1,198
Member
|
Member
Joined: May 2009
Posts: 1,198 |
The toll-free calls need to be routed over the local lines instead of the long distance T1.
Build a route group for toll-free patterns (1800+, 1888+, etc.)and make sure it's listed prior to your toll route group.
Point the toll-free route group to a facility group with the proper dial rules and trunk group/node.
|
|
|
|
Joined: Aug 2005
Posts: 908
Member
|
Member
Joined: Aug 2005
Posts: 908 |
The system was already set up that way. Here are some more clues. A toll free call (888 & 800)to a local area business works fine. Such as our own number and that of a local vendor. I ran a call report on the extension being used. The last four digits are being truncated on the report. However, the phone displays the full number, and the local toll free numbers go through, even though the report shows the last four digits truncated on them as well.
|
|
|
|
Joined: May 2009
Posts: 1,198
Member
|
Member
Joined: May 2009
Posts: 1,198 |
Let me see if I have this right...
Node 1 is the Axxess. Node 2 is the 5000 with the toll T1.
Node 2 local calls route via Node 1. Node 2 toll calls route via Node 2.
You have a Node 2 route group that sends toll-free calls (1800+, etc.) to Node 1. The facility group echos the entire 11-digit number dialed (dial rules 2,3,4). Node 1 has a matching route group that sends toll-free calls (1800+, etc.) to a facility group that echos the entire 11-digit number dialed (dial rules 2,3,4) to the local trunk group.
How about using SMDR monitor at Node 1 to watch the digits on the local trunks? At least you'll be able to see exactly what digits are being sent over which trunks.
|
|
|
|
Joined: Aug 2005
Posts: 908
Member
|
Member
Joined: Aug 2005
Posts: 908 |
You are correct.
Here is an example of SMDR Monitor on Node 2. This call is to a Toll Free number in our local area. Even though the last four digits don't show, the call was still completed. If I call a toll free number in what would be a long distance area, the call does not complete.
TLC 1262 94144 888-7457 11:04 00:00:03 $00.00
The SMDR monitor won't open for the Axxess.
|
|
|
|
Joined: May 2009
Posts: 1,198
Member
|
Member
Joined: May 2009
Posts: 1,198 |
Is trunk 94144 on Node 2? If so, the call is not being routed to Node 1.
Double check the Node 2 route groups, to make sure there are no patterns that match the toll-free patterns, and send these calls to the toll T1.
Isn't ARS fun?
|
|
|
|
Joined: Aug 2005
Posts: 908
Member
|
Member
Joined: Aug 2005
Posts: 908 |
The toll free route group was last on the list. It has been moved to the second line and is now working. Live and learn.
Thanks for the help.
|
|
|
|
Joined: May 2009
Posts: 1,198
Member
|
Member
Joined: May 2009
Posts: 1,198 |
It’s important to remember that Route Groups, like Call Routing Tables, are classified as “ordered lists†and will route calls as soon as a match is found - even if it’s not the route that you want.
In this case, [Q]TNXXXXXXX+ (the default dial pattern for toll long distance), is also a match for toll-free calls. If toll long distance is listed higher than toll-free, the call will get routed before it hits the toll-free dial patterns.
|
|
|
Forums84
Topics94,552
Posts640,111
Members49,861
|
Most Online5,661 May 23rd, 2018
|
|
1 members (Toner),
39
guests, and
85
robots. |
Key:
Admin,
Global Mod,
Mod
|
|
|
|