[cisco-voip] CUC Speech Connect Ports

Tue Jun 23 11:48:39 EDT 2020

I don’t think there’s any free tier of speechconnect, you have to pay for it regardless of it you use standard or professional, and I don’t recall it ever having been included in an ELA.

My understanding of it is that it’s “assisted” and not using the magic Webex Assistant technology. I clicked on the box the other day just for novelty and it pops up saying that you agree by clicking on this that portions of conversations may be sent to a third party for transcription. This mechanical turk method I think is what a number of other recognition/OCR “apps” used. I don’t speak for my org in this capacity so I clicked cancel.

As far as the speech recognition goes, I believe it uses the Nuance engine in the background. We have a large international population which is hopeless with this thing, but even some bog standard stuff is just impossible.  You can supply alternate grammars, but, at one point I found myself having it read things back to me to get an idea of what it thought the grammar was, I don’t think it uses any sort of markup there. Setting the confidence level lower helped somewhat but it also delayed the response on the speech enabled auto attendants. The ONLY benefit to this thing that I’ve found is that it lets dial-by-name directories work if the customer hasn’t recorded their own name.

We looked at a myriad of these back in the day, I think Parlance had the better solution since it was turnkey and fully taken care of, but, last time I’d looked the price had gone up and it wasn’t very many ports when we were talking about all the IVRs we wanted to put into it. Back then I don’t think they really intended for it to front end 100 departments and a main number.

Adam

From: cisco-voip <cisco-voip-bounces at puck.nether.net> On Behalf Of Anthony Holloway
Sent: Tuesday, June 23, 2020 11:34 AM
Cc: Cisco VoIP Group <cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] CUC Speech Connect Ports

As a follow up, if you find yourself in this situation, you could just recover from a backup....yuck....or you can use the built-in stored procedures via CUDLI to just put your parameters back.

First, you need the Object ID for each of the target objects.  You can use the query builder in CUDLI to get these:

select objectid, tagname from tbl_licensestatus where tagname in ('LicRealspeakSessionsMax', 'LicUnityVoiceRecSessionsMax')

[cid:image001.png at 01D64954.3A2E6D50]

Next, you need to execute a stored procedure called csp_licensestatusmodify, once for each objectid, filling in the default value of 2 for each of the three fields below:

[cid:image002.png at 01D64954.3A2E6D50]
[cid:image003.png at 01D64954.3A2E6D50]

This will not create any ports:

[cid:image004.png at 01D64954.3A2E6D50]

Nor add to your license requirements:

[cid:image005.png at 01D64954.3A2E6D50]

On Mon, Jun 22, 2020 at 5:55 PM Anthony Holloway <avholloway+cisco-voip at gmail.com<mailto:avholloway%2Bcisco-voip at gmail.com>> wrote:
Thanks for the reply Lelio, but no this is not specific to the voice enabled directory handler.

This is specific to the Speech Connect ports and accompanying licenses.  This affects generated spoken names and voice enabled directory handlers.

However, I would like to update you that you can search mailboxes and contacts in the same search.  Also, the list is updated automatically, especially after you add alternate names for a person, though the system does come with a built-in list of common nicknames.  E.g., Mike for Michael.

Thanks again for the reply.

PS, What sparked this question was someone configured some ports (they didn't know what they were doing), and then removed them (because it shows 0 by default), and now CUC is broken, because the GUI removes the 2 default ports (which cannot be seen in the GUI).

This is documented here: https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvt31253

In fact, the only way I have seen that you can view the defaults, is in a protected licensing table.

CLI Method
admin:run cuc dbquery unitydirdb select tagname, limit, clusterwidelimit, restartlimit, usage from tbl_licensestatus where tagname in ('LicRealspeakSessionsMax', 'LicUnityVoiceRecSessionsMax')

This 'sql_statement' is not allowed. You are not allowed to perform CRUD operations on License Tables through CLI.
Command Failed

CUDLI Method
[cid:image007.png at 01D64954.3A424370]

On Mon, Jun 22, 2020 at 3:26 PM Lelio Fulgenzi <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>> wrote:

Are you talking ‘bout the voice activated auto attendant?

If so, we investigated and stopped a project for the amount of work necessary to get it working in our environment.

At the time you could only search mailboxes or a contact list, not both. Because we had more than just mailboxes, we went with contact list.

There was no way to update the list at the time so it was a delete all and recreate via csv or something like that.

I think the interpretation was ok. So was saying the names. But your stuck with what you got. No grammar updates.

So Guelph would be “gwelp” no matter what.

We ended up going with Nuance. Which has announced EOS at end of next year I believe.

We might revisit connection.
Sent from my iPhone

On Jun 22, 2020, at 12:24 PM, Anthony Holloway <avholloway+cisco-voip at gmail.com<mailto:avholloway%2Bcisco-voip at gmail.com>> wrote:

CAUTION: This email originated from outside of the University of Guelph. Do not click links or open attachments unless you recognize the sender and know the content is safe. If in doubt, forward suspicious emails to IThelp at uoguelph.ca<mailto:IThelp at uoguelph.ca>

I'd like to hear your personal stories.  Do you configure these?
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200623/ab566b62/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 33068 bytes
Desc: image001.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200623/ab566b62/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 36305 bytes
Desc: image002.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200623/ab566b62/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 36888 bytes
Desc: image003.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200623/ab566b62/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 3834 bytes
Desc: image004.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200623/ab566b62/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 15442 bytes
Desc: image005.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200623/ab566b62/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image007.png
Type: image/png
Size: 79963 bytes
Desc: image007.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200623/ab566b62/attachment-0005.png>