| Previous | Next |
| OLE_E_CANT_GETMONIKER | OLE_E_CANT_BINDTOSOURCE |
TAPI_E_CONFERENCEFULL
TAPI conference has reached participant capacity
TAPI_E_CONFERENCEFULL is HRESULT 2147745801 (0x80040009) from TAPI 3.0. The documented description is “The conference is full.” The result belongs to adding or joining calls through conference-control operations. This HRESULT is most useful when tied to the method and lifecycle phase where the current conference cannot accept another participant under provider or device limits.
This result means that the current conference cannot accept another participant under provider or device limits. Preserve the original HRESULT and the state that made this condition true; the severity bit alone does not determine how the caller should handle it.
Where the result appears
- This result can surface in a TAPI 3 address, call-control, terminal, stream, conference, dialing, or completion-management code.
- Map the failure to one concrete operation among ITTAPI, ITAddress, ITBasicCallControl, ITCallInfo, terminal and stream interfaces, provider events, and asynchronous request state.
An incident record must distinguish caller, runtime, provider, and backing resource while testing whether the current conference cannot accept another participant under provider or device limits.
Typical causes and interpretation
The immediate contract boundary is specific: the current conference cannot accept another participant under provider or device limits. Common cause branches include the following:
- The bridge maximum is reached.
- Reserved resources reduce available participant slots.
- A disconnected participant has not yet been removed.
Confirm the cause branch that explains why the current conference cannot accept another participant under provider or device limits by using call arguments, object state, metadata, device information, or provider traces.
Correct handling and recovery
The primary recovery is to wait for conference-state cleanup or create another conference according to provider capability. The failure report should capture the relevant state during adding or joining calls through conference-control operations so it is clear why the current conference cannot accept another participant under provider or device limits.
The owner of it must define idempotency, cancellation, attempt limits, and reconciliation for the failed adding or joining calls through conference-control operations.
Practical scenario
A hardware bridge supports six parties and rejects the seventh consultation call; the application offers a second bridge instead.
Difference from related HRESULTs
TAPI_E_CALLUNAVAIL concerns call appearances; it specifically concerns membership in an existing conference
Developer and administrator guidance
Use a controllable service provider or simulator to cover state races, capability differences, device removal, cancellation, and provider restart.
Broad permission or compatibility changes are inappropriate unless evidence for the current conference cannot accept another participant under provider or device limits points to that layer.
References
Looking for a different code? Search another status or error code.