Accessing and using Microsoft Teams on smartphones and tablets across platforms
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.
Recommended defect-isolation package
- 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.
- 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+CLCCrequest 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^
- 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.
- 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^
- Submit the Sysdiagnose and vehicle Bluetooth trace to Apple/OEM engineering for interpretation of the value returned to
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