Home › Knowledgebase › KB-1653

How To Customise Outbound Caller ID in Microsoft Teams

Summary

This guide helps you troubleshoot and resolve: How To Customise Outbound Caller ID in Microsoft Teams. Follow the steps below to fix the issue.

Quick Tip: Need immediate assistance? đź’» Open a Ticket

Common Causes

Configure Outbound Caller ID in Microsoft Teams for NDIS Providers

Outbound calls made from the Microsoft Teams mobile app can display a generic mobile caller ID rather than your organisation’s direct inward dial (DID) number. For NDIS support providers in Brisbane, this can mean participants with home phone call blockers do not recognise the number and send the call straight to voicemail. Configuring an outbound caller ID allows your Brisbane support roster to present a consistent, regionally recognised PSTN number when calling participants from mobile Teams devices.

Outbound caller ID is not controlled by Teams calling policies. Caller ID presentation is managed by your telephony carrier or SIP trunk configuration, or through phone number and resource account settings in the Teams admin centre, depending on your PSTN connectivity method. Changes must be validated by your carrier, and number formats may need to match national or international expectations for participant home phone blockers to recognise the Brisbane DID.

Quick Fix Steps

  1. Identify the Brisbane DID linked to your NDIS support roster.
  2. Confirm the number is assigned and active in your Microsoft 365 tenancy.
  3. Configure outbound caller ID through the correct path for your telephony setup: Voice > Phone numbers, resource accounts, or Direct Routing/SIP trunk configuration.
  4. Assign the Brisbane DID to the appropriate users or resource accounts used by support workers.
  5. Test outbound calls from the Teams mobile app to confirm the correct number displays.

Detailed Instructions

1. Identify the Authoritative Brisbane DID

  1. Sign in to the Microsoft Teams admin centre with administrator credentials.
  2. Navigate to Voice > Phone numbers.
  3. Locate the Brisbane geographic DID linked to your support roster.
  4. Confirm the number is assigned, active, and valid within your tenancy.
  5. Verify with your telephony carrier that the Brisbane DID can be presented as outbound caller ID. Number porting or carrier validation may be required before the number can be used for caller ID purposes.

2. Configure Outbound Caller ID Based on Your Telephony Setup

The configuration path depends on how your organisation connects to the PSTN.

Microsoft Calling Plans or Operator Connect

  1. In the Teams admin centre, go to Voice > Phone numbers.
  2. Select the Brisbane DID you want to use as the outbound caller ID.
  3. Assign the number to the relevant users or resource accounts used by support workers making calls from Teams mobile.
  4. If using resource accounts, configure the resource account with the Brisbane DID and assign it to the call queue or auto attendant handling participant calls.
  5. Contact your carrier to confirm the number is authorised for outbound caller ID presentation on your SIP trunk or Calling Plan.

Direct Routing

  1. In the Teams admin centre, go to Voice > Direct Routing.
  2. Review your SBC (Session Border Controller) configuration and SIP trunk settings.
  3. Configure the outbound caller ID at the carrier or SBC level so the Brisbane DID is presented on outbound PSTN calls.
  4. Assign the Brisbane DID to the appropriate users or resource accounts in Teams.
  5. Validate with your carrier that caller ID overrides are permitted and that the number format matches Australian national numbering expectations.

3. Assign the Number to Users or Resource Accounts

  1. Go to Users > Manage users.
  2. Select the support worker who makes outbound calls from the Teams mobile app.
  3. Under Account or Voice, assign the Brisbane DID or resource account configured for outbound caller ID.
  4. Click Save.
  5. Repeat for additional support workers, or use batch assignment if multiple users require the same Brisbane DID.

4. Test from the Teams Mobile App

  1. Open Microsoft Teams on a mobile device.
  2. Place a test call to a participant’s home line.
  3. Note that mobile Teams app calls may use different routing than desktop Teams calls depending on network and app configuration, so test specifically from the mobile app.
  4. Ask the participant to confirm the caller ID displays your Brisbane DID rather than a mobile number.
Overriding outbound caller ID can affect emergency services. Emergency calls rely on accurate caller ID and location information to route to the correct emergency response centre. Presenting a Brisbane DID that does not match the caller’s physical location may delay emergency response or route the call incorrectly. Do not override caller ID for users who may need to place emergency calls from locations outside the Brisbane DID’s service area without confirming emergency routing with your carrier.

Troubleshooting

Caller ID Still Shows a Mobile Number

Participant Home Phone Still Blocks the Call

Emergency Call Routing Concerns

Configuration Path Not Available

If you need assistance configuring outbound caller ID for your NDIS support team, Open a Ticket.

Still Having Issues?

Need more help? If the issue persists after trying these steps, please open a support ticket and our team will assist you.

đź’» Open a Ticket