Cisco Bug: CSCvt55070 - SIP registration issue with Anyconnect VPN turned on two Windows PCs
Sep 02, 2020
- Cisco Jabber for Windows
Known Affected Releases
11.6(1) 11.7(0) 11.7(1) 12.9(0)
Symptom: SIP registration issue with Anyconnect VPN turned on two Windows PCs Conditions: The issue is related to AnyConnect defect CSCtd44727. Anyconnect always uses the same virtual MAC address 00059a3c7a00 on Widnows platform. Since Jabber uses MAC address in sip.instance which identifies registration instance, CUCM will always accept new registration instead of prompting Jabber there is an existing registration. The result is both old and new clients will show registered. But actually CUCM only treats the recent registered client as active client. Outbound calls will fail and no incoming calls appear on old Jabber client. Afterwards, The old client and new client will register itself alternatively before registration expires. Calls will work alternatively on the two clients. Steps to reproduce: 1, Turned on Anyconnect on 2 Windows PC. 2, Register Jabber on two PCs. 3, Both show phone service connected, but only the latest client can make or receive calls. 4, Wait the first client to register again, then calls work on the first client and not work on second client 5, Wait the second client to register again, then calls work on the second client and not work on first client. You can also reproduce it when you have both teams calling client and Jabber on the same PC when VPN is turned on.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases