Webex Error 1000:1020?

[rikardkrvaric]

Not technically Webex Calling - more like Webex with CSF (what board is that?)

Recently, anyone that is new to the organization is not able to connect to their CSF profile in the Webex App.

We use CUCM 12.5, and have CSF devices for all people that need phones.
It used to work fine, people would login to Webex, and then it would ask you for username/password for the phone portion.
Recently, we're getting this error, and I am not sure why.

• We have Option 150 setup in all DHCP scopes, so it should know where to go for UC services.
• My _cisco-uds._tcp.example.com is resolving correctly.
• In the Webex Help Center article, 1000:1020 is not mentioned.
• On my iPhone, i can come in from outside, so my Webex phone is connected via MRA, but once i get on the Wifi, I am no longer connected. If i disconnect Wifi, it hits the MRA and it works again.

What am i missing here?
Does it not use option 150 for DHCP anymore?

[Joe_Tseng1]

Did you fixed this issue? Thx.

[mm322]

In case still useful (and although not recommended), this can be troubleshooted also by allowing non-secure Unified CM registrations (i.e. without trusted certificates).

If you want to test this go to Control Hub > Calling > Unified CM Settings and enable the option 'Allow Unified CM registration without trusted certificate'.

Based on my experience the error 1000:1020 can be connected with certificate issues.

Hope this helps.

MN

[Shalid Kurunnan Chalil]

Hi,

The CSFXXXXX is only being used for softphones (Windows-based), and it never uses option 150. Instead, it will be using the SRV record _cisco-uds._tcp.domain.com. In your case, I believe it will be _cisco-uds._tcp.hccs.edu (based on your screenshot). Ensure that you can resolve the above _cisco-uds._tcp.hccs.edu and get the call manager server FQDN. Also, it doesn’t resolve _collab-edge when you are connected via WiFi

Additionally, ensure you have connectivity to your call manager when connected via WiFi. I assume the WiFi you are referring to here is your enterprise WiFi.

Here are the initial checks to be done while you are connected to WiFi:

1. Check the SRV record _cisco-uds._tcp.hccs.edu to ensure it resolves to the correct call manager FQDN.
2. Check the SRV record _collab-edge._tls.hccs.edu; make sure it is not resolving to the Expressway FQDN.
3. Ensure that you have connectivity to the call manager.
4. Ensure that you can access https://<CUCM IP/FQDN>:8443/cucm-uds/version.

Replace the domain with correct domain if it is wrong here.

Also, you may try testing with Jabber and see the result. and see in your control hub, you have selected the correct profile assigned to the affected user (i believe you are using connected UC here). if not, please provide your current setup.  

Regards,

Shalid 

Disclaimer:

Responses are based on personal knowledge and experience. Consider them as guidance. Other members may offer different perspectives or better approaches. No responsibility is assumed for outcomes; discretion is advised.