The virtualized IBM
® Unified Telephony deployment requires that 4 subnets be presented to it as labels during virtual machine creation. Each of these labels needs to be in a different subnet as presented to Sametime
Unified Telephony; these subnets are used in building the node.cfg
file for installing the Telephony Control Server.
You can configure the subnets based on the type of configuration you are installing, described in Virtualized servers using VMware
. In each case these 4 subnets are required (each subnet would be assigned to specific network interface card):
- Admin subnet (assigned to NIC1)
Used for administration and maintenance information.
- Signaling subnet (assigned to NIC2)
Used for SIP/CSTA/MGCP signaling.
- Cross Connect (assigned to NIC3)
Used for call state synchronization:
- When virtual machines are co-located on the same host, this is a virtual-switch-only connection.
- When virtual machines are co-located on separate hosts, this is a direct gigabit-quality ethernet cable cross connect.
- When virtual machines are a geo-separated system, this can be either an L2 bridged connection or an L3 routed connection.
- Billing subnet (assigned to NIC4)
Used for sending CDRs to the billing server.
The connection of the labels to the real network is dependent on the customer’s network configuration. This can be a flat or segmented network and can also use the VMware VLAN capability. VMware network interface redundancy can also be used if required. The exception to this is the cross-connect link, which due to the heavy traffic carried and the L2 nature of co-located or L2 bridged geo-separated connections should be a dedicated link.
The subnets must be created as type E1000 in the virtual machine.
Parent topic: Requirements for the virtualized Telephony Control Server