MDD Sim Gateway v1.4.1
修复
服务码的提示不再抢在答案前面
拨运营商服务码时，判决（运营商是否受理）和回复文本是分头到达的，判决通常先到一步。界面拿到先到的那个就下结论，于是会在文本到达前一秒宣称「没有可用响应」或「此类代码不返回文本」，然后当着你的面改口。
一句稍等，好过一个会变的答案。现在它等到真有东西可报再说，并且区分两种情况：运营商已接受——回复可能随后就到，继续等；运营商拒绝或无法处理——不会再有内容，立即出结论。
结果不再来回跳变
每个事件都会刷新一次通话列表，而这些并发请求的响应可能乱序返回——一个较早发出、较晚返回的响应会把旧列表盖回去，结果就在「等待中」和答案之间反复横跳。
现在刷新带序号，只有最新的那次允许写入；并且运营商给出的判决一旦显示就不再收回。
其他
- 返回按钮的 30 秒倒计时不再因为回复晚到而被重置
- 服务码不再显示静音、拨号键盘、录音——它们都作用于音频，而服务码是纯信令，没有音频
- 快速连拨两个代码时，先返回的结果不会再被记到另一通电话头上
本版只改动 WebUI 与控制面的提示逻辑，引擎镜像与 v1.4.0 相同，无需重建。
Fixed
A service code's status no longer answers before the answer does
The verdict (whether the carrier took the request) and the reply text arrive
separately, and the verdict usually wins the race. The screen concluded from whichever came
first, so it would announce "no usable response" or "this kind of code returns no text" a
second before the text appeared — correcting itself in front of you.
A brief wait beats an answer that changes. It now holds until there is something real to
report, and it tells the two cases apart: accepted — a reply may still follow, keep
waiting; refused or could not be handled — nothing more is coming, conclude now.
The outcome no longer flips back and forth
Every event refreshed the call list, and those concurrent requests could return out of
order — an older response landing last put a stale list back on screen, so the result
alternated between "waiting" and the answer.
Refreshes now carry a sequence number and only the newest may write; and once a carrier's
verdict has been shown, it is never withdrawn.
Also
- The Back button's 30-second countdown no longer restarts when the reply lands late
- Mute, keypad and record are hidden for service codes — they act on audio, and a service
code is pure signalling with none - Dialling two codes in quick succession no longer files the first result under the wrong call
This release changes only the WebUI and control plane. The engine image is identical to
v1.4.0 — no rebuild needed.