IS-95 Web Browsing
1xBTS includes a built-in UP.Link gateway so an old Openwave UP.Browser handset — the WAP 1.x browser baked into many early-2000s CDMA phones — can browse the modern web. The gateway terminates the handset’s HDTP session, fetches the requested page, and converts it to the handset’s markup (HDML) before sending it back. It runs inside the fou-nat packet-data container and is on by default, so once a handset has a working data session its browser can reach it.
Status: Experimental. Aimed at period Openwave UP.Browser handsets. Web pages are transcoded to HDML on a best-effort basis — expect text, headings, and links, not full page fidelity. Encrypted (cipher-2) browser sessions are supported. See Known issues.
How the handset reaches the gateway
A UP.Browser doesn’t resolve a hostname — it dials a fixed UP.Link proxy IP over UDP, provisioned in the phone’s browser settings. There’s nothing to intercept with DNS, so the gateway instead redirects those fixed proxy endpoints to itself with a DNAT on the tunnel. A handset whose provisioned proxy is one of the built-in defaults just works, with no reprovisioning.
Built-in configuration
These are set on the fou-nat service (defaults shown). You normally don’t need to change anything.
| Setting | Default | What it does |
|---|---|---|
HDTP_ENABLE | 1 | Enables the gateway. Set to 0 to turn it off. |
HDTP_HIJACK_ENDPOINTS | 153.114.115.100:1905,153.114.116.100:1905 | Comma-separated IP:port proxy endpoints redirected to the gateway. |
HDTP_GW_PORT | 1905 | UDP port the gateway listens on. |
HDTP_LOG | info | Log verbosity for the gateway. |
The two default endpoints are common carrier UP.Link proxy addresses, so many stock handsets browse without any changes. On startup fou-nat prints the active hijack, e.g. hdtp-gw=10.55.0.1:1905 hijack=[153.114.115.100:1905,...].
Pointing your handset at the gateway
If your handset’s provisioned UP.Link proxy isn’t one of the built-in defaults, you have two options:
- Add your handset’s proxy to the hijack list. Set
HDTP_HIJACK_ENDPOINTSon thefou-natservice to include theIP:portyour phone dials. This is the least intrusive — the phone keeps its factory settings. - Reprovision the handset’s UP.Link gateway IP to ours. In the phone’s WAP/browser settings, change the UP.Link gateway (proxy) IP to one of the built-in defaults, or to the tunnel gateway IP directly. Do this when the phone’s proxy address is unknown or can’t be discovered.
Either way the browser must have a working data session first — see Packet Data Setup and Packet Data.
Known issues
- “System Error” on the handset. If the browser shows a System Error, exit and resume (reopen) the browser — the next session recovers and the page loads. This is a known issue and doesn’t require reconnecting data or restarting the phone.