Packetstream income tax full#
Cisco Unified CME has features that address this, although currently you cannot treat a network of many Cisco Unified CME systems as if they are a single logical entity with full intersite feature transparency. In some cases, you might want to treat H.323 calls as internal calls and not want a high degree of differentiation in the treatment of LAN versus WAN calls, such as calls between separate systems on two floors of the same building. This division is useful in many ways, because it inherently supports the often-necessary difference in treatment of calls between internal and external phone users. You can view the H.323/SIP versus SCCP contrast as the difference between interbranch office voice traffic and intrabranch office voice traffic, or alternatively as long distance (WAN) versus local VoIP (LAN). Although SCCP technically does use VoIP technology, it is primarily used in the context of operating voice calls within the confines of a LAN with more or less unlimited bandwidth and many fewer concerns about security. This interpretation excludes SCCP used to control local IP phones. The term VoIP here specifically describes "long-distance" VoIP telephone calls that traverse a WAN. Cisco Unified CME uses SCCP for phone control, and SCCP shares many common traits with MGCP. Cisco Unified CME itself does not support control of MGCP endpoints. Many MGCP Call Agent implementations (using MGCP internally for phone control) use H.323 or SIP to connect separate Call Agents (as intersystem peer-to-peer). Of course, it is still possible to connect Cisco Unified CME to MGCP networks, primarily using either H.323 or SIP. In contrast, this similarity between H.323 and SIP does not extend to Media Gateway Control Protocol (MGCP) (and also Skinny Client Control Protocol ), which takes a significantly different approach to telephony. Therefore, you also need some kind of telephone number directory system to be able to resolve the IP address of the appropriate destination VoIP peer device for intersite calls. For networks built on either H.323 or SIP, you are dealing with peer-to-peer communication between sites. The shared aspects of the two protocols means that the overall high-level architecture and distribution of hardware and primary component roles within your VoIP network don't significantly depend on which protocol you choose to use for intersite VoIP. Some technical and protocol-specific differences exist between H.323 and SIP VoIP networking, but for the most part, you'll find more commonality than difference, at least at the level of technical detail that this chapter addresses. However, many of the high-level VoIP networking considerations that apply to H.323 apply equally in the SIP context. Because H.323 is more mature than SIP, you can expect to see increased real-world interoperability between different vendors' H.323 products, particularly with basic call handling. H.323 is the dominant protocol deployed for VoIP networks from an installed-base perspective. Note For additional information, see the "Related Documents and References" section on page xii.Ĭonsiderations When Integrating Cisco Unified CME in H.323 and SIP VoIP Networks
The following sections address specific multiple Cisco Unified CME deployment issues: This chapter focuses on the call handling implications of using Cisco Unified CME in a network. It examines some of the considerations that apply within a networked environment that do not arise in simpler standalone configurations. This chapter describes the ways in which you can use Cisco Unified CallManager Express (Cisco Unified CME) as a component of a larger network using the two major Voice over IP (VoIP) protocols-H.323 and SIP-to link multiple Cisco Unified CME systems. Public and Internal Phone Numbers in a SIP NetworkĬonnecting Multiple Cisco Unified CallManager Express Systems with VoIP.Integrating Cisco Unified CME in a SIP Network.Cisco Unified CME Local Supplementary Services.H.450.12 Supplementary Services Capabilities.Call Transfer and Call Forwarding in an H.323 Network Using H.450 Services.Transporting DTMF Digits Reliably Using DTMF Relay.Registering Individual Telephone Numbers with a Gatekeeper.Public and Internal Phone Numbers in an H.323 Network.Using a Gatekeeper as a Proxy for Additional Services.Integrating Cisco Unified CME in an H.323 Network.Considerations When Integrating Cisco Unified CME in H.323 and SIP VoIP Networks.
0 kommentar(er)
