<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
     xmlns:content="http://purl.org/rss/1.0/modules/content/"
     xmlns:dc="https://purl.org/dc/elements/1.1/"
     xmlns:dcterms="http://purl.org/dc/terms/"
     xmlns:media="http://search.yahoo.com/mrss/"
     xmlns:atom="http://www.w3.org/2005/Atom"
>
    <channel>
                    <atom:link href="https://www.tvtechnology.com/feeds/tag/intercom-matrix" rel="self" type="application/rss+xml" />
                            <title><![CDATA[ Latest from Tv Technology in Intercom-matrix ]]></title>
                <link>https://www.tvtechnology.com/tag/intercom-matrix</link>
        <description><![CDATA[ All the latest intercom-matrix content from the Tv Technology team ]]></description>
                                    <lastBuildDate>Fri, 11 May 2018 18:09:48 +0000</lastBuildDate>
                            <language>en</language>
                                <item>
                                                            <title><![CDATA[ Guidelines and Requirements for Next-Gen IP-based Intercom Systems ]]></title>
                                                                                                                                                                                                <link>https://www.tvtechnology.com/opinions/guidelines-and-requirements-for-next-gen-ip-based-intercom-systems</link>
                                                                            <description>
                            <![CDATA[ Intercom systems are used in fixed and mobile broadcasting, entertainment, houses of worship and other applications that require coordination of real-time production. ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">94QGE6cdbWm2D9PPzWuWfK</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/GmAA8W4pjRMuz3SVFb7zJT-1280-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Fri, 11 May 2018 18:09:48 +0000</pubDate>                                                                                                                                                                                                                                <category><![CDATA[Opinion]]></category>
                                                    <category><![CDATA[Insights]]></category>
                                                                                                                    <dc:creator><![CDATA[ Fredrik Borjesson and John Ball ]]></dc:creator>                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/GmAA8W4pjRMuz3SVFb7zJT-1280-80.jpg">
                                                            <media:credit><![CDATA[null]]></media:credit>
                                                                                                                                                                        <media:description><![CDATA[Microsoft Production Studios recently finished upgrading their Cisco Systems infrastructure to Cisco 9508 chassis. The new units are ready to handle just about any IP production thrown at them with their four 100 Gbps links bonded for a 400 Gbps throughput creating the redundancy between them. The remote switches around the facility are 10 Gbps bonded for 20 Gbps throughputs to these cores. MPS’s systems engineer,    ]]></media:description>                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/GmAA8W4pjRMuz3SVFb7zJT-1280-80.jpg" />
                                                                                        </item>
            </channel>
</rss>