What is best way to throttle (choke) outbound calls to a specific Nbr?

[MitelInMyBlood]

CUCM 8.5

I have received an inquiry about the max number of call concurrency we can allow to a specific external number. I have 7 PRIs in a two-way configuration on our gateways, but these are used for normal business requirements and we're not heavily over provisioned on trunks. Without bringing the business needs to its knees we estimate we might be able to allow as many as 23 simultaneous calls (1 full PRI worth) with minimal impact on business.

So how do we do it?

Is there a recommended way of building what we legacy telecom guys would call a traffic choke? We tried it using a CTI RP and squeezing down the max calls allowed to 1 (just to try it) but it did not seem to restrict the call concurrency like we thought it would or should.

Thanks in advance

Original MUG/NAMU Charter Member

 

[whykap]

So it's an outbound call to a specific number you want to limit?

 

[trvlr1]

I have never tried this before, so squint as you are reading it .....
Could you build a partition that only includes one of your circuits, then build a route pattern that sends that number to only this new patition. That would limit the maximum outbound calls to that number, but would still be available for inbound if you needed it, so the practical amount of calls you could make out would depend on how many calls are coming in on that circuit.
Just "spitballing" here, so please join in and fill in the blanks .....

 

[MitelInMyBlood]

Right, it's an outbound call to a specific (known) number. A coworker suggested building a dial peer just for this one number then directing it to a specific RG with only a limited number of trunks in it, ie., say two or maybe 3 PRIs thus limiting concurrency to 46 or 69 trunks. The problem is these are 2-way trunks and we really have no way of preventing inbound traffic from hitting them. Even though they are at the bottom of the LEC's trunk group some will still get hit inbound during peak traffic hours.



Original MUG/NAMU Charter Member

 

[trvlr1]

They need to be answering the inbound then ... not making outbound!

 

[whykap]

just create a route group as you said with as many PRI's you want to support for incoming calls. Then add the route group to a new route list and create a route pattern with the outbound number in discussion. Point the route pattern to the new route list.
Obviously you can't prevent inbound calls to hit those PRI's so you'll either have to ask the provider to take them out of the hunt or during peak hours deal with less that desired outbound calls.

 

[MitelInMyBlood]

Thanks!!

Original MUG/NAMU Charter Member