Require to configure CUCM and Gateway router PRI for 200 users

Question

Hi all,
My current scenario is like this:
We have two CUCM servers(7.1) in reduandancy. One is publisher and other is subscriber. We have a gateway router 2921 with a single PRI card. We have 200 IP Phone users. Currently the problem is we have only 30 telephone lines. So with the help of DID configuration. We assign thirty ports to thirty users. Now these thirty users are able to to make an outbound call and recieve an Inbound call. Now I also want to create a pattern in which we dedicate 10 channaels for other 120 users to make an outbound call. And restrict 50 users to not make an outbound call. So we require such a scenario.
Total 200 Users:
1. First 30 users. Able to make an outbound call and also able to recieve an inbound call.
2.  Next 120 Users. Able to make an outbound call. But not able to recieve an inbound call because of PRI restriction. Because we only have a thirty numbers. Dedicate 10 channels for them.
3. Last 50 users. Not able to make an outbound call. And also not able to recieve an Inbound call.
So I need a configurations of Gateway router and PRI. And also of CUCM in which we could define such a pattern.
Regards,
Ali Raza

Answer 1

Ali,
The outbound call restrictions can be implemented using the CUCM Calling Search Space configurations.  A basic example to illustrate:
Partition 1:  internal_pt   (only internal patterns)
Partition 2: phones_pt (ip phones on your network)
Partition 3: pstn_pt (off net patterns/external)
CSS1: Offnet_css
internal_pt
phones_pt
pstn_pt
CSS2: Onnet_css
internal_pt
phones_pt
You place all patterns that can reach off net in "pstn_pt". Phones that are using CSS2 cannot reach off net.  The above example is leveraging the device CSS for all call routing decisions.Using this approach, you would assign "onnet_css" to phones that can only dial internally. NOTE: I am just using a basic example here and not suggesting you use this PT/CSS config "as is".
There is another approach where you "allow" all patterns on a device and "restrict" on the line. For example:
Partition 1:  internal_pt   (only internal patterns)
Partition 2: phones_pt (ip phones on your network)
Partition 3: pstn_pt (off net patterns/external)
Partition 4: block-pstn_pt (blocking patterns for pstn)
CSS1: AllPhones_css
internal_pt
phones_pt
pstn_pt
CSS2: restrict-pstn_css
block-pstn_pt
Again, pstn_pt contains all pstn patterns.  The block-pstn_pt would also contain off net patterns. The difference is that in the block-pstn_pt all patterns would have the "Block this pattern" flag enabled. All phones would have a Device Level CSS of AllPhones_css.  Phone lines where you wanted to restrict off net dialing would have a Line Level CSS of restrict-pstn_css.
Just a quick refresher, when a phone LINE goes off hook to dial the CUCM is using the "Line Level CSS" + "Device Level CSS" to make the routing decision.  So, assume Line 1 on Phone A has restrict-pstn_css and the phone Device Level CSS is AllPhones_CSS. The Effective Search Space is:
1. block-pstn_pt
2. internal_pt
3. phones_pt
4. pstn_pt
So, if we assume that block-pstn_pt contains patterns that override patterns in pstn_pt then you can effectively block off net access to Phone A, Line 1.
Why would this be a good approach?  Well, what if you had a need to restrict Line 1 on Phone A but allow Line 2 on Phone A.  Using line level restrictions is much more flexible. Especially if you have more than 2 options you need to consider.
As far as inbound restrictions. If a phone line doesn't have a DID then you have achieved your objective.
The part I can't answer is reserving 10 specific channels for one group of users. I do not believe this is possible.
HTH.
Regards,
Bill