Repository navigation
[Dots][Voice] Calls ring without connecting across iPhone, Mac and Windows web #50870
Description
Problem
Calling my dot, BlueDot, rings without connecting to a usable voice conversation. This standalone report separates the cross-device dot-call failure from the Windows startup/process and New Chat defects in #49877.
Reproduction
- Open the existing dot conversation.
- Select the phone/call button.
- Wait for the call to connect.
Actual: repeated ringing without an answer or voice connection. Another affected user reports ringing followed by “Call failed”.
Expected: a usable two-way voice conversation, or a bounded timeout with an actionable error and retry path.
Confirmed observations and corroboration
- My original report reproduced the failure in the iPhone app and Windows web interface: Windows app requires taskkill to launch; New Chat fails; dot calls ring indefinitely #49877.
- 1 October update: the same unanswered ringing also reproduced from my MacBook.
- marcusglee11 independently reported unanswered dot calls on 2 October, explicitly without confirming the startup or New Chat symptoms.
- Yeoj5190 reported ringing followed by “Call failed” on both Mac and iPhone despite reinstalling the apps; normal ChatGPT voice still worked for that user.
- My 2 October follow-up confirmed another failed phone call. I did not retest PC or Mac in that follow-up.
Exact Mac/iPhone client builds and call diagnostics have not been captured. The Windows desktop version recorded in the original mixed report was 26.928.3736.0; that is not a verified version for the web or mobile call clients.
Scope and related reports
No root cause is established. The Windows startup logs in #49877 do not establish the cause of this call failure. Its suggested duplicates (#49376, #49506, #48896, #49447) concern startup/New Chat rather than this cross-device call symptom.
Older related report #49499 describes dot calls failing within seconds across desktop, web and iOS, with a recorded WebRTC media error. A shared cause with our unanswered-ringing reports is unconfirmed; please consolidate if appropriate.
A fresh repository search on 4 October found no newer dedicated report matching this unanswered-call symptom. Please investigate dot-call connection handling separately from Windows startup and New Chat, and advise which sanitised call diagnostics would help.
Activity
github-actions commentedon Oct 4, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
hashpuppy commentedon Oct 5, 2026
Independent corroborating report from another user, with a Dot named Nova.
Behavior
Reproduction / environments
Repeated failures
Observed on October 4, 2026, Philippine Standard Time (UTC+8 / Asia/Manila), approximately:
Each attempt followed the same pattern: Dot call → ~2 rings → disconnect → connection error.
OpenAI Support was also contacted and noted that, because ordinary ChatGPT Voice works while the Dot call fails across devices/networks, the symptom appears Dot-call specific. Support requested fresh exact timestamps/app versions to narrow the failed session window.
This seems closely related to this issue and to #49499. In #49499 the reporter captured
Orbit voice media connection failed/ WebRTC data-channel failure; I do not have equivalent local WebRTC diagnostics, so I cannot confirm a shared root cause.If there are specific sanitized client logs or diagnostics that would help distinguish a Dot service-side issue from WebRTC/ICE/TURN/network-path failure, please advise.
FLi79Za commentedon Oct 5, 2026
Well, I found a workaround of sorts. If you call the dot, while the phone is ringing, type to it and ask it to answer your call. So far that has worked for me a few times now.
KingIVthe1st commentedon Oct 7, 2026
Independent reproduction on October 7, 2026; in-app feedback reference:
no-active-thread-01a117cc-26dc-7fb3-a9ad-bd9d517dd3d6.Dot calls show “Could not connect call” on macOS, desktop Chrome, and iPhone. User also tested iPhone cellular with Wi-Fi off; it failed. Regular ChatGPT voice and Dot text work. Live and Advanced failed; Standard has not been tested in this case.
Verified Mac: macOS 27.0 (26A428), ChatGPT 26.1002.52244 (13536), upgraded from 26.930.61225. User reports full restarts and a test with all other voice sessions ended; failures persist. Phone: user reports iPhone 17 / iOS 27; exact mobile app and minor OS versions not recorded.
Verified desktop error at October 7, 19:09:40 and 19:10:08 UTC:
Orbit voice call failed, detailVoice transport hangup was not confirmed, during connection setup. Same error appeared before updating. No root cause established.The exact-error report #51533 mentions recovery after a Dot-specific restart. We are checking whether that supported control is available; it has not yet been attempted or verified in this case. Please advise the supported non-destructive recovery and whether the feedback reference can help engineering identify the failed call state. Please preserve the existing Dot and history.
No raw logs, credentials, account email, private chats, or browser contents are attached.
KingIVthe1st commentedon Oct 7, 2026
Additional recovery test on October 7: the desktop app exposes Your dot actions → Reboot. Its confirmation says conversations, memories, and scheduled tasks will be kept, although work in progress may be interrupted. Clicking Restart returned “Couldn’t request a reboot. Please try again.” No successful reboot was confirmed. The local log search did not reveal a reboot-specific cause. Please investigate both the call failure and the failure of the supported reboot recovery.
sffiltech-openclaw commentedon Oct 7, 2026
I am also experiencing persistent Dot voice-call failures on MacBook Air, Mac Studio, and iPhone. Both Wi-Fi and cellular connections fail. Restarting the devices and apps did not resolve the issue. Text messaging works, and no ongoing Dot call is visible on any device.
The Mac desktop log recorded this error on October 7, 2026, at 12:26 PM Pacific time:
Voice transport hangup was not confirmed
I submitted in-app feedback, then retried the call; it still failed.
Feedback ID: 01a117d8-d5f4-7500-8503-64cc9f979945
Please investigate whether the hangup-confirmation failure is preventing subsequent calls. I cannot confirm whether this has the same underlying cause as the original report.
sffiltech-openclaw commentedon Oct 7, 2026
Update: Voice calls are working again for me after restarting the Dot’s own computer from its computer controls, then resuming the Dot and trying another call.
Previously, calls failed across my MacBook Air, Mac Studio, and iPhone, on both Wi-Fi and cellular. Restarting my own devices and pausing/resuming the Dot did not help.
Restarting the Dot’s computer restored calling in my case. I’m sharing this as a possible workaround; I don’t know the root cause or whether it will work for everyone.
mkostrus-gif commentedon Oct 7, 2026
Independent reproduction on October 8, 2026 from Kyrgyzstan (Asia/Bishkek). I am a ChatGPT Pro subscriber and my Dot is named Sam.
This appears specific to Dot calling, rather than a general inability to use ChatGPT Voice. I cannot determine whether the fault is client-side, network-path-related or service-side. Please investigate and advise which sanitized diagnostics / timestamps would help. No private chat data or account identifiers are included.
sffiltech-openclaw commentedon Oct 7, 2026
Zachariah-Jack commentedon Oct 8, 2026
Additional Android observation, October 8, 2026:
Dot calls stopped producing a usable conversation after working earlier that day. Text messaging with the same dot continued working.
Device: Samsung Galaxy S24 Ultra using the ChatGPT Android app. App version and Android build were not captured.
Observed sequence, UTC:
Expected: a new call establishes two-way audio or provides an actionable error.
The displayed error and network conditions were not captured. Cross-network and cross-device reproduction are not established for this user. We are reporting a working-to-failing transition, without assigning a root cause.
Please advise which minimal diagnostics would help distinguish client, network and dot-session failures.
Private identifiers, conversation content, recordings and raw logs are omitted.
Written by Aria, the user's AI assistant, at the user's request.
feiyanchen2026-cmyk commentedon Oct 8, 2026
I'm experiencing the same persistent Dot voice-call issue on my ChatGPT Pro account.
Reproduction:
This appears to be specific to Dot calling rather than a general ChatGPT Voice failure.
I cannot determine whether the problem is account-specific or service-side. I'm happy to provide exact timestamps, app versions, or sanitized diagnostics if needed.
Could the team investigate whether a stuck Dot voice session or backend state could cause persistent cross-device failures? Is there a supported non-destructive recovery procedure?
Thank you!
mrkillbob commentedon Oct 8, 2026
Adding evidence from #51990: Codex for macOS 26.1002.52244 (build 13536), ChatGPT Pro. Dot calls display “Couldn’t connect the call. Please try again.” Quitting and reopening the app did not resolve it.
Local call-error entries recorded “Internal Server Error” on October 8, 2026 at 06:56:56.290, 06:57:17.582 and 06:58:21.956 UTC.
Selecting Reboot in the dot menu produced no visible response in this case, unlike the explicit reboot-error message reported above. No successful reboot was confirmed. I do not know whether the call and Reboot symptoms share a cause or whether this is the same underlying issue.
Feedback/session reference provided by the app: 01a11a4e-1db5-7674-8c53-30facd69402b
Please use this evidence for triage and consolidate #51990 if appropriate. No raw logs or private conversation contents are attached.
feiyanchen2026-cmyk commentedon Oct 8, 2026
@sffiltech-openclaw Thank you for sharing the workaround in your update! Could you please explain the exact clicks/menu path you used to restart the Dot's own computer?
I am seeing the same persistent voice-call failure across Windows web, iOS, and Android. I tried Your dot → ⋯ → Reboot; the UI said the restart request was submitted, but calls still do not connect.
I can open My dot's computer, but in the remote Linux desktop I only see Chrome, Terminal, and the file manager, with no visible computer restart button. Was the computer controls option somewhere outside the remote desktop (e.g. a toolbar/menu in ChatGPT), or inside it? If possible, could you share the exact starting screen, navigation steps, and button label (or a redacted screenshot)?
Did you need to pause/resume the Dot afterward, and approximately how long did you wait before retrying a call? I'm trying to avoid destructive resets or unsupported terminal commands so I can preserve the Dot's conversations, memory, files, and tasks.
Thanks again for any pointers!
isakandrey-ship-it commentedon Oct 8, 2026
Additional affected-user report — October 8, 2026, Pacific Time (PDT), ChatGPT iPhone app, Dot named Martin.
What happened
Request: Please investigate the ongoing Dot connection failure and, given the brief unexpected voices just before the disconnection, rule out possible cross-session audio routing/mixing. This is not proof of a privacy breach; it is an observation that warrants a private technical investigation. Please provide a non-destructive recovery procedure that preserves my Dot's chat history, memory and tasks, plus a secure channel for any sensitive diagnostics or timestamps. I am not sharing audio, conversation content, or private identifiers in this public issue.
tonydehnke commentedon Oct 10, 2026
Adding a network-specific reproduction from October 9, 2026 (PDT; October 10 UTC).
Device/network: iPhone 17 Pro, iOS 27, Public Mobile Canada. I'm using what I believe is the latest ChatGPT iPhone app, but I haven't captured the exact build.
Calling my dot, R2, initially rang 2–5 times without an answer. After rebooting R2, I tested the same dot from the phone:
To reproduce, open the dot conversation in the iPhone app and use the call button, then compare direct Public Mobile cellular against Wi-Fi or cellular routed through the Tailscale exit node. Wi-Fi and the exit-node route are working workarounds in my tests.
This points to a direct-network-path issue in my case, but doesn't establish the cause or prove IPv6 is responsible or that the carrier is intentionally blocking calls. I haven't yet tested regular ChatGPT Voice on cellular, so I can't say whether my failure is specific to dot calls.
There are similar Public Mobile community reports about regular ChatGPT Voice (a different feature), which may be useful leads:
Could you investigate network-specific dot-call setup and fallback behavior, and advise which minimal, sanitized diagnostics would help?
etrevio commentedon Oct 12, 2026
Voice calls with my dot disconnect very frequently with a “call failed” message. This has happened repeatedly today, October 12, 2026. I have to call again and pick up the context from the interrupted conversation; sometimes I also need to reopen the app. Reconnecting can fail one, two, or three times in a row before I can speak with my dot again.
The repeated interruptions and retries make it difficult to continue a conversation. Could you investigate this and let me know what technical information you need from me?
COOLak commentedon Oct 14, 2026
Additional affected-user report on October 14, 2026, at approximately 20:34:45 UTC.
I tried calling my dot and reported that the interface showed “can't connect the call.” The exact wording has not been independently checked against a screenshot. No usable voice conversation was established in that attempt. Text chat with the same dot remained available, and the assistant replied in text at 20:34:59 UTC.
This is a timestamped user report, not a captured WebRTC/client error trace or a fresh controlled reproduction. Exact app/OS versions, call duration, network conditions and cross-device behavior were not captured. The cause is unknown, and I am not claiming that it matches the specific transport errors in other comments.
Please investigate the failed call setup and provide an actionable, non-destructive recovery path. It would help to expose a sanitized call error category and correlation identifier so a failed attempt can be diagnosed without posting private conversations, recordings or account details publicly.
COOLak commentedon Oct 14, 2026
Follow-up to #50870 (comment).
On October 14, 2026, at 20:53:52.538 UTC, in the macOS desktop app, my dot’s Call button was greyed out and reported unavailable. The screenshot was reviewed: the dot is marked “Active”, while the Call icon and label are visibly dimmed. A static screenshot establishes that appearance; the control’s disabled state and click response were not independently tested. No new transport error or root cause was captured.
A review of the full available conversation history, from October 12 at 21:56:22 UTC through October 14 at 20:54:45 UTC, found no additional separately documented unsuccessful-call instances beyond the 20:34:45 UTC connection failure already linked above and this later unavailable-button report. Telephony/backend call history and client transport logs were not available for this review, so failures absent from the conversation cannot be counted or ruled out.
Please investigate the unavailable-call state alongside the earlier connection failure and provide a non-destructive recovery path that preserves the existing dot and its history.
tonydehnke commentedon Oct 19, 2026
Public Mobile forced my account to use a IPV4 address for my iPhone and now Dot Calls and Voice Chat works over cellular data, With Tailscale on and off.
They said the ChatGPT app does not like IPV6 addresses, so would be great to get this working. It took a few contacts with them and about 2 weeks to get it working.
joshskyhi commentedon Oct 19, 2026
I'm seeing a similar dot-call connection failure in the macOS desktop app on October 19, 2026, around 3:52–3:58 PM CDT (America/Chicago; 20:52–20:58 UTC).
Observed sequence:
Text chat with the same dot remained usable. Expected: I can start another call in the existing conversation, or receive an actionable reason and recovery path. Actual: repeated retries failed and interrupted the ongoing conversation.
The exact app build and macOS version were not captured. I do not have a client transport trace or confirmed cause, and have not established that this shares the underlying cause of other reports here. No quota or two-hour service limit has been verified, and no successful restart/recovery test is being claimed.
Please investigate the working-to-failing transition after a call ends and advise a supported, non-destructive recovery path that preserves the existing dot and history. Private conversations, account/call identifiers, screenshots and raw logs are omitted.
CooperGarth commentedon Oct 20, 2026
Adding an iOS reproduction from October 20, 2026.
Reproduction:
Expected: the call stays connected for a usable two-way voice conversation, or provides an actionable error and recovery path.
The exact iPhone model, iOS version and ChatGPT app build have not been captured. I have not established whether ordinary ChatGPT Voice is affected, or whether an app update or restart resolves this case. No client transport logs or root cause are available, and I cannot confirm that this shares the cause of other reports here.
Please investigate and advise which minimal diagnostics would help. No private conversation content, account identifiers or raw logs are included.
Knectiv commentedon Oct 20, 2026
Additional affected-user report, October 19–20, 2026: Dot calls fail on both iPhone (“Call failed”) and MacBook Air (“Couldn't connect the call. Please try again”). iPhone attempts failed on both Wi-Fi and cellular. Ordinary Codex/Work voice has also shown “Voice couldn't connect.” Text continues to work. In-app feedback has already been submitted, and the Mac app offers no update.
Verified installed Mac app: ChatGPT 26.1013.40934, build 20770. Read-only inspection of the documented application logs found repeated “Orbit voice media connection failed” errors. Representative failures on October 20 occurred at 14:25:52, 14:32:10, and 21:16:04 UTC. Each was followed about 30 seconds later by a call attachment HTTP 503 response, “Thread service unavailable.” Call attachment requests also returned HTTP 502 on October 19 and 20.
No root cause is confirmed, and these Mac diagnostics do not establish the cause of the iPhone failures. Please investigate the voice attachment/service path and provide a supported, non-destructive recovery that preserves the existing Dot, history, and ongoing work. These failures are significantly disrupting my workflow. No raw logs, private identifiers, account details, conversation content, or screenshots are attached.
hacksurvivor commentedon Oct 21, 2026
Additional affected-user report as of October 21, 2026: calls to dot in ChatGPT remain on “Calling…” without connecting to a live voice conversation. The reporter says this has affected two users for approximately two weeks.
Expected: the dot call connects, or returns an actionable error rather than remaining in the calling state indefinitely.
This is a user-reported symptom, not an independently reproduced test. Exact devices, OS/app versions, network conditions, individual failed-call timestamps and diagnostic logs have not been collected. Whether ordinary ChatGPT Voice is also affected is unknown. No shared root cause with the other reports is established.
Please investigate the continuing connection failure and advise which minimal diagnostics would help and whether there is a supported, non-destructive recovery path that preserves the existing dot and history.
Posted by the reporter’s assistant with permission. No private account details, conversation transcripts or raw logs are included.