I am trying to set up a way to in limit incoming calls coming to certain extensions so that trunk lines are always available for more important extensions. I have CM 2.1 and Tenant Partioning available to make it happen. My Avaya people said I needed Tenant Partioning to do this.
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 TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Block Calls
- Thread starter cmeyer
- Start date
U can limit all calls to a certain extension through the COR.
Da-vi'do
P.S. For the best response to a question, please read FAQ222-2244. Also give the type & version of your voice mail & pbx system & preview your post to make sure it is complete & understandable. Be aware that if u don't answer a question, I usually will not continue to help u. Please leave a post on how u fixed the problem too.
Da-vi'do
P.S. For the best response to a question, please read FAQ222-2244. Also give the type & version of your voice mail & pbx system & preview your post to make sure it is complete & understandable. Be aware that if u don't answer a question, I usually will not continue to help u. Please leave a post on how u fixed the problem too.
- Thread starter
- #3
JEzz, I don't know how u would be able to do that even with tenant partioning. But that doesn't mean u can't.
But U could take away the low priority extensions DID extensions and make callers to those extension go through a autoattdt or vector to get to them. These extensions would have their own small trunk group.
Then the higher priority extensions would get their own DID trunk group with a lot more members.
OR , u could have the lower priority extensions have their own DID trunk group with few members.
But U could take away the low priority extensions DID extensions and make callers to those extension go through a autoattdt or vector to get to them. These extensions would have their own small trunk group.
Then the higher priority extensions would get their own DID trunk group with a lot more members.
OR , u could have the lower priority extensions have their own DID trunk group with few members.
Try breaking up the trunk group into two separate groups. Give one trunk group a COR that everyone can use, and leave the other for the important extensions.
It'll be easiest if your provider setup the trunk group with a linear hunt. The first trunks that calls would hit would be for everybody, and the last trunks that calls would hit would be for the important extensions.
In your route patterns, you would make the 'important extension' trunk group your second choice.
With a properly configured COR, calls that arrive or try to leave over the 'important extension' trunk group will not be completed for the stations that you have designated 'less important', but they would have access to some trunks anyway.
This may have the effect of increasing the complaints about trunk availability, but it will make sure there are some trunks generally available for the important customers.
Carpe dialem! (Seize the line!)
It'll be easiest if your provider setup the trunk group with a linear hunt. The first trunks that calls would hit would be for everybody, and the last trunks that calls would hit would be for the important extensions.
In your route patterns, you would make the 'important extension' trunk group your second choice.
With a properly configured COR, calls that arrive or try to leave over the 'important extension' trunk group will not be completed for the stations that you have designated 'less important', but they would have access to some trunks anyway.
This may have the effect of increasing the complaints about trunk availability, but it will make sure there are some trunks generally available for the important customers.
Carpe dialem! (Seize the line!)
- Status
Similar threads
