Using CUPC over Remote Access VPN (ASA)

Unanswered Question
Sep 2nd, 2010

I have an issue whereby when a user connects to their infrastructure via VPN and they connect to the CUPC server, they do not get any presence information. I read other posts which suggested that turning off SIP inspection would resolve the issue. This did work to an extent however, when I made the change and the user logged back in to CUPC all the presence user ids changed from [email protected] to [email protected] (1111 being the extension number rather than user id). Therefore the change whilst fixing one issue appears to have introduced another.

Also, am I right in thinking that disabling SIP inspection would ultimately cause problems if the customer did want to allow SIP voice or messaging through the ASA also.

Does anyone know how to fix the new issue or are there any design guides for this to get CUPC working whilst retaining SIP inspection ?



I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Marcin Latosiewicz Sat, 09/04/2010 - 03:28


Looks to me a strange behavior in SIP inspection. Normally on a VPN if no NAT is done you can safely disengage SIP inspection (unless you also need dynamic pinholes to be created for some reason).

I'd say get the ASA to latest CCO image in your train and if that still does not work - open a TAC case.



This Discussion