Soft phones

You have to provide your own soft phones (we recommend VTGO IP Blue) while using our rack. Our rack does not provide any soft phones (including PSTN) so all soft phones have to be provided by you. This is to allow you to test actual voice traffic from your computer. Please read the PDF file for more information on setting this up on your computer. Please remember to change the MAC address for ephone 1 in the PSTN router.

Hard phones (Not supported by us)

(Adapted from http://blog.ipexpert.com/2009/06/22/hardware-phones-with-software-vpn-and-the-future-of-ccie-voice-v3-product-development/)

Note: The instructions given below are for a wireless interface connecting to the Internet and the Ethernet interface connecting to the phones. You can do the same with both interfaces being Ethernet.

Here are simple directions on how you can easily use Cisco Hardware IP Phones with your Cisco Software AnyConnect Client:

1. When you have a rack session connect to us via your wireless network interface, and simply ensure that the AnyConnect VPN works properly, and that you can ping what you should be able to ping. (Eg, ping the VPN router 10.10.10.1)
   
   
2. Setup ICS (Internet Connection Sharing) so that your Ethernet shares your WiFi connection (this means, configure NAT on your wireless interface for traffic from the Ethernet interface). Your Ethernet will attach either to a 802.3af powered switch which has connected to it all of your hardware phones (all in one VLAN for ease of setup); or else if you don’t have a 802.3af switch then you can connect one of the phones’ “Switch” ethernet ports directly to your laptop/desktop Ethernet port, and then daisy-chain all of the other hardware phones that you have together – making sure that phone 2’s “Switch” port connects to phone 1’s ”PC” port, and so on and so on. These can all be straight-through ethernet cables that you use.
   Then you will need to power all 5 phones with individual power cubes, bearing in mind that any 7960 phones (PSTN and BR2 Phone 2) only need 6.3W of juice, but that the 7962 phones will need 15.4W, so your power cube size may vary.  (Link to setup ICS on a Mac running 10.5) (Link to setup ICS on Windows Vista) (Link to setup ICS on Windows XP)
   
   
3. From the Settings Button: Set all of your phones to Static  IP Addressing, making sure that they are all on the same IP Subnet as your Mac/PC Ethernet port is statically set to, set your Default Gateway to the IP Address statically assigned to your Mac/PC Ethernet port, and then statically point TFTP to the following addresses (you do not need to turn on “Alternate TFTP” since that is only when you are running DHCP, and here you are not): For the 2 phones (HQ Ph2 & BR1 Ph2) pointed to the CUCM Cluster: TFTP = 10.10.210.10
   For the 2 phones (BR2 Ph3 & BR2 Ph4) pointed to the CUCME Cluster: TFTP = 10.10.110.3 ; For the 1 phone (7960 PSTN) pointed to the PSTN Cluster: TFTP = 10.10.10.253 (remember to change the MAC address for ephone 1 in the PSTN router).

To test if your ICS is working, you can use another computer. Set the IP accordingly and the default gateway to the computer's Ethernet address. If you have Internet access, your ICS is working. However, if you have problem, please try the following to configure NAT instead of ICS. (Taken from http://www.nanodocumet.com/?p=14). For Windows Vista and 7, please run everything in administrator mode.

Follow these steps to have your Windows XP to work as a NAT but without the restrictions of ICS (Internet Connection Sharing)

Requirements:

   1. To have two network cards:
         1. NIC1: One connected to the internal network (any network not only 192.168.1.0).
         2. NIC2: The other one connected to the Internet (or other network you want to connect to)
   2. To have administrative access to stop/start some services.

Steps:

   1. Disable ICS on both NICs.
         Right-click on NIC -> Properties -> Advanced. Make sure Allow other network users to connect through this computer’s Internet connection is unchecked.
   2. Enable Routing and Remote Access Service.
         Control Panel -> Administrative Tools -> Services. Enable Routing and Remote Access
   3. Disable Firewall/ICS Service (which might take precedence over step 1)
         Control Panel -> Administrative Tools -> Services. Disable Windows Firewall/Internet Connection Sharing (ICS)
   4. Configure the NICs:
         Only 1 should have a gateway (In my example is NIC2). Disable the gateway on the other NIC (NIC1)
         Add the NAT configuration.
            - You still need to find out the name of your network cards. Here are presenting them as NIC1 and NIC2. In reality they could be something like “Local Area Connection”
            type the command netsh

            pushd routing ip nat
            uninstall
            install
            set global tcptimeoutmins=1440 udptimeoutmins=1 loglevel=ERROR
            add interface name="NIC2" mode=FULL
            add interface name="NIC1" mode=PRIVATE
            popd

And that’s it!. Your users on the private network can go to the internet using NAT, just make sure they can route their packets through this configured PC.