类的服务

在这篇博客中，我将讨论线路/设备类服务(CoS)方法。在以前的博客中提到的传统的呼叫搜索空间方法对于涉及少数站点的小规模部署是足够的。•4个呼叫搜索空间(CSS)•7个分区(PT)•7个路由模式(RP)。大多数统一通信部署都需要到本地网关的呼叫路由。本博客不考虑使用IP电话服务提供商(ITSP)。如果你想在以后的博客中讨论这些，我很乐意。在我们的示例网络中，本地路由调用需要为CUCM集中呼叫处理体系结构中的每个站点配置18个元素。50个站点部署将需要900个配置元素。900个配置元素使统一通信部署的持续操作、管理、维护和供应(OAM&P)复杂化。线路/设备CoS方法通过每个站点只使用一个不受限制的呼叫搜索空间，将每个站点所需的呼叫搜索空间数量限制为一个。在线路级别上使用了三个集群范围的呼叫搜索空间，以显式地阻止应该有拨号限制的电话呼叫。 This approach leverages the fact that CUCM processes a concatenation of both the line and the device calling search spaces when defined at both the line and device level. CUCM processes the line CSS and then the device CSS. The device CSS includes all of the route patterns for that particular site and steers traffic to the local gateway through the route pattern > route list > route group > gateway call routing processing. The device calling search space is unrestricted and includes every PSTN route pattern. Call restrictions are applied explicitly at the line level through the use of a few cluster-wide CSS that include access to translation patterns with a block action. The line CSS explicitly blocks calls before the device CSS is considered. Additional information on these two approaches from the CUCM 7.x SRND appear at the end of this blog. I’ll talk about some more applications of CSS in the next blog. Building classes of service using the traditional approach http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/7x/dialplan.html#wp1150934 Building classes of service using the line/device approach http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/7x/dialplan.html#wp1150997