cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
421
Views
0
Helpful
5
Replies

CSCwf24116 - WebEx App UCM Calling - Centralized Call History

JoshuaL1
Level 1
Level 1

Was wondering if there was any update on when this fix would be pushed out. We've had this issue for some time now within our deployment.

1 Accepted Solution

Hi Joshua,

This issue is fixed in webex version 45.X. You need to make sure the user account is associated on lines of both webex app and desk phones.  Additionally, centralized call history should be enabled in Connected UC.

Thanks,

Dijin

View solution in original post

5 Replies 5

mparra.fusionet
Level 1
Level 1

Hi @JoshuaL1 , we turned this on for a multi CUCM cluster environment and had to turn it off (temporarily, we want it) because we had shared lines associated at the DN level to a user, hence when the user would get a missed call the other phones that were associated to the shared line would see the missed calls of the user.

 

we are cleaning up our configuration to bring this feature back, I am curious in understanding what cases are not replicating to the WebexApp or if it is just a random behavior where some calls don’t replicate t the webex app.

 

i am asking this because we want this feature back and the bug itself doesn’t seem to specify if there is some logic to the missed calls.

At least on our end of things it appear to be random, as some users have no issues, some users have issues only with external calls, other only internal calls, and then some with both. There's no pattern on who has what issue as far as I can tell. 

Hi Joshua,

This issue is fixed in webex version 45.X. You need to make sure the user account is associated on lines of both webex app and desk phones.  Additionally, centralized call history should be enabled in Connected UC.

Thanks,

Dijin

We did end up fixing the issue. The issue was that the user accounts weren't associated with the lines for the webex softphones like you mentioned. Not sure why that was a problem all of the sudden but once I knew the fix it was a quick thing to implement. 

Great!