![\"Deploying_Cisco_Voice_Over_IP_Solutions_www.default.am\"](\"http:\/\/www.default.am\/wp-content\/uploads\/2012\/01\/Deploying_Cisco_Voice_Over_IP_Solutions_www.default.am_-228x300.jpg\" "\\"Deploying_Cisco_Voice_Over_IP_Solutions_www.default.am\\"")
<\/p>\n<\/p>\n
Deploying Cisco Voice Over IP Solutions<\/p>\n
<\/p>\n
This book is a sequel to Voice over IP Fundamentals, published by Cisco Press in
\n2000. Since the publication of that book, there has been a fundamental change in
\nthe assumptions made by those in the telecommunications industry. Instead of
\nincumbent telecommunications service providers attempting to determine whether
\npacket voice will be a viable technology, they are attempting to determine the right
\nopportunity to begin deploying this technology. These providers are either actively
\nresearching the technology, conducting lab trials, or deploying it. In addition,
\nexisting TDM equipment providers have determined that they must provide packet
\nvoice equipment in addition to their TDM equipment. These equipment providers are
\nforced down this path due to the fact that their customers want and need to
\npurchase this type of equipment.
\nThe next phase of packet voice will focus not just on lowering equipment costs
\n(capital expenditures), but lowering operating expenditures. This phase will be
\ncompleted over time by integrating voice technology into Network Management
\nSystems (NMS) owned by incumbent carriers as well as integrating IP data NMS
\ntechnology and packet voice network management systems.
\nAlthough service providers realize that there are many benefits to packet voice
\ntechnology, they also recognize that there are potential downsides to this
\ntechnology. The largest of the potential caveats is multi-vendor equipment
\ninteroperability. Although there are many standards defining how devices should
\ncommunicate with each other, there are few standards defining how these
\nindependent standards should communicate with each other. One example is how
\nmany existing networks utilize H.323 to signal voice calls over IP. There are several
\nnewer protocols, however, that appear to have momentum in this space\u2014MGCP,
\nMEGACO, and SIP, for example.<\/p>\n
The good news about protocol interworking is that there is much work being done in
\nthis space. Each major protocol has its own interoperability event at least yearly.
\nThere is a good analogy that can be drawn from the data networking industry. There
\nare dozens of routing protocols currently in use across the world for routing IP across
\nheterogeneous networks (OSPF, IS-IS, BGP, EIGRP, and so on), and all of these
\nprotocols must interoperate with one another in order for IP networks to be truly
\nubiquitous. This interoperability has, of course, been accomplished. Another
\ncomparison that can be drawn between packet voice signaling protocols and IP
\nrouting protocols is that there is a definite need for each of these protocols in certain
\ntypes of networks, and one cannot expect to erase the need for another. In the
\npacket voice space, a newer protocol such as MEGACO may be better for certain
\napplications, but it doesn’t solve the same problem that protocols such as H.323
\nsolve. Therefore, they are both necessary, and interoperability between the two is
\nrequired.
\nThe interoperability between equipment vendors will be solved, and then the next
\nlevel of interoperability will bubble to the surface\u2014that of service interoperability, or
\nhow users can utilize a similar application across an entire service area in a similar
\nmanner.<\/p>\n
<\/p>\n
Download<\/strong>: link 1<\/strong><\/a> | link 2<\/strong><\/a><\/p>\n","protected":false},"excerpt":{"rendered":" Deploying Cisco Voice Over IP Solutions<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26,3,9],"tags":[],"class_list":["post-230","post","type-post","status-publish","format-standard","hentry","category-ccvp","category-cisco","category-other"],"_links":{"self":[{"href":"http:\/\/www.default.am\/index.php?rest_route=\/wp\/v2\/posts\/230","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.default.am\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.default.am\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.default.am\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.default.am\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=230"}],"version-history":[{"count":1,"href":"http:\/\/www.default.am\/index.php?rest_route=\/wp\/v2\/posts\/230\/revisions"}],"predecessor-version":[{"id":232,"href":"http:\/\/www.default.am\/index.php?rest_route=\/wp\/v2\/posts\/230\/revisions\/232"}],"wp:attachment":[{"href":"http:\/\/www.default.am\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=230"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.default.am\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=230"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.default.am\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=230"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}