Configure the Network

Configure the Network
Configure the Network
• DHCP Pool Setup, page 1
• Domain Name Resolution, page 1
• Configuration Files, page 2
• Open Required Ports in Firewalls, page 2
DHCP Pool Setup
If your network uses DHCP, specify the domain name in the DHCP pool. Without this setting, DHCP does
not assign a domain to the thin clients. Therefore, the devices cannot register with the Cisco Unified
Communications Manager, the client keypads are dimmed, and users cannot make calls.
Example:
ip dhcp pool Non-VXCM server
network 10.2.209.0 255.255.255.0
dns-server 10.2.25.11
default-router 10.2.209.1
domain-name rtpvxi.com
!
Domain Name Resolution
If thin clients reside in a different domain than the Cisco Unified Communications Manager, the DNS server
may be unable to resolve the domain name for the Cisco Unified Communications Manager.
To resolve this issue, edit the /etc/hosts file on the thin client. To save the change permanently, edit the wlx.ini
file. Add the AddtoEtcHosts= parameter, and specify the IP, FQDN, and aliases for each
Cisco Unified Communications Manager in the cluster. This parameter adds entries to the /etc/hosts file, where
aliases are an optional space-separated list of hostnames.
For more information about how to edit the wlx.ini file, see the INI reference guide for the thin client.
Syntax
AddtoEtcHosts= "ip1 FQDN1 aliases1;ip2 FQDN2 aliases2"
Deployment and Installation Guide for Cisco Virtualization Experience Media Engine for SUSE Linux Release 10.6
1
Configure the Network
Configuration Files
Sample wlx.ini File
;*************************************************************
;* General 1 *
;*************************************************************
AddtoEtcHosts="10.200.252.2 CUCM123.cisco.com CUCM123;10.100.7.117 CUCM456.cisco.com CUCM456"
IniFileSource=cache
;*************************************************************
;*
Connections
*
;*************************************************************
Browser.Homepage=http://gwydlvm120
CONNECT=BROWSER \
Description="Citrix-HVD" \
URL=www.cisco.com \
AutoConnect=yes \
Sound=yes \
mode=normal
Configuration Files
For each Cisco Unified Client Services Framework (CSF) device that you add to the system, Cisco Unified
Communications Manager creates a configuration (CNF.xml) file. The CNF file contains the device
specifications for the associated user.
When users sign in to their supported Cisco Unified Communications application, Cisco Virtualization
Experience Media Engine starts the download of the associated CNF file to the thin client. To ensure the
successful transfer of the file, open the relevant ports in all firewall applications to allow the thin client to
access the ports. For more information about how to open ports, see the documentation for the firewall software.
Important
Download of the CNF.xml file follows the system setting for HTTP proxy. Ensure that the proxy does
not route the HTTP request from the thin client outside of the corporate network.
Open Required Ports in Firewalls
If the network includes firewalls, you may have to open ports. See Ports Reference Guide for Cisco
Virtualization Experience Media Engine Release 9.0, available from:
http://www.cisco.com/en/US/docs/voice_ip_comm/vxc/english/vxme/9.x_ports_ref/b_vxme_
ports-reference-guide.html
Deployment and Installation Guide for Cisco Virtualization Experience Media Engine for SUSE Linux Release
10.6
2
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising