12-26-2015 03:24 PM - edited 03-19-2019 10:31 AM
Hello Support Team,
i have updated my Lab Environment to Unity Connection 11. (11.0.1.21900-11)
The New Missed Call Email Notification is really a great feature.
but can i configure that the Caller Name is sent within the Email?
it works only if the caller has a Mailbox withing Unity connection, but if the caller has no Mailbox, his Name is always send as " from unknown" in the email.
in the Remote Port Status Monitoring Tool i can see that cuc is receiving the Caller Name from CUCM.
Solved! Go to Solution.
07-15-2016 09:38 AM
Hi there,
I would have a look at this bug;
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCuz80965
12-27-2015 07:39 PM
Hi,
As per the CUCC admin guide the caller name should be displayed if it is being received by Unity Connection, please check the following
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/11x/administration/guide/11xcucsagx/11xcucsag140.html#pgfId-1170249
If the settings are verified and the issue is still there then i would recommend opening a TAC case.
Manish
- Do rate helpful posts -
12-28-2015 07:11 AM
Hello Manish,
thank you for your answer.
it really looks like a bug, because if the same caller leaves a message then the synchronized message has the correct Caller Name. but if the caller does not leave a message then the missed call notification has an Caller name of "Unknown".
07-15-2016 07:26 AM
unfortunately the behavior is the same on Unity Connection 11.5(1).
in the notification email i get the correct name only if the User has a Unity Connection Mailbox.
so for a caller that do not leave a message: i get a Missed Call Notification Email from Unity Connection without the Caller Name
if the same caller leaves a Message and it get's synced to my exchange i can see the Caller Name.
so it seems to be intended to be that way, but i don't think that this is a good design to take the name only from Unity Connection Users because i don't have so much license to put in all my external Contacts as users...
09-09-2016 01:11 AM
The Bug is solved with CUC 11.5.1.11900-26
07-15-2016 09:38 AM
Hi there,
I would have a look at this bug;
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCuz80965
08-01-2016 01:00 AM
great, thanks!
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