12-11-2013 12:42 PM - edited 03-18-2019 02:17 AM
Hi,
I have a problem that I can't setup login and password on SIP Profile 1 config page. Each time I set it up and refresh page, login and password is missing and diagnostics show me error "401 Unathorized" when registering to SIP Proxy (VCS).
Software version 6.3.
Any idea how to setup it without factory reset?
EDIT: I have found that if I disable SIP protocol, set username and password, it is there. But immediately after I enable SIP back, username and password is missing.
Thanks
Solved! Go to Solution.
12-11-2013 04:52 PM
Hey Tibor,
This is due to CSCuj48259. If you go into your sytem and set your provisioning mode to Off, it will resolve the issue.
This defect has not yet been resolved, however it is being addressed in a future software release. I
f you are running TC 6.2 or higher you will have this issue if you have your provisioning mode set to auto and the auto discovery of a provisioning back end succeeds but supplys a blank username and password to your system. Also, if it is set to auto and DHCP option 150 is configured on that network, it will attempt to provision with CUCM which would clear these fields.
12-11-2013 01:58 PM
Most probably same issue as mentioned in this thread:
https://supportforums.cisco.com/thread/2240415?tstart=0
/jens
Please rate replies and mark question(s) as "answered" if applicable.
12-11-2013 02:51 PM
It sounds you are using the webinterface, does it happen as well when you use ssh and xconfig to set it?
Please remember to rate helpful responses and identify helpful or correct answers.
Please remember to rate helpful responses and identify
12-11-2013 04:52 PM
Hey Tibor,
This is due to CSCuj48259. If you go into your sytem and set your provisioning mode to Off, it will resolve the issue.
This defect has not yet been resolved, however it is being addressed in a future software release. I
f you are running TC 6.2 or higher you will have this issue if you have your provisioning mode set to auto and the auto discovery of a provisioning back end succeeds but supplys a blank username and password to your system. Also, if it is set to auto and DHCP option 150 is configured on that network, it will attempt to provision with CUCM which would clear these fields.
12-11-2013 05:30 PM
Chad: the bug is not public visible, could you follow up that this is going to be set to public?
Would setting the username and password in TMS for example fix that issue?
Please remember to rate helpful responses and identify helpful or correct answers.
Please remember to rate helpful responses and identify
12-12-2013 06:30 AM
Hey Martin,
That is correct. If you were to supply the credentials using a TMS provisioning template, then that could also resolve the issue. I will work to have the bug publicly viewable!
12-12-2013 06:49 AM
thanks, disable provisioning resolved issue. thanks
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: