I’ve repeatedly been unable to connect to my dot using the phone/call button on October 1–2, 2026. I’ve tried on iPhone, the Mac desktop app and the web, and the call fails across all three.
Steps: Open my dot conversation, press the phone/call button and wait for it to connect.
Expected: A voice call connects.
Actual: The call fails. The displayed error is:
通話失敗
未能建立通話連線。請檢查網絡連線及麥克風存取權限,然後再試一次。
In English: “Call failed. Unable to establish a call connection. Please check your network connection and microphone access permissions, then try again.” No error code is shown.
I haven’t confirmed the cause. I’ve also contacted OpenAI Support and am waiting for follow-up.
Has anyone else had this problem with dot calls, and has any workaround helped? Thank you.
I’m experiencing a similar issue on my iPhone 17 Pro Max: dot calls won’t connect. Calls work on macOS. I haven’t tested the web version. Is there a known iOS issue or workaround?
Same here. And it’s not just the Mac version; the Windows app, all web versions, and the Android mobile app all have the same issue. A few days ago, it just took a long time to load, but today it’s failing outright—and there hasn’t been any explanation from the official side.
Issue Summary:
Every time I attempt to initiate a voice call with a ChatGPT Dot agent on the Android app, the interface immediately throws a “Call Failed” error screen. The call drops instantly before any connection can be established.
Key Technical Details:
Platform: Android (Latest App Build)
What Works: Standard ChatGPT Live Voice works flawlessly. Sending text messages to the Dot works perfectly and it responds normally.
What Fails: Launching a direct voice call to the Dot agent.
Troubleshooting Attempted: I have already forced closed the app, cleared the local app data/cache completely, and toggled the device microphone permissions off and back on.
This appears to be an isolated server-side audio routing or WebRTC socket crash specifically affecting the Dot framework nodes. Please investigate the backend agent communication lines.
Drafted with help from my dot, based on my own experience:
I had been unable to connect to my dot on Windows desktop and web. Earlier attempts included restarting, signing out, and trying other browsers. My logs included “Voice transport hangup was not confirmed.”
Today I tried this sequence:
Opened a new regular chat in my local ChatGPT/Codex client.
Started a regular Voice conversation and then ended it normally.
Returned to my dot conversation and pressed the call button again.
This time the dot call connected, and we could talk.
This is one successful attempt, not a confirmed fix. I don’t know whether the sequence helped or whether the service recovered around the same time. Sharing it in case others can test whether they see the same result.
Thanks for the reports, @wainok0608 + everyone! We rolled out fixes for Dot call connection issues on October 8. Can you try another call and let us know if it still won’t connect?
My dot calls still time out on October 10, after the October 8 connection fixes. Regular ChatGPT Voice and dot text work. Please investigate the continuing failure, referencing GitHub issue #50870 and OpenAI Support’s October 9 update confirming that fixes had been rolled out.
Still failing on October 11 at 04:32 UTC. On iPhone, calls stay on ‘Calling…’ and never connect. This happens on both Wi-Fi and 4G, including after rebooting the dot. Please advise the next diagnostic step.
Hi @kenrend, we traced the iPhone attempt around your reported time. Microphone setup passed, but the app ended the attempt while it was still waiting for the call to start.
Are Dot calls still getting stuck on “Calling”? If so, do they end on their own, or only when you stop them?
I’m unable to connect voice calls to my dot, in the ChatGPT iPhone app (AMC / web). Calls repeatedly stay on “Calling…” without connecting or showing an error.
I tried starting and ending a normal ChatGPT Voice conversation, then calling my dot again, but it didn’t resolve the issue. My latest unsuccessful test was around 9:19am Singapore time (UTC+8) on 14 October 2026.