As NimbusOne and the Nimbus Unify integration currently in active development, feature parity with Nimbus Extend is the goal. The table below shows which transfers are possible from a source (rows) to a destination (columns), for calls between Nimbus Unify, Nimbus Extend, Microsoft Teams and the phone network.
Legend: ✔️: Supported, available | 🔜: Planned, in development | 🟣Teams feature, not provided by Nimbus. |❌ Not possible | -: not applicable.
| Source / transfer type | NimbusOne user | Teams user | Unify service | Extend service | PSTN | |
|---|---|---|---|---|---|---|
| NimbusOne User (Unify-enabled user) | Add participant | ✔️ | ✔️ | - | - | ✔️ |
| Blind transfer | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | |
| Safe transfer | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | |
| Consultative transfer | ✔️ | ✔️ | 🔜 | 🔜 | ✔️ | |
|
Nimbus User (Extend-enabled user)2 |
Add participant | ❌ | 🟣 | - | - | 🟣 |
| Blind transfer | ❌ | 🟣 | 🔜 | 🟣 | 🟣 | |
| Safe transfer | ❌ | 🟣 | 🔜 | 🟣 | 🟣 | |
| Consultative transfer | ❌ | 🟣 | ❌3 | 🟣 | 🟣 | |
| Unify Service Workflow | Custom Parameter | ❌ | 🔜 | 🔜 | 🔜 | 🔜 |
| PSTN | - | - | - | - | 🔜 | |
| Service | - | - | ✔️ | ✔️ | - | |
| User | ❌ | ✔️ | - | - | - | |
| Extend Service Workflow | Custom Parameter | ❌ | 🟣 | 🔜 | 🟣 | 🟣 |
| External | - | - | ✔️1 | 🟣 | 🟣 | |
| Service | - | - | 🔜 | 🟣 | - | |
| User | ❌ | 🟣 | - | - | - | |
1 Supported with a workaround: use the PSTN number of the Unify service as External target and enable Leave Nimbus. This may result in double call charges.
2 Users which handle calls in Attendant Console or Nimbus Assistant.
3 Currently hard-limited by Microsoft-imposed limitations. Luware are continuing to monitor for further solutions and workarounds.