Teams location-based routing

See also

Sources

1. 1
   For code 510546, Microsoft's article says to check the Teams calling policy with Get-CsTeamsCallingPolicy if you don't use Direct Routing, and to set PreventTollBypass to False with Set-CsTeamsCallingPolicy if it is True.

   SIP 403 and Microsoft response codes - Microsoft Teams · Section '510546 403 ...', second bullet · Checked 2026-09-25
2. 2
   For Direct Routing LBR, inbound PSTN calls from an LBR-enabled gateway can connect to an auto attendant, but calls to a call queue are not supported.

   Plan Location-Based Routing for Direct Routing · Inbound calls through Auto attendants, first paragraph · Checked 2026-09-25
3. 3
   LBR is enforced for specific users by turning on 'Prevent toll bypass and send calls through the PSTN' in the calling policy assigned to them (the PreventTollBypass setting of the Teams calling policy).

   Enable Location-Based Routing for Direct Routing · Using the Microsoft Teams admin center > Enable Location-Based Routing for calling policies · Checked 2026-09-25
4. 4
   Direct Routing LBR supports Teams desktop clients (Windows and Mac), Teams mobile clients (iOS and Android) and Teams IP phones; the Teams web client, Skype for Business clients and IP phones connected through SIP Gateway are not supported.

   Plan Location-Based Routing for Direct Routing · Other planning considerations > Client support for Location-Based Routing · Checked 2026-09-25
5. 5
   Network configuration lookups, which LBR depends on, are not supported with cloud proxy service deployments that modify the source IP addresses of Teams clients.

   Network settings for cloud voice features · Trusted IP address, Important box · Checked 2026-09-25
6. 6
   Microsoft response code 10500 with SIP 403 ('Current call site state prevents fork to this entity') is resolved by verifying that Location-Based Routing is set up correctly.

   SIP 403 and Microsoft response codes - Microsoft Teams · Section '10500 403 Current call site state prevents fork to this entity' · Checked 2026-09-25
7. 7
   Microsoft response code 510546 with SIP 403 ('Get Outbound Direct Routing - no trunk config found by LBR selection criteria') is expected when LBR restricts toll bypass at the user's location; otherwise it indicates an LBR misconfiguration.

   SIP 403 and Microsoft response codes - Microsoft Teams · Section '510546 403 Get Outbound Direct Routing - no trunk config found by LBR selection criteria', first bullet · Checked 2026-09-25
8. 8
   An LBR-enabled user on a PSTN call who has no Audio Conferencing license cannot start a conference with another user or PSTN number, though connecting to auto attendants is allowed.

   Plan Location-Based Routing for Direct Routing · Location-Based Routing for conferencing, first paragraph · Checked 2026-09-25
9. 9
   Microsoft's Location-Based Routing planning article applies only to Direct Routing; it states that this form of LBR does not apply to Calling Plan, Teams Phone Mobile, Operator Connect, or Operator Connect in India.

   Plan Location-Based Routing for Direct Routing · Introductory paragraphs before the Note · Checked 2026-09-25
10. 10
    Microsoft's enable article assumes Direct Routing is already deployed and network regions, sites and subnets are already configured before LBR is enabled.

    Enable Location-Based Routing for Direct Routing · Introductory paragraphs · Checked 2026-09-25
11. 11
    GatewaySiteLbrEnabled (Boolean, default False) makes the SBC report its assigned site; on an incoming call the SBC's site is compared with the user's site to make the routing decision, and the parameter is mandatory for enabling LBR.

    Set-CsOnlinePSTNGateway (MicrosoftTeams) · Parameters > -GatewaySiteLbrEnabled · Checked 2026-09-25
12. 12
    When LBR blocks an inbound PSTN call, the call follows the called user's unanswered call forwarding settings (typically voicemail), and it disconnects if no unanswered settings are configured.

    Plan Location-Based Routing for Direct Routing · Overview > Toll bypass evaluation and outcome, notification list · Checked 2026-09-25
