Cisco Systems Network Provisioning and Configuration Cisco MeetingPlace Express Networking Provisioning and Configuration Copyright 2006 Cisco Systems Page 1
Cisco Systems Network Provisioning and Configuration Table of Contents 1 2 Introduction................................................................................................................. 3 Network Provisioning Considerations ........................................................................ 3 2.1 Voice over IP (VoIP) Voice................................................................................ 3 2.1.1 Bandwidth Settings .........................................................
Cisco Systems Network Provisioning and Configuration 1 In tr o d u c tio n This white paper describes information that may be useful when installing Cisco MeetingPlace Express. This white paper is designed to be used in conjunction with the Administrator’s Installation, Upgrade, and Troubleshooting Guide for Cisco MeetingPlace Express Release 1.1. It is not intended to be used in place of that guide.
Cisco Systems Network Provisioning and Configuration 2.1.1 B a n d w i d t h Se t t i n g s Cisco MeetingPlace Express supports only G.711 (mu-law or a-law). Within the core network, Cisco recommends allowing the end points to use G.711 when communicating with Cisco MeetingPlace Express, without employing a transcoder. Assuming the default packet size of 20ms, each voice endpoint can send and receive approximately 84Kbs of constant bandwidth traffic, including packet overhead.
Cisco Systems Network Provisioning and Configuration In a lecture-style meeting, latency generally does not matter. However, in an interactive discussion, high latency breaks the normal conversation model, causing serious frustration as people attempt to break into a conversation and discover they can’t without colliding with someone else. If you are finding that the conversation flow seems unnaturally difficult, it may be because of high latency on one or more of the connections.
Cisco Systems Network Provisioning and Configuration The aggregate quantity varies considerably due to several factors. In a steady state with no presenters or no screen updates, traffic will average well under 1Kbs per client. In the worst case, with complex, rapidly presented materials, it is possible for Cisco MeetingPlace Express to sustain output in excess of 1Mbs per client, or well over 100Mbs on aggregate in a 120 port system.
Cisco Systems Network Provisioning and Configuration server limits the output to each client according to the lesser of that client’s connection setting and the meeting room setting. For example, say the meeting room is set to DSL, the presenter is set to LAN, one client is set to DSL, and one client is set to Modem. The meeting room setting of DSL overrides the presenter’s LAN setting, so the presenter transmits to the server at a maximum of 250Kbs.
Cisco Systems 2.3 Network Provisioning and Configuration E n d -U se r I n t e r f a c e a n d Ad m i n i st r a t i on Ce n t e r On the whole, Cisco MeetingPlace Express HTTP traffic is neither high bandwidth nor real-time in nature and is relatively insignificant compared to other traffic types. However, during the period when meetings are starting, particularly in the few minutes right after the hour, you should assume many users will hit the server for the purpose of attending a meeting.
Cisco Systems Network Provisioning and Configuration traditional (PSTN) links and voice gateways to achieve high voice quality for external callers. Voice end points can reduce their bandwidth usage by employing low-bit-rate coders or compressed headers. Note, however, that Cisco MeetingPlace Express does not natively support any CODEC except G.711; nor does it support compressed RTP. If you wish to use a low-bit-rate coder, you will need to introduce a transcoder.
Cisco Systems • • • Network Provisioning and Configuration You will need at least two IP addresses and two host names, configured both in Cisco MeetingPlace Express and in Domain Name System (DNS). Choose one of the three supported port configuration models. If audio is divided onto a separate network, use static route settings to assure traffic will go to the right network. 3 .
Cisco Systems Network Provisioning and Configuration 3 .2 Con f i g u r a t i on Mod e l s Consistent with the above rules, the following configurations can be supported: (Only the voice, HTTP, and RTMP services are listed because the other services can be accessed using any of the IP addresses assigned to the server.) 1. One Ethernet port, two IP addresses: a. Primary: HTTP and voice b. Secondary: RTMP 2. Two Ethernet ports, two IP addresses: a. Port 1 (eth0): HTTP and voice b. Port 2 (eth1): RTMP 3.
Cisco Systems Network Provisioning and Configuration conferencing on another, thus separating the high bandwidth traffic from the time critical traffic. The assignment of services to IP addresses and IP addresses to Ethernet ports, described above, can provide good control of incoming traffic. However, this only partially controls how Linux divides outbound traffic. Cisco MeetingPlace Express only supports traditional Linux (UNIX) packet routing.
Cisco Systems Network Provisioning and Configuration The net command is menu driven. First, choose option 4, Configure service bindings. This lets you select the port model (described in Configuration Models). After selecting the port model, go to the main menu and choose option 1, List current configuration. You can change configuration parameters here. When you quit, the net command verifies some of the settings to ensure that they are consistent. If they are not consistent, you can correct them.
