[cisco-voip] CUC Speech Connect Ports

Anthony Holloway avholloway+cisco-voip at gmail.com
Mon Jun 22 18:55:53 EDT 2020


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*
[image: image.png]

On Mon, Jun 22, 2020 at 3:26 PM Lelio Fulgenzi <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> 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
>
> I'd like to hear your personal stories.  Do you configure these?
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> _______________________________________________
> cisco-voip mailing list
> 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/20200622/356bbe04/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 34136 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200622/356bbe04/attachment.png>


More information about the cisco-voip mailing list