13. 13
    Microsoft states that deploying Location-Based Routing for Direct Routing in India also requires configuring media bypass.

    Plan Location-Based Routing for Direct Routing · Media bypass requirement for Location-Based Routing · Checked 2026-09-25
14. 14
    Microsoft states that Direct Voice over IP must not be deployed with any telephony equipment in India, and that on-network conferencing for Audio Conferencing must not be deployed with any telephony equipment in India.

    Plan Location-Based Routing for Direct Routing · Direct Voice over IP (VoIP); Location-Based Routing for conferencing, penultimate paragraph · Checked 2026-09-25
15. 15
    LBR supports both IPv4 and IPv6 subnets and checks for an IPv6 match first, falling back to IPv4 only if no IPv6 address is present.

    Configure network settings - Location-Based Routing · Define network subnets, third paragraph · Checked 2026-09-25
16. 16
    An LBR-enabled user whose endpoint is at a known site not enabled for LBR can make outbound PSTN calls through a gateway not enabled for LBR, if the user's online voice routing policy allows the call.

    Plan Location-Based Routing for Direct Routing · User is enabled for Location-Based Routing, list after the Outbound PSTN calls table · Checked 2026-09-25
17. 17
    At the time of a PSTN call, LBR determines a user's location from the IP subnet the user's Teams endpoint is connected to.

    Plan Location-Based Routing for Direct Routing · Overview, paragraph after the network topology diagram · Checked 2026-09-25
18. 18
    An LBR-enabled user on a PSTN call cannot merge it with another call, and recording or compliance recording of that PSTN call is not supported.

    Plan Location-Based Routing for Direct Routing · Location-Based Routing for conferencing, last paragraph · Checked 2026-09-25
19. 19
    All calls to and from a user not enabled for LBR must route through PSTN gateways not enabled for LBR; an inbound call to such a user that arrives on an LBR-enabled gateway goes to the user's unanswered call settings.

    Plan Location-Based Routing for Direct Routing · User is not enabled for Location-Based Routing · Checked 2026-09-25
20. 20
    Microsoft advises against using Location-Based Routing to dynamically route PSTN calls based on user location, warning that doing so may cause unintended results.

    Plan Location-Based Routing for Direct Routing · Note under the introduction · Checked 2026-09-25
21. 21
    LBR is not enforced for call park or retrieval of PSTN calls through Call Park, for an on-premises Skype for Business user calling a Teams user, or for call queues.

    Plan Location-Based Routing for Direct Routing · Other planning considerations > Capabilities not supported by Location-Based Routing · Checked 2026-09-25
22. 22
    For Operator Connect for India, the location rules also apply to PSTN calls reaching a user through an auto attendant or call queue; the user must be at the site the auto attendant or call queue number is associated with.

    Plan Location-Based Routing for Operator Connect for India · Toll bypass evaluation and outcome, list after the table · Checked 2026-09-25
23. 23
    Unlike Direct Routing, LBR for Operator Connect for India does not require enabling users, PSTN gateways or network sites for LBR; instead, India fixed-line numbers are associated with the network site they belong to.

    Plan Location-Based Routing for Operator Connect for India · Configure Location-Based Routing for fixed-line number calls, Note · Checked 2026-09-25
24. 24
    Operator Connect for India fixed-line numbers are associated with network sites using Set-CsPhoneNumberAssignment -PhoneNumber <number> -NetworkSiteId <site>.

    Plan Location-Based Routing for Operator Connect for India · Associate phone numbers to network sites · Checked 2026-09-25
25. 25
    For an Operator Connect for India fixed-line user, inbound and outbound PSTN calls are allowed only at the office location (the site associated with the number); at a remote site, another known site or an unknown site they are not allowed.

    Plan Location-Based Routing for Operator Connect for India · Toll bypass evaluation and outcome, Outbound and inbound PSTN calls table · Checked 2026-09-25
26. 26
    Microsoft's Operator Connect for India LBR article says that bypassing the PSTN provider is illegal in India and that Indian telecom service providers must block PSTN calls made or received by customers roaming outside their PSTN location.

    Plan Location-Based Routing for Operator Connect for India · Introductory paragraph · Checked 2026-09-25
