'Bridge' networking does exactly that - makes your PC NIC, and the VM NIC work as if they are physically connected to the same VLAN/subnet.
What it doesn't do is any IP magic, so you have to ensure that your PC NIC and VM NIC have iP addresses that are layer-2 adjacent.
To prove this, set your PC NIC to 10.1.1.2, and then browse to 10.1.1.1.
Typically I would either:
1) Set the CUCM to be on an IP address of my home LAN, as 90% of the time this is where I use the VM
2) Set the networking to 'host only' on the VM. You will have a host-only NIC linked to this network, and can see the address of it when you look in the VMWare networking prefernces. You would need to give the VM an IP that matches this subnet. Bear in mind that host-only means just that - other hosts (IP phones on your LAN, other PCs) cannot reach the VM, but you could have a CIPC on your computer (or in a another VM on the same host-only virtual network) that could register to it.
Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...