服务班级

在此博客中，我们将继续使用呼叫搜索空间（CSS）和分区（PT）来继续我们的Cisco Unified Communications Manager（CUCM）Service（COS）实现。在最后一个博客中，我们介绍了出站呼叫路由的示例。回想一下，呼叫方的CSS确定拨号计划中的哪些路由模式可访问。CSS可以访问各种分区，并且将路由模式应用于分区。此博客将通过网关和树干从其他系统覆盖入站呼叫路由。让我们来看看一个分布式的多簇呼叫处理模型，我们有群集A和群集B.群集A和B具有H.225中继线在IP云中的H.323网守。网守具有站点间呼叫路由拨号计划和呼叫准入控制（CAC）策略，以限制可以放置在广域网（WAN）上的呼叫数。If calls between cluster A with directory number (DN) range 11XXX and cluster B (DN range 12XXX) are failing, attention should be paid to the CoS configuration at both cluster A and B. The calling party’s phone in cluster A must have a calling search space configuration which has access to the route pattern partition that is pointed to the H.323 gatekeeper. The following configuration is the CSS configuration of the calling party: •Calling Party (11001) -> Calling Search Space ClusterA_CSS •ClusterA_CSS: internal_pt, local_pt, e911_pt, ld_pt, ict_pt •Route Pattern 12XXX -> ict_pt Cluster A call routing configuration: •Route pattern 12XXX -> InterSite_RL -> WAN_RG -> H.225 Trunk to GK Based on the configuration above, CoS and call routing to the H.225 trunk pointed to the H.323 gatekeeper is properly configured at cluster A. Assuming the gatekeeper is properly configured and there are no CAC challenges, the configuration of cluster B’s H.225 trunk should be inspected. Calls inbound to cluster B from the H.225 trunk will take on the CSS that is applied to the trunk. Trunks have a CSS applied in the inbound call routing section of the trunk configuration. The CSS is used to restrict how call from the trunk can be routed. Cluster B’s perspective is that the trunk is the calling party and the DN dialed (DNIS) is the called party. •Calling Party (trunk) -> Calling Search Space Internal_CSS •Internal_CSS: internal_pt •Directory number 12001-> internal_pt The CoS configuration above would not allow a tail end hop off (TEHO) implementation because the CSS of the trunk does not allow access to any of the partitions that are used for outbound call routing. The Internal_CSS is only being used as an example. Calls from the PSTN accessed through a gateway have the same inverted approach of CoS. Calls from the PSTN (or other TDM based device) will take on the CSS of the gateway to determine which dial plan elements the inbound PSTN calls have access to. More fun with calling search spaces in the next blog….