Teams call displays long string of random numbers on carkit when connected to vehicle over bluetooth with iPhone

Aaron Adler 0 Reputation points
2026-10-12T23:48:23.8833333+00:00

General Motors filing a Bluetooth Defect with Carkit

cluster and center screen displayed the call name as a super long string of numbers, see video. Should be displaying the name of the meeting or something more intuitive instead of a bunch of random numbers.

After analyzing the Bluetooth logs, When VCU requested for current calls list to remote iPhone but remote phone responded with Phone Number: "[Moderator note: Personally Identifiable Information removed]". Its remote phone is sending the long list numbers.

Next Action:

We need to check with Apple-OEM, so we need iPhone Sysdiag logs + gmlogger + video.

Log snippet:

VCU requested with AT+CLCC → Query List of current calls and remote phone resounded with call info. Phone Number: "[Moderator note: Personally Identifiable Information removed]" which is display on screen.

Microsoft Teams | Microsoft Teams for business | Teams on mobile devices
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. BabybooHN 3,465 Reputation points Independent Advisor
    2026-10-13T00:14:54.76+00:00

    Dear @Aaron Adler

    Thank you for providing the detailed Bluetooth logs and explaining the findings from General Motors. I understand your concern about the unusually long numeric string appearing on the vehicle’s instrument cluster and center display during Microsoft Teams calls.

    Based on the log you provided, the vehicle sends the AT+CLCC command to request the current call information, and the iPhone responds with the long numeric value.

    This confirms that the vehicle receives the value through the Bluetooth connection. However, it does not yet confirm whether the value originates from Microsoft Teams, iOS, or the interaction between them.

    I recommend the following steps to isolate the issue:

    1. Compare different call types: Using the same iPhone and vehicle, compare a regular cellular call, a Teams one-to-one call, and a Teams meeting. Check whether the long numeric string appears only with Teams.
    2. Test another iPhone: If possible, repeat the test using another iPhone with the latest supported iOS and Teams versions. This can help determine whether the behavior is device-specific.
    3. Collect synchronized diagnostic logs: I agree with your proposed next step of collecting the iPhone sysdiagnose logs, GM logger data, and video evidence. I would also recommend collecting Teams mobile diagnostic logs and recording the exact timestamp and time zone of the issue. Microsoft provides instructions here: Send diagnostic log files from Microsoft Teams mobile
    4. Escalate for further investigation: If the issue occurs only during Teams calls, I recommend opening a Microsoft 365 support case through your organization’s administrator and providing the reproduction steps, Teams version, iOS version, Bluetooth logs, and timestamps. Since the AT+CLCC response is generated through the iPhone’s Bluetooth interface, coordinating with Apple and the vehicle manufacturer’s engineering teams would also be appropriate.

    I also found a previous Microsoft Q&A discussion describing a similar issue where Teams calls displayed unexpected numeric caller IDs on a vehicle screen: Teams caller ID displaying random numbers over Bluetooth

    Although this suggests similar behavior has been reported before, it does not establish that the underlying cause is identical.

    Could you please confirm whether the issue occurs only during Teams meetings or also during one-to-one Teams calls?

    This distinction would help narrow down whether the behavior is related specifically to Teams meeting identification or more generally to iOS call information handling.

    I hope this helps guide the investigation.

    Was this answer helpful?

  2. AI answer

    2026-10-12T23:49:18.8733333+00:00

    The AT+CLCC trace shows that the vehicle is displaying the call identifier supplied by the iPhone, so this should be filed as an iPhone–Teams–Bluetooth interoperability defect with synchronized iPhone, vehicle, and Teams logs rather than addressed through a Teams caller-ID policy.

    1. Reproduce the issue with exact timestamps
      • Record the iPhone model, iOS version, Teams iOS version, vehicle model/year, VCU or infotainment firmware, and Bluetooth profile/version if known.
      • Capture the Teams meeting/call type: scheduled meeting, Teams-to-Teams call, or PSTN call.
      • Record a video showing the long number on both the cluster and center display.
      • Note the timestamp, time zone, caller/callee, and meeting link or ID. Do not post those identifiers publicly.
    2. Collect the three log sets from the same reproduction
      • iPhone: Apple Sysdiagnose immediately after reproducing.
      • Vehicle: GM logger/VCU Bluetooth logs containing the complete Hands-Free Profile exchange, including the AT+CLCC request and response.
      • Teams: In Teams for iOS, open profile picture → Settings → Help and feedback → Send feedback, enable Attach logs to help troubleshoot, and submit the report. This option must be enabled by the organization’s administrator. Teams mobile logs contain app-process diagnostic information and can contain usernames or email addresses, so transfer them only through approved support channels.^1^
    3. Correlate the evidence Include the relevant vehicle-log line, for example: 
         Vehicle → iPhone: AT+CLCC
   iPhone → Vehicle: ... "
   Vehicle UI:        

        Also document whether the value is:
      • Stable for the same meeting.
      • Different for each meeting or call.
      • Present only for Teams calls.
      • Absent during ordinary cellular calls and calls from another iPhone application.
      If ordinary cellular calls display correctly but Teams calls do not, include that comparison prominently. It narrows the defect to the Teams/iOS Bluetooth call-signaling path rather than general vehicle contact resolution.
    4. Open coordinated cases
      • Submit the Sysdiagnose and vehicle Bluetooth trace to Apple/OEM engineering for interpretation of the value returned to AT+CLCC.
      • Have the Microsoft 365 administrator open a Teams support request and attach the video, sanitized Bluetooth excerpt, reproduction matrix, Teams feedback timestamp, and case references from Apple and GM. Microsoft’s support workflow accepts logs, screenshots, and video as attachments.^2^

    What the current evidence establishes

    The vehicle is not generating the number: its request asks the iPhone for the current call list, and the iPhone returns the long numeric value that the vehicle then renders. However, that trace alone does not determine whether Teams generated the identifier, iOS transformed it, or the Bluetooth integration mapped an unsupported field into the telephone-number field.

    Teams caller-ID policies are unlikely to correct this. Those policies govern PSTN calling line ID (CLID) and calling party name (CNAM), including substituting a user or resource-account number or using Anonymous.^3^ They do not document control over the value returned by iOS in a Bluetooth AT+CLCC response. A meeting title also is not documented as CLID or CNAM, so the vehicle cannot be assumed to receive or display the meeting name through the generic Bluetooth call-list interface.

    Supported workaround

    If the affected GM vehicle supports Apple CarPlay, use the Teams CarPlay application instead of the generic Bluetooth call screen. Microsoft supports Teams calls and audio-only meetings through CarPlay; its Meetings view displays that day’s meetings and lets the user join them directly.^4^

    This is a workaround, not proof that the Bluetooth behavior is correct. Keep the defect open if the requirement is for the cluster or native center display to show a meaningful Teams call label without CarPlay.

    References

    1. Send diagnostic log files from Microsoft Teams mobile app | Microsoft Support
    2. Create a support request for Teams device issues
    3. Manage caller ID for users - Microsoft Teams | Microsoft Learn
    4. Place Microsoft Teams calls with Apple CarPlay
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.