Белая книга для Cisco Cisco Unified MeetingPlace Express 1.1
Cisco Systems
Network Provisioning and Configuration
Page 10
•
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 .1 S e r v i c e s, I P Ad d r e sse s, a n d Host n a m e s
Some of the services running on Cisco MeetingPlace Express bind to specific IP
addresses, as follows:
addresses, as follows:
Services
Binding
End-User Interface and Administration Center (HTTP/S)
HTTP IP address
Web conferencing (RTMP/S)
RTMP IP address
Voice signaling (SIP and H.323)
Any IP address
Audio data (RTP/RTCP)
IP address bound to port 1 (eth0)
Other services
2
Any IP address
Due to the need to distinguish the HTTP and RTMP traffic and the desire to allow them
both to connect using a single firewall-friendly port (80 or 443), it is necessary to assign
different IP addresses to these services.
It is further necessary for the HTTP and RTMP IP addresses to have a distinct hostname
configured in the DNS. To be sure that service binding works correctly, it is vital that the
HTTP and RTMP hostnames, corresponding IP addresses, and domain name are
configured the same way in the DNS tables as in the Cisco MeetingPlace Express
configuration. Hostnames must match exactly, except for capitalization, or the URLs
generated by Cisco MeetingPlace Express will be incorrect.
The only hostname that needs to be exposed to end users is the one for HTTP. Names and
addresses associated with the other services are normally transparent.
2
SSH, SNMP, and NTP