05-27-2019 01:06 AM
Will there be a fix for this on Cisco 7800 and 8800 phones at some point?
We have over 400 Hunt Pilots and it would be a lot of work to just put quotation marks and then delete them in a later update.
Thanks
Danny
Solved! Go to Solution.
05-27-2019 06:33 AM - edited 05-27-2019 06:35 AM
We found a quick solution for that issue.
We ran two SQL statements in the publisher CLI to put quotation marks to every hunt pilot:
run sql update numplan set alertingname = CONCAT('"',alertingname) where tkpatternusage=7 AND alertingname NOT LIKE '\"%' run sql update numplan set alertingname = CONCAT(alertingname,'"') where tkpatternusage=7 AND alertingname NOT LIKE '%\"'
We needed to use two statements because the CONCAT in CUCM only supports 2 arguments, so we put quotation marks in front in the first statement and behind in the second one. We also added a condition to check, if the pilot already has quotation marks.
tkpatternusage=7 declares a numplan entry (dn or pattern) as hunt pilot.
Best Regards
Danny
05-27-2019 06:33 AM - edited 05-27-2019 06:35 AM
We found a quick solution for that issue.
We ran two SQL statements in the publisher CLI to put quotation marks to every hunt pilot:
run sql update numplan set alertingname = CONCAT('"',alertingname) where tkpatternusage=7 AND alertingname NOT LIKE '\"%' run sql update numplan set alertingname = CONCAT(alertingname,'"') where tkpatternusage=7 AND alertingname NOT LIKE '%\"'
We needed to use two statements because the CONCAT in CUCM only supports 2 arguments, so we put quotation marks in front in the first statement and behind in the second one. We also added a condition to check, if the pilot already has quotation marks.
tkpatternusage=7 declares a numplan entry (dn or pattern) as hunt pilot.
Best Regards
Danny
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide