My solution to your problem involves Gatekeeper CAC instead of Locations. This is because you only want to limit external calls not internal calls between sites.
The Gatekeeper has 5 zones for your IP phones. This is because Group 3 actually gets split into 3 zones since you want 2 phones to have dedicated bandwidth not available to others.
The Gatekeeper also has a Gateway zone. You will instruct your H323 Gateway to register into this zone with a 9# tech-prefix. The existing dial-peers on the gateway need to be adjusted to remove 9# tech-prefix also.
Instead of 1 H323 Trunk in CCM you now have 5. Group 1's phone CSS's for external calls point to Trunk1. Trunk1 registers into GK with tech-prefix 1#. This continues up to Trunk5, although as mentioned above, Group4 & 5 are a single phone.
We then use Bandwidth total statement on GK to limit calls from the other zones out to the gateway which is registered in the Gateway zone. Each G.711 call through a gatekeeper counts 128kbps.
Your Zone Prefix commands will vary to suit your needs for inbound & outbound calls.
Please rate helpful posts.
R7#sho run | b gatekeep
zone local Group1 netpro.com 126.96.36.199
zone local Group2 netpro.com
zone local Group3 netpro.com
zone local Group4 netpro.com
zone local Group5 netpro.com
zone local Gateway netpro.com
zone prefix Gateway 1..........
zone prefix Group1 61040722..
zone prefix Gateway 610407....
bandwidth total zone Group1 256
bandwidth total zone Group2 640
bandwidth total zone Group3 384
bandwidth total zone Group4 128
bandwidth total zone Group5 128
line con 0
exec-timeout 0 0
line aux 0
line vty 0 4
R7#sho gatekeep endp
GATEKEEPER ENDPOINT REGISTRATION
CallSignalAddr Port RASSignalAddr Port Zone Name Type Flags
Of course the Cisco Gatekeeper implementation Jeff recommended does have a more scaleable CAC then CallManager locations and is the preferred method for complex configurations. The problem with the CCM CAC, is that the Location is just a single lookup, or dual if both have sides have locations set. It just tracks the numbers and if it exceeds it denys (or follows AAR if configured). It's not meshed per say like Regions are, so it's hard to do what you need.
If gatekeeper isn't an option and even then I'm not sure it'll fufill Group 3's needs, you could use COR on your H323 router (assuming the Trunk is connected to a Cisco router) to achieve what you need as well. This would involve a series of Inbound dial-peers from CCM, matching on ANI from the Groups you specified. This of course would require design work on your groups to make sure contiguous ANI numbers. From there the inbound dial-peers could have COR lists and you could craft a series of outbound dial-peers with corlists corresponding to each inbound. The outbound dial-peers would also use the max-con command to limit the outbound calling. Here is an example.
dial-peer cor custom
dial-peer cor list Group1-2out
dial-peer cor list Group2-5out
dial-peer cor list Group3-5out
dial-peer cor list Group3-allphones
dial-peer cor list Group3-phone1
dial-peer cor list Group3-phone2
dial-peer voice 100 voip
!or destination-pattern for ANI inbound
corlist incoming Group1-2out
!can be ulaw as well an gateway can then be alaw, depends on voip design.
dial-peer voice 200 voip
corlist incoming Group2-5out
dial-peer voice 300 voip
corlist incoming Group3-allphones
dial-peer voice 301 voip
!Dedicated phone 1
corlist incoming Group3-phone2
dial-peer voice 302 voip
!Dedicated phone 2
corlist incoming Group3-phone2
dial-peer voice 1 pots
corlist outgoing Group1-2out
dial-peer voice 2 pots
corlist outgoing Group2-5out
dial-peer voice 3 pots
corlist outgoing Group3-5out
dial-peer voice 31 pots
corlist outgoing Group3-phone1
dial-peer voice 32 pots
corlist outgoing Group3-phone2
Thing to remember on this configuration, is that if you have an existing inbound dial-peer using incoming called-number, then that will take precedence over the Answer-address dial-peers.
Thank you very much, really this is very helpful. I am just thinking of something, will the gatekeeper handle all this with no problems. I am not experinced using GK but say for example I will have this model that I explained in a 100 or 150 other sites (Service Provider Implementaion) all this will be okay with the gatekeeper.
The other thing that I just think of it now, do I have to create a complete dial plan for each group?? (and have the appropiate trunk for each group assigned to a gorup of IP Phones))
I really appricate ur help and for sure i will try ur ideas but I am afraid that will be very big configuration tasks and planning.
As Fred had mentioned, if you want to scale this solution the GK is more suited to your needs. I would say getting above 10 sites you would want to be there. The config was more lengthy matching on ANI & Using COR. The advantage it offers is not using the GK which many are less comfortable configuring and understanding.
The GK config was shorter but requires knowledge of GK Call Routing & possibly hardware. As for your question on inbound calls from the GK to the CCM. The CCM will not care where calls route IN from, so long as appropriate CSS is set on the trunk itself in CM. Your original question was limiting OUTBOUND calls, which was addressed in both solutions.
The flowchart in this GK Doc is indispensable. Use it with Debug Gatekeep Main 10 (or 5)(hidden debug).
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: firstname.lastname@example.org Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...