locked
SfB call history showing incorrect name when calling mobile number, or direct number forwarded to mobile RRS feed

  • Question

  • I have a strange scenario in which any call to a users mobile, or direct number forwarded to any mobile number, shows the name of the caller (not callee) in the call history list. The contact card shows the correct callee information and the email in outlook is correctly populated. The only difference within the email, is that it shows only the caller as a recipient, and not the callee. This problem is global and there's no difference if the mobile number is from AD or entered manually in the SfB client.


    Troubleshooting steps:

    - Client Cache deleted

    - Client updated


    Environment:

    - 1 x SfB Standard (6.0.9319.277)

    - 1 x SfB Edge (6.0.9319.277)

    - Client version 16.0.6925.1049

    - Windows 10 Build 14393

    - Audiocodes SBC VE 7.20A.102.001


    Any tips would be greatly appreciated as I am unable to find any similar cases in my searches.


    • Edited by Jagassar Tuesday, June 13, 2017 11:52 AM
    Tuesday, June 13, 2017 11:44 AM

All replies

  • Hi Jagassar,

    Did this issue only appear on the specific user or all users had this problem?

    In the addition to the troubleshooting steps above, please also try the following steps:

    1. Try to perform a clean boot on your computer: https://support.microsoft.com/en-us/kb/929135
    2. Also try to repair office.
    3. You could also try to test with another user check if there is the same issue.
    4. For SFB server side, please check if there are any event IDs in your SFB FE server.
    5. If the issue just appeared on the specific user, please compare user attributes between the affected user and other normal users.

    Hope this reply is helpful to you.


    Regards,

    Alice Wang


    Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, June 14, 2017 2:00 AM
  • Hello Mrs Wang

    Thank you for your reply.

    1. Clean boot performed -> Same problem

    2. Repair ran -> Same problem

    3. This is a global issue

    4. There are no relevant errors found on the Frontend server

    5. see point 3

    Thanks for any other tips! :)

    Regards

    Greg

    Friday, June 16, 2017 9:55 AM
  • Hi Jagassar,

    Are there the same issue between desktop client and desktop client?

    Did you use a PSTN call? If you use a PSTN call, we suggest you check the configuration of the SIP trunk

    If possible, please try to create a new user for test purpose, then check if the issue persists.


    Regards,

    Alice Wang


    Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, June 22, 2017 7:17 AM
  • Hello Wang

    Yes the problem is the same between all clients and is present while calling a mobile (PSTN call). The Trunk config seems to be ok when compared to working environments.

    Regards

    Greg

    Monday, June 26, 2017 7:53 AM
  • Are there any event IDs in the application log of SFB FE server side?

    Regards,

    Alice Wang


    Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Proposed as answer by Alice-Wang Wednesday, July 19, 2017 8:22 AM
    Monday, July 3, 2017 8:21 AM
  • Sorry for the late reply!

    We have performed this mobile test and find no indication of it in the event logs on the any SFB server.

    Wednesday, August 2, 2017 12:40 PM