{"id":568,"date":"2004-09-21T00:00:00","date_gmt":"2004-09-21T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2004\/09\/21\/ford-in-major-shift-to-voip\/"},"modified":"2021-12-30T11:37:42","modified_gmt":"2021-12-30T11:37:42","slug":"ford-in-major-shift-to-voip","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2004\/09\/21\/ford-in-major-shift-to-voip\/","title":{"rendered":"Ford in Major Shift to VoIP"},"content":{"rendered":"<p>Ford Motor Co. (Quote, Chart) will move 50,000 employees at 110 facilities to Voice over IP (define) calling, a ringing endorsement for the emerging technology&#8217;s performance and reliability.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>SBC Communications (Quote, Chart) will design, install and manage the project using IP phones and network equipment from Cisco Systems.<\/p>\n<p>The Ford VoIP deployment will occur over three years and impact the headquarters and other facilities in southeast Michigan.<\/p>\n<p>Profits aside, the Ford contract could serve as a case study for SBC and Cisco to present to other large corporations that may have misgivings about VoIP.<\/p>\n<p>Ford is expected to save money over its Centrex (define) phone system in several areas, including the decrease in its long-distance bills.  The company also expects system maintenance to decline by shifting voice and data onto a single IP network.  Also, IP telephony service makes handling employee moves more efficient, because businesses can scale up or down without calling vendors or ordering new cards.<\/p>\n<p>http:\/\/www.internetnews.com\/infra\/article.php\/3410681<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[29],"tags":[],"class_list":["post-568","post","type-post","status-publish","format-standard","hentry","category-news"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/568","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=568"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/568\/revisions"}],"predecessor-version":[{"id":3055,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/568\/revisions\/3055"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=568"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=568"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=568"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}