Back to all discussions

  •   2 months ago

region/language support

Hi CALL-E team,

I am building a hackathon project using the CALL-E MCP / CLI flow.

I found a related developer-runtime limitation, but it is not exactly the same as credential_grant_unavailable.

In my case:

- CALL-E Chat may have broader calling behavior than the developer runtime.
- MCP plan_call was invoked successfully through the calle CLI.
- No run_call was executed.
- The controlled endpoint was an authorized test phone number in E.164 format.
- plan_call returned ready_to_run=false.
- No confirm_token / runtime authorizer was returned.
- The provider message indicated that the endpoint was recognized as Taiwan + English, and that this region/language combination is not currently supported for this channel.

This means the zero-trust flow correctly failed closed before run_call, but I cannot proceed to a controlled endpoint proof call.

Questions:

1. Which country / language combinations are currently supported for MCP or Developer API controlled endpoint testing during the hackathon?
2. Does CALL-E Chat currently have different calling credentials or regional coverage from MCP / Developer API?
3. Is there an official recommended test endpoint region for hackathon participants?
4. If a region/language combination is unsupported, should plan_call return a documented unsupported_region / unsupported_language code?

Related issue: https://github.com/CALLE-AI/awesome-phone-call-agents/issues/106

I can share redacted artifacts or run metadata privately if useful.

  • 1 comment

  •   •   2 months ago

    Thanks for the report. The observed MCP/CLI behavior is expected.

    CALL-E Chat currently has a broader capability envelope than the public Developer API and MCP/CLI integrations. These channels use different execution paths and runtime configuration, so availability is not guaranteed to be identical across them.

    Taiwan (TW, +886) is not currently included in the published supported-regions-and-languages list for the documented integrations. Therefore, an MCP plan targeting Taiwan should remain non-executable: `plan_call` returns `ready_to_run=false`, no confirmation token is issued, and `run_call` is not attempted.

    Region/language availability is configuration-driven, not hard-coded as a permanent matrix. The published supported list is the current integration contract and will change as supported voice and outbound-line configurations are added: [Supported Regions and Languages](https://github.com/CALLE-AI/call-e-integrations#supported-regions-and-languages)

    We have opened a [feature request for Taiwan line support](https://discord.com/channels/1493880186826133504/1532615923863654410/threads/1536950576859062332) and are working on adding it. Until that support is enabled and reflected in the published list, `TW` should be treated as unsupported for MCP/CLI testing.

    This is separate from `credential_grant_unavailable`: your call was correctly rejected before execution, rather than accepted and then failing during credential handoff.

Log in or sign up for Devpost to join the conversation.