Luban UK OpenAI phone test: 10 attempts, no SMS (2026-05-11)

Context

Account under test:

2925 account: chickliu2031@2925.com
OpenAI alias: chickliu2031som6d8@2925.com
Email verification: passed
OpenAI page before test: https://auth.openai.com/add-phone
SMS provider: Luban SMS
Country/service: United Kingdom/England, OpenAI
Luban service_id: 537935
Cost observed: 0.05

Secrets, full phone numbers, email/SMS codes, API keys, and proxy strings are omitted.

Runner policy

Command:

PYTHONUNBUFFERED=1 ATTEMPTS=10 PHONE_POLL_SECONDS=190 \
  /Users/chick/homebrew/opt/python@3.11/bin/python3.11 \
  /tmp/luban_uk_2031_10_attempts.py \
  | tee /tmp/luban_uk_2031_10_attempts.log

Important policy from BOSS:

Wait at least 3 minutes per Luban order before releasing it.

The runner waited about 190s per order and only called setStatus?...&status=reject after the 3-minute window.

Result summary

{
  "attempts": 10,
  "bought": 10,
  "rejected_by_openai": 0,
  "sms_timeout": 10,
  "sms_received": 0,
  "success": false
}

Request ids tested:

All 10 orders were released successfully via Luban setStatus:

activation_reject ok=true msg=success

Details

Attempts 1-9:

OpenAI country gate: GB / 英国 OK
Luban number bought OK
OpenAI phone submit entered https://auth.openai.com/phone-verification
OpenAI did not immediately reject the number
Luban getSms kept returning msg=wait for ~190s
No SMS code arrived
Order released successfully

Attempt 10 nuance:

Country gate OK and Luban number bought OK.
After submit, page remained https://auth.openai.com/add-phone instead of phone-verification.
The runner still polled Luban for ~190s and got only msg=wait, then released the order successfully.
Treat this as submit/page-state failure + no SMS, not as confirmed OpenAI SMS-page entry.

Operational conclusion

For this specific account/session and Luban service 537935 (United Kingdom/England OpenAI):

Luban UK numbers were accepted by OpenAI for attempts 1-9, but no SMS arrived after >3 minutes each.
Continuing the same Luban UK service is low-yield unless BOSS wants more spend/testing.

Recommended next options:

Try a different Luban country/provider/service_id if available.
Return to 5sim/free-country strategy, since previous successful OpenAI phone verification happened with a non-UK 5sim activation.
If staying on Luban, query multiple OpenAI/ChatGPT service entries and avoid repeatedly using only service_id=537935.

Script improvement note

The runner should be patched before reuse:

Only poll SMS if phone submit lands on phone-verification / SMS verification page.
If submit remains on add-phone without explicit reject, classify as submit_no_sms_page, release after the required minimum hold time, and continue.
Keep the 3-minute minimum release window for Luban provider orders.

3.0 KiB Raw Blame History