☝Nimbus and related addons can only perform PSTN transfers according to Microsoft's licensing and constraints.
✅ As Administrator you need to acquire Microsoft Teams phone licenses
🤔Which PSTN licenses do I need to acquire?
Service Licensing
|
Number Type using any of the Microsoft | PSTN Connectivity options ▼ |
License to apply for Nimbus Services |
| Direct Routing |
"Teams Phone Resource Account". 🔎 See: |
| Calling Plan |
"Teams Phone Resource Account" license, plus
1🔎 Only required for Outbound Call functionality. See: Microsoft Learn | Microsoft Teams Calling Plans. |
|
Operator Connect |
"Teams Phone Resource Account" 🔎 See: Microsoft Learn | Voice applications prerequisites and licensing |
User Licensing
| Target User | License to apply to Nimbus Users & Call Targets |
|
All Users, including … + Agents that handle Nimbus calls + Attendant Console transfer and consultation targets. |
"Teams Phone Standard", each account having: |
☝Please note that Luware staff cannot give recommendations on which license plan is best suited for your needs. Depending on your scenario, additional Teams App licenses may be required. Exact details are to be discussed with your Microsoft contacts.
🤔How does PSTN licensing affect Service and call transfers?
Assuming that the initially called Service has (no) PSTN license assigned - the following scenarios may unfold:
Scenario A - Service A has a PSTN license. Transfers to other Services occur.
⮑ The PSTN license carries over throughout transfers to other Nimbus Services B and C.
⮑ As the license carries over, a PSTN transfer to an external target is possible from either Service.
Scenario B - Service B has no PSTN license. A Transfer to Service C occurs which has a PSTN license.
⮑ The customer skips over Service A and manages to reach Service B instead.
⮑ The PSTN license is missing on Service B, so nothing is carried over to Service C.
⮑ Even if Service C has its own PSTN license, a PSTN transfer to an external target is not possible.
🌟Learnings:
- Nimbus will use the PSTN license – and create a (transfer) Session – from the FIRST Service responding to a call.
- Regardless of how many internal Service transfers are performed thereafter, the FIRST Service PSTN license remains in effect.
- If a PSTN license is missing, the transfer task will fail and be treated accordingly by the System.1
- Even if a Service being transferred towards has a PSTN license, it cannot be added in post, as the Call Session is already ongoing from the first-responding Service.
✅ For your licensing needs this means: If you require PSTN transfer functionality, you'll need to ensure that this Service is handling all your incoming calls.
- For ONE first-level / Front Desk Service, you'll need a PSTN license for this particular Service.
- For MULTIPLE first-level Services scenario, you'll need PSTN licenses for all first-level Services.
1🔎 Assumption: Workflow takes the normal "Exit" Announcement route and Service Session will conclude with a "Transfer failed" outcome. For more details on analyzing your Reporting results, refer to Nimbus Reporting and Static Dimensions > "Service Session Outcomes"
🤔How does PSTN licensing affect Transfer on User Exit?
When DTMF-Supported Transfer is enabled on a Transfer on User Exit configuration, Nimbus places a new outbound PSTN call to the target service's configured E.164 number at transfer time. This is different from the "license carries over" behavior described above — it is a fresh outbound call, not a continuation of the existing call session.
The PSTN license must be assigned to the originating service — the service where Transfer on User Exit is configured.
☝ Each Transfer on User Exit via PSTN generates a new outbound call and incurs additional costs. Costs are billed to the originating service, not to the customer.
In the current release, this also generates a second Unified Session for the PSTN leg, which is not yet linked to the original session in reporting. 🔎 See Transfer on User Exit > Known Limitations.
☝Note that handling and tracking of running cost for PSTN licenses is outside of the Luware support scope. If you however require assistance in extending and/or configuring your Nimbus Services for PSTN, our support will gladly assist you:
| Luware Website | https://luware.com/support/ |
|---|---|
| Luware Helpdesk | https://helpdesk.luware.cloud |
| Cloud Service Status | https://status.luware.com/ |