I'm using a Cisco VPN concentrator 3000 and when two laptops are connected out of the office with VPN, they can't speak to each other with their IP Softphone. Signalisation is good because we can see the flashing key. But media stream is lost...The 2 laptops are on the same address range.
No problem with PSTN or other internal phones.
How can I configure the VPN concentrator 3000 to enable routing for voice ?
Call signaling is working because it is between the Callmanager and IP Phone, not the two phones. Have you tried pinging from one communicator to the other, I bet you can't do it. The problem here is that a typical VPN configuration does not allow two remote connections to talk to each other. It sounds like what you need is Dynamic Multipoint VPN or DMVPN.
DMVPN allows two remote locations to have a direct IPSec link between the two of them to pass traffic directly without going through a hub location.
Another thing to check is to make sure that your audio traffic is being sourced from your VPN interface. You can verify this by going to the preferences menu, select the "Audio" tab, click the "Network" button and verify that the "Audio IP Address" is that of your VPN interface or the interface itself.
If you can't implement DMVPN and you find that is your problem, you can always hairpin the audio through a gateway as a temporary solution. If the communicators have DID's, just dial those instead of the on-net extensions. Obviously that will tie up two channels of your PSTN dialtone, but it will temporarily solve the problem.
I have done this without multipoint. What you need dto do is ensure that the subnet they are both on is pushed out to them via the client, so that it appears in the route list. When I added this to our vpn clients we were successfull in vpn to vpn use of softphones.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.