This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(252.8, 47%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKJ%3C/text%3E%3C/svg%3E)
Deploying Teams Voice as a PBX replacement for a small (17seat) church. All users have Voice licenses and Microsoft Calling Plan (Trial) add-on. Using default policies and setting. Global Call Policy allows forwarding and simultaneous calls to external numbers. Inbound and outbound calls work fine. Voicemail works fine. Users are unable to complete forwarding to an external number. Setting works fine, using +1xxxxxxxxxx syntax for number. Inbound callers get a non-complete recording. Online help suggests a voice routing policy is required for Direct Routing, but not needed for Calling Plans.
Suggestions?
What error are you receiving when you try to external forward? Do you have a screenshot?
Ok, it may be related to the number being forwarded to. Used a commercial 800 number (United Airlines) and forwarding works fine. Used a T-Mobile cell number and their spam filters intercept the call. Direct dial to that same T-Mobile number goes through though.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(246.4, 22%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKY%3C/text%3E%3C/svg%3E)
Glad to hear the issue has been resolved!
Wondering if it might possible be related to the trail calling plan we are using now. Will be converting to a paid plan in the near future and see if that helps.