☝Out of box, transfers towards the UPNs of Teams-native Auto Attendants (AA) or Call Queues (CQ) Resource Accounts will fail. Preconditions and Workarounds apply.
| Nimbus transfer to… | ... using … | Result |
|---|---|---|
| Auto Attendant | Attendant Console | Only works using Blind Transfer or with workaround → 🛠 see below |
| Teams Client | Works for all options, but as a workaround with limitations → 🔀 see below. | |
| Workflow | Works as detailed by the table below. | |
| Call Queue | Attendant Console | Only works using Blind Transfer or with workaround → 🛠 see below |
| Teams Client | Works for all options, but as a workaround with limitations → 🔀 see below. | |
| Workflow | Works as detailed by the table below. |
Connectivity plan dependencies
Based on the PSTN connectivity option used, transfers towards the Resource Accounts' assigned phone numbers will work as summarized in the table below.
| Transfer Type | Direct Routing | Calling Plan | Operator Connect |
|---|---|---|---|
| Attendant - Safe Transfer | 🛠 | ❌ | ❌ |
| Attendant - Blind Transfer | ✅ | ✅ | ✅ |
|
Attendant - Consultation Call then transfer (Attended Transfer) |
🛠 | 🔀 | 🔀 |
Workflow Conversation Handling Activities > Transfer > “Leave Nimbus” disabled |
🛠 | ❌ | ❌ |
Workflow Conversation Handling Activities > Transfer > “Leave Nimbus” enabled |
✅ | ✅ | ✅ |
|
🛠 Only works with reverse number lookup workaround, described below. 🛠 Workaround: Reverse Number Lookup (RNL)For any of the above mentioned transfer types to work together with the chosen connectivity plan, Reverse Number Lookup (RNL) has to be disabled in the Resource Account's phone number assignment. RNL can be disabled by executing the following PowerShell command: 💡Effects: ⮑ After disabling RNL for a Phone Number Assignment, Teams will automatically forward the call to the Direct Routing SBC, which then needs to redirect it toward the Resource Account of the Call Queue or Auto Attendant. 🔀Workaround: Consultation Call then transfer🔎Analysis: Transfer scenarios for existing call conferences is limited – specifically for voice applications such as Call Queues, Auto Attendants and Nimbus. These limitations are imposed by Microsoft Teams and cannot be circumvented by Nimbus.
🔀Workaround: A consultation transfer can be completed using the teams call window instead of Nimbus, an example of the call flow is provided below.
☝Limitations Note: This workaround involves circumvention of the Nimbus UI in favor of MS Teams functionality, which is generally not recommended when you want to have detailed Nimbus Reporting with accurate session outcomes 💡Effects: | |||