I am wanting to understand the concept of IP Communicator working from home over a VPN registering with on-site CallManager.
Customer reports that when the register their IPC on their company laptop at home. The IP phone registers but when a call is originated, set up, but no RTP is passed.
The concept will be along the lines of the layer 2 MAC registering on the CallManager will be the PC's MAC and not as traditionally I.E hard phones MAC.
I understand the UDP ports assigned for RTP.
What I am wanting to fully understand is what needs to be built on the customer network to facilitate this - I can appreciate customer firewalls etc but what would be the base requirements if we consider the voice and data sit on different VLAN's.
Any guidance to further clarify would be most appreciated...
Software VPN clients are overlaid on top of an existing IP network, meaning that there are essentially two IP addresses on the computer when a VPN is in use:
"The IP address from the underlying network
"The IP address provided by the VPN client that is used by parties on the remote side of the connection to communicate with applications on the computer
Some VPN clients, such as Cisco Systems VPN Client 3.x, assign the VPN IP address at a very low level, which makes it difficult for Cisco IP Communicator to specify the correct address. To eliminate this problem, Cisco IP Communicator queries the Cisco VPN client directly.
Other VPN Clients, such as the Microsoft PPTP client and Cisco VPN Client 4.x appear as alternative network interfaces. In these cases, the IP address can be selected with the same auto-detection process that is used to resolve selection when there are multiple interfaces.
Other third-party VPN clients might be unsupported and result in one-way audio. You can resolve this problem by running the Cisco IP Communicator Administration Tool to create a getIP.asp audio IP address reflector web page as described in the "Resolving Audio IP Address Auto-Detection Problems" section. Cisco IP Communicator attempts to fetch this reflector page rather than using other methods of auto-detection. The reflector page returns the IP address from which it sees the request originate, which is a relatively reliable way to identify VPN IP address of Cisco IP Communicator.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: firstname.lastname@example.org Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...