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 MikeeOK on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Route limit 999, is it a license issue or system max?
- Thread starter 9mmgeek
- Start date
What kind of configuration are you running that you need over 1000 route patterns? Even if you had remote gateways each with their own local trunking with maybe 5 routes each, that would still be 200 gateways before hitting 1000 routes.
-CL
-CL
- Thread starter
- #4
- Thread starter
- #5
Lopes,
It is an IP Connect system with 25 locations, each with a PRI. In order to fully mesh the sites for least cost routing, AND give each site the alternative to use its local PRI if they are in LSP mode, each site needs its standard 6 routes for 911,800, local, LD, intnl, and bad number, plus 24 routes to reach the local calling domain at each other office. That is 750 routes now not counting MM, Rightfax and some other misc stuff. As the number of sites grows it compounds to 26 sites x 31 routes. I ran into the problem now because the numbering that I am using was/is leaving room for growth between the routes for each site. I have 250 more but I expect those to be gone by the middle of next year.
The only solution I can see is if there is a code for the route pattern that says use the trunk at this location. Then I wouldnt need to keep duplicating all the ARS routes for each site.
It is an IP Connect system with 25 locations, each with a PRI. In order to fully mesh the sites for least cost routing, AND give each site the alternative to use its local PRI if they are in LSP mode, each site needs its standard 6 routes for 911,800, local, LD, intnl, and bad number, plus 24 routes to reach the local calling domain at each other office. That is 750 routes now not counting MM, Rightfax and some other misc stuff. As the number of sites grows it compounds to 26 sites x 31 routes. I ran into the problem now because the numbering that I am using was/is leaving room for growth between the routes for each site. I have 250 more but I expect those to be gone by the middle of next year.
The only solution I can see is if there is a code for the route pattern that says use the trunk at this location. Then I wouldnt need to keep duplicating all the ARS routes for each site.
This is why I asked. 2 issues.
1. Your last sentance about "use the trunk at this location". The system actually does this by default. If you had 10 PRI's, each in a different gateway, all in 1 trunk group and 1 route pattern. When a call is then placed from a station at a gateway, it will always choose it's local reasource 1st (it's local tone, medpro, and in this case the local PRI). You may in fact be unecessarily duplicating your work.
2. Least cost routing as you have decribed hasn't really existed in many years due to current LD rates. Of course there are exceptions to every rule like an "all you can eat" local pri usage packages but you may want to do an analysis of what you pay for a 3 minute LD call vs what you pay for a 3 minute local call which was also sent over WAN BW plus the admin/upkeep time of manipulating ARS this way. We used to do this all of the time 10-15 years ago when we paid 8 cents for a local call any duration and 8 cents per minute LD. Now with the 1~2 cent LD rates and all inclusive packages available these days, you may actually be spending more money by using the WAN in the manner.
-CL
1. Your last sentance about "use the trunk at this location". The system actually does this by default. If you had 10 PRI's, each in a different gateway, all in 1 trunk group and 1 route pattern. When a call is then placed from a station at a gateway, it will always choose it's local reasource 1st (it's local tone, medpro, and in this case the local PRI). You may in fact be unecessarily duplicating your work.
2. Least cost routing as you have decribed hasn't really existed in many years due to current LD rates. Of course there are exceptions to every rule like an "all you can eat" local pri usage packages but you may want to do an analysis of what you pay for a 3 minute LD call vs what you pay for a 3 minute local call which was also sent over WAN BW plus the admin/upkeep time of manipulating ARS this way. We used to do this all of the time 10-15 years ago when we paid 8 cents for a local call any duration and 8 cents per minute LD. Now with the 1~2 cent LD rates and all inclusive packages available these days, you may actually be spending more money by using the WAN in the manner.
-CL
- Thread starter
- #7
In my experience 1-2 cents rates are not a reality except in the mouths of salesmen and maybe best case scenarios. Our investigations show Intra state and switched access in the 4-5 cent range. Only Interstate and dedicated with a high volume commmitment gets that low and it would take a lot of analysis to show what it would get us.
I don't think I can merge all of my disparate trunks into one group because they are in diffent tenants. But the concept is interesting. The BP set up each office as a tenant and I think it was done because management wanted each site to operate independantly with their own attendant. They got over that and now we have several attendant sites serving groups of unattended sites. Maybe I should study if there is a reason to keep so many tenants. It might simplify things.
I don't think I can merge all of my disparate trunks into one group because they are in diffent tenants. But the concept is interesting. The BP set up each office as a tenant and I think it was done because management wanted each site to operate independantly with their own attendant. They got over that and now we have several attendant sites serving groups of unattended sites. Maybe I should study if there is a reason to keep so many tenants. It might simplify things.
I'm right there with you on the fact that tags, taxes, out the door pricing is more than a contracted rate of say 1 cent per minute but the same games should more or less apply to your local rate as well.
Our per minute blended LD rate with fees comes out to about 1/3 of the cost of our rate for a flat per call local charge. Basically, that means our LD is actually cheaper than our local rates on calls less than 3 minutes but more expensive on calls greater than 3 minutes. Your CDR should be able to let you take a swag out where you are at. We just haven't seen any necessity for that type of ARS in a while. We do however have a few "frequenty called and long duration" numbers that pop up on our call accounting which we will create specific routes over the WAN for.
-CL
Our per minute blended LD rate with fees comes out to about 1/3 of the cost of our rate for a flat per call local charge. Basically, that means our LD is actually cheaper than our local rates on calls less than 3 minutes but more expensive on calls greater than 3 minutes. Your CDR should be able to let you take a swag out where you are at. We just haven't seen any necessity for that type of ARS in a while. We do however have a few "frequenty called and long duration" numbers that pop up on our call accounting which we will create specific routes over the WAN for.
-CL
- Thread starter
- #9
- Status
Similar threads
- Locked
- Question