27. 27
    Transfers, forwards, delegation and conferencing of an Operator Connect for India PSTN call are allowed only to other Operator Connect for India users with the same operator, and only if everyone involved is at the same network site as the Operator Connect user's number.

    Plan Location-Based Routing for Operator Connect for India · Call transfers, delegation, and conferencing, introductory paragraph and Note · Checked 2026-09-25
28. 28
    According to Khaitan & Co, India's Department of Telecommunications issued revised OSP guidelines on 23 June 2021, replacing the November 2020 guidelines, and allowed voice-call interconnection between OSP centres, including centres belonging to different entities.

    DoT's Re-vision to the OSP Framework · Article body, opening and interconnection discussion · Checked 2026-09-25
29. 29
    Microsoft describes Other Service Provider (OSP) deployments in India as a regulated category, usually for call centres, that may let calls leave India over a private network, requires an entitlement from India's Department of Telecommunications, and says Microsoft support for OSP calls with international numbers is pending.

    Plan for Operator Connect for India - Microsoft Teams · Other Service Provider (OSP) deployments · Checked 2026-09-25
30. 30
    Khaitan & Co reports that the 2021 OSP guidelines define toll bypass as carrying PSTN calls, either between India and another country or between two Indian cities, over the OSP's own network.

    DoT's Re-vision to the OSP Framework · Article body, toll bypass discussion · Checked 2026-09-25
31. 31
    When LBR blocks an outbound PSTN call, the Teams call window shows the message 'Call not allowed due to your organization's settings.'

    Plan Location-Based Routing for Direct Routing · Overview > Toll bypass evaluation and outcome, notification list · Checked 2026-09-25
32. 32
    The Set-CsOnlinePSTNGateway parameter GatewayLbrEnabledUserOverride is a Boolean with default False; it lets an LBR-enabled user outside the corporate network, or at an on-network location not configured as a tenant network site, make and receive PSTN calls through an LBR-enabled gateway.

    Set-CsOnlinePSTNGateway (MicrosoftTeams) · Parameters > -GatewayLbrEnabledUserOverride · Checked 2026-09-25
33. 33
    An LBR-enabled user at an unknown site can place and receive PSTN calls only if the call uses an LBR-enabled PSTN gateway configured with GatewayLbrEnabledUserOverride set to True.

    Plan Location-Based Routing for Direct Routing · Apply Location-Based Routing, best practices list, third bullet; outbound and inbound tables, User at unknown site row · Checked 2026-09-25
34. 34
    Microsoft says not to enable LBR on gateways that don't route calls to the PSTN (such as gateways to PBX systems), but those gateways must still be associated with the network site where the system is located so restrictions apply to PSTN calls reaching endpoints behind them.

    Enable Location-Based Routing for Direct Routing · Using PowerShell > Enable Location-Based Routing for gateways, paragraph after step 2 examples · Checked 2026-09-25
35. 35
    Some changes to Teams network settings can take up to four hours to propagate and become available to Teams clients.

    Network settings for cloud voice features · Introductory paragraphs, before the first Note · Checked 2026-09-25
36. 36
    In PowerShell, LBR is enabled on a gateway with Set-CsOnlinePSTNGateway -Identity <gateway> -GatewaySiteLbrEnabled $true -GatewaySiteID <site ID>, which also associates the gateway with its network site.

    Enable Location-Based Routing for Direct Routing · Using PowerShell > Enable Location-Based Routing for gateways, step 2 · Checked 2026-09-25
37. 37
    In PowerShell, LBR is enabled on a network site with Set-CsTenantNetworkSite -Identity <site ID> -EnableLocationBasedRouting $true.

    Enable Location-Based Routing for Direct Routing · Using PowerShell > Enable Location-Based Routing for network sites, step 1 · Checked 2026-09-25
38. 38
    Subnets are mapped to sites with New-CsTenantNetworkSubnet -SubnetID -MaskBits -NetworkSiteID, and external trusted IPs are defined with New-CsTenantTrustedIPAddress -IPAddress -MaskBits; a tenant can define an unlimited number of trusted external subnets.

    Manage your network topology for cloud voice features in Microsoft Teams · Configure network settings using PowerShell > Define network subnets; Define external subnets (external trusted IP addresses) · Checked 2026-09-25
39. 39
    The PreventTollBypass reference says not to set the parameter to True for Calling Plan or Operator Connect users because it will prevent successful call routing; it only works with Direct Routing configured for LBR restrictions.

    Set-CsTeamsCallingPolicy (MicrosoftTeams) · Parameters > -PreventTollBypass, Note · Checked 2026-09-25
40. 40
    Location-Based Routing lets an administrator restrict toll bypass for a Teams user based on policy and the user's geographic location at the time of an inbound or outbound PSTN call.

    Plan Location-Based Routing for Direct Routing · Overview, first paragraph · Checked 2026-09-25
41. 41
    For an LBR-enabled user at an LBR-enabled site other than the site of the LBR-enabled gateway the call would use (the 'remote location' case), both outbound and inbound PSTN calls through that gateway are not allowed.

    Plan Location-Based Routing for Direct Routing · User is enabled for Location-Based Routing, Outbound PSTN calls and Inbound PSTN calls tables, Remote location row · Checked 2026-09-25
42. 42
    In Teams LBR the network site voice routing policy from on-premises LBR is no longer used; the user's voice routing policy is used instead, so it must include the gateways of the sites the user roams to.

    Plan Location-Based Routing for Direct Routing · Other planning considerations > Changes from an on-premises Location-Based Routing deployment · Checked 2026-09-25
43. 43
    When an LBR-enabled user transfers or forwards an inbound PSTN call to another PSTN number, the outbound leg must leave through the same LBR-enabled gateway the inbound call arrived on.

    Scenarios for Location-Based Routing for Direct Routing · Teams user transfers or forwards call to PSTN endpoint > User enabled for Location-Based Routing, first bullet · Checked 2026-09-25
44. 44
    Inbound PSTN calls to an LBR-enabled user's DID are not routed to that user's endpoints while they are at a different site from where the DID is assigned, whether or not that site is enabled for LBR.

    Scenarios for Location-Based Routing for Direct Routing · Teams user receives an inbound call from the PSTN > User enabled for Location-Based Routing, table rows Site 2 and Site 3 · Checked 2026-09-25
45. 45
    An LBR-enabled user roaming to another LBR-enabled site has outbound calls routed through that roamed site's LBR-enabled gateway, based on the user's voice routing policy.

    Scenarios for Location-Based Routing for Direct Routing · Teams user places an outbound call to the PSTN > User enabled for Location-Based Routing, table row Site 2 · Checked 2026-09-25
46. 46
    Simultaneous ringing for an LBR-enabled user follows the same LBR rules as call transfers and forwards.

    Scenarios for Location-Based Routing for Direct Routing · Simultaneous ringing, introductory paragraph · Checked 2026-09-25
47. 47
    Transferring or forwarding an inbound PSTN call from an LBR-enabled gateway to another Teams user is allowed only if the target user is LBR-enabled and at the same network site; any other target location is not allowed.

    Scenarios for Location-Based Routing for Direct Routing · Teams user transfers or forwards call to another Teams user > User enabled for Location-Based Routing, paragraph and table · Checked 2026-09-25
48. 48
    For Direct Routing, Microsoft's best practice for LBR is a separate network site for each location with unique PSTN connectivity, and a site not enabled for LBR can be created so LBR-enabled users can make PSTN calls when they roam there.

    Configure network settings - Location-Based Routing · Define network sites, 'For Direct Routing' bullet · Checked 2026-09-25
49. 49
    The LBR documentation treats a network site as Enabled (configured and LBR-enabled), Not enabled (configured but not LBR-enabled) or Unknown (not configured as a tenant network site, whether internal or external to the corporate network).

    Plan Location-Based Routing for Direct Routing · Apply Location-Based Routing, network site states list · Checked 2026-09-25
50. 50
    Each network subnet must be associated with one specific network site; a site can have multiple subnets, but a subnet cannot belong to multiple sites.

    Configure network settings - Location-Based Routing · Define network subnets, first paragraph · Checked 2026-09-25
51. 51
    In the Teams admin center, LBR is turned on for a gateway under Voice > Direct Routing > SBCs by editing the SBC, turning on 'Enable location based routing' under 'Location based routing and media optimization', and specifying the gateway site ID and bypass mode.

    Enable Location-Based Routing for Direct Routing · Using the Microsoft Teams admin center > Enable Location-Based Routing for gateways, steps 1-5 · Checked 2026-09-25
52. 52
    In the Teams admin center, LBR is turned on for a network site under Locations > Network topology by editing the site and turning on 'Location based routing'.

    Enable Location-Based Routing for Direct Routing · Using the Microsoft Teams admin center > Enable Location-Based Routing for network sites · Checked 2026-09-25
53. 53
    For Direct Routing, LBR has to be applied to users, network sites and PSTN gateways; the PSTN gateway and the network site associated with it must both be enabled for LBR.

    Plan Location-Based Routing for Direct Routing · Apply Location-Based Routing, list and best practices · Checked 2026-09-25
54. 54
    When an LBR-enabled user transfers a 1:1 Teams VoIP call to the PSTN, the transfer is permitted only if the transferred party could make that PSTN call from their own location through the same PSTN gateway as the transferring user.

    Plan Location-Based Routing for Direct Routing · Conditions for call transfers with Location-Based Routing, first bullet · Checked 2026-09-25
55. 55
    LBR first matches the endpoint's external IP against the tenant's trusted IP list; only if it matches does it look up the internal subnet, and otherwise the endpoint is classified as being at an unknown location.

    Configure network settings - Location-Based Routing · Define trusted IP addresses (external subnets) · Checked 2026-09-25
56. 56
    'Location-Based Routing' in Teams refers to two differently configured mechanisms: Direct Routing LBR, enabled on users, sites and gateways, and Operator Connect for India LBR, which ties wireline numbers to network sites. Answers should say which one they mean.inferred

    Plan Location-Based Routing for Operator Connect for India · Introductory section and Note under Configure Location-Based Routing for fixed-line number calls; compare ms-learn-lbr-plan introduction · Checked 2026-09-25
57. 57
    The LBR network settings article says that for Direct Routing, any PSTN call to or from an LBR-enabled user whose external IP matches no trusted IP (an unknown location) is blocked, without mentioning the GatewayLbrEnabledUserOverride exception documented in the planning article and cmdlet reference.disputed

    Configure network settings - Location-Based Routing · Define trusted IP addresses (external subnets), 'For Direct Routing users' bullet · Checked 2026-09-25
58. 58
    Microsoft states that for users with India wireline numbers and LBR enabled, if Windows falls back to a manually configured default location, Teams strips the coordinates and disables PSTN calling until an automatically detected location is available.

    Plan for Operator Connect for India - Microsoft Teams · Wireless numbers > Location sharing for Teams clients, Important box 'Location detection requirements for Location-Based Routing (wireline numbers)' · Checked 2026-09-25
59. 59
    Read together, the Operator Connect for India planning page implies that a wireline LBR user on Windows may need both a network-site match and an automatically detected OS location to place PSTN calls.inferred

    Plan for Operator Connect for India - Microsoft Teams · Wireline numbers, Important box; Wireless numbers > Location sharing for Teams clients, Important box · Checked 2026-09-25
60. 60
    For Operator Connect for India, LBR is required for wireline numbers only; wireless numbers can roam within India using the client's operating system location or, on supported desk devices, the static emergency address instead of network sites.

    Plan for Operator Connect for India - Microsoft Teams · Choose a wireline or wireless number > Wireline numbers; Wireless numbers · Checked 2026-09-25

Documents

Cite this page

WarmTransfer. (2026, September 25). Teams location-based routing. WarmTransfer. https://warmtransfer.net/knowledge/teams-location-based-routing

@misc{warmtransfer-teams-location-based-routing,
  title  = {Teams location-based routing},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/teams-location-based-routing},
  note   = {Verified 2026-09-25}
}