Route patterns, CSS and Partitions with H.323

Unanswered Question
Nov 18th, 2007
User Badges:

Can someone detail from a best practices standpoint how route patterns/CSS/Partitions on the CCM should be configured if using h.323 as gateway protocol?

In our design, we will have three sites each with PSTN connectivity (HQ houses CCM/VM). Phones need to be seperated by COS (local, local and LD, local LD and International).

So in the above, do I just create a single route pattern on the CCM for each site (9.@) and then specify the more specific router patterns on the h.323 dial-peers? And then also impliment COS on each h.323 gateway so I can differentiate each COS groups dialing ability?

Or should we use traditional partitions and CSS's on the CCM, and then for each location setup a local, ld and international route pattern (pointing to the respective h.323 gateway). Then essentially have the same setup on the h.323 from a destination-pattern perspective (that matches route patterns on CCM for each location)? And thus it will be on the CCM that determines which route patterns a phone has access too?

thanks in advance,

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (2 ratings)
Chris Deren Sun, 11/18/2007 - 07:40
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,
  • Cisco Designated VIP,

    2017 IP Telephony, Contact Center, Unified Communications

Configure all of your COS configuration on CallManager using either traditional or line/device approach, there is no need to build COR on the GW unless you want to retain the same COS under SRST conditions. The challange with COR is the ongoing meintenace, everytime you will change phone's COS or add a phone you will need to modify the GW.




This Discussion