CMR SIP alias via Productvity tools

Question

Recently added CMR and running into an issue with SIP Alias for video endpoints.  When scheduled via the Webex portal, the SIP alias is correct ([email protected]).  However when we schedule using Productivity Tools or via Jabber, it schedules the meeting fine but then assigns the video alias differently.  Rather than users firstname.lastname, it assigns the meeting number as the video alias.  So now its [email protected]  I need to figure out how to create a consistent meeting invite.

Answer 1

Hi,
So your current situation is that you are using AnyConnect with Split-tunneling? So you can access the LAN through VPN and Internet through the users local Internet connection?
I wonder if the problem with Full-Tunnel + Internet traffic is due to problem with NATing the traffic from VPN Client pool to the "outside" interface IP?
I think that NAT could be done by the following configuration
object network VPN-POOL
subnet 192.168.0.200 255.255.255.248
nat (outside,outside) after-auto source dynamic VPN-POOL interface
EDIT: The "after-auto" should take the rule at the bottom of the NAT rules, but I'm still thinking should it interfere with the configurations even if it didnt have the parameter.
I've only done this in software 8.2 and below, where it was
global (outside) 1 x.x.x.x
nat (inside) 1 10.10.10.0 255.255.255.0
nat (outside) 1 192.168.0.200 255.255.255.248
But as I said I havent done this with the new software. I can probably test this tomorrow at work though.
- Jouni
EDIT2:
I'm not 100% sure but is the following NAT statement even needed at the current configuration?
nat (inside,outside) source static any any destination static NETWORK_OBJ_192.168.0.200_29 NETWORK_OBJ_192.168.0.200_29
EDIT3:
I also usually use a totally different network for the VPN-pool. Your current LAN seems to be 192.168.0.0/24 and the VPN pool is 192.168.0.200/29. Maybe the top NAT statements are causing problems with the VPN Client Internet traffic.
What I would try to do is change the VPN Client pool to some different network, do the NAT0 between LAN and POOL like you have in the current configuration (just with new VPN Pool) and use the PAT configuration mentioned earlier. Leave out the NAT statement in the "EDIT2" in this post.
Sorry this is alot of guessing from my part before I get to test it myself with a lab ASA.