[hunterdg]

here's a breakdown... the condensed version.. i can expand if needbe
Disclaimer: my knowledge is of Sprint ONLY, this may or may not apply to other CDMA carriers.
Please be aware the info below is fairly low-level but comprises enough to understand the basic process... i can get more specific if necessary

first a few terms

error 1012: failure to IOTA
error 67: failure to authenticate

IOTA = Internet Over The Air, the process of populating M.IP 1 (and M.IP 2 if PAM capable) automatically, otherwise called "provisioning"

NAI = Network Access Identifier, a component of an M.IP Profile, specifically the username

M.IP Profile = Mobile IP Profile, a 'profile' (aptly named) that contains, amongst other things, the NAI and associated password necessary for authentication to sprint's servers (for data transmission ONLY, this has NOTHING to do with voice)

API: Active Profile Index, a setting in the phone that corresponds with the M.IP Profiles and tells the phone which profile to use when attempting a data connection. Settings are by number, 0,1,2 are the only settings in use today, 0 is default from factory.

All internet capable devices have at LEAST 2 M.IP's, and PAM capable devices have 3 (for now)

M.IP's can be viewed/edited by ##778#
anything in brackets [] below is dynamic, different for every user, and is entered into the phone WITHOUT said brackets

M.IP '0' (often called Default M.IP Profile) is set at the factory as follows:
NAI: [hex esn]@hcm.sprintpcs.com
password: ???
DO NOT EDIT THIS ENTRY! (reason below)

M.IP '1' is set by IOTA as follows:
NAI: [username]@sprintpcs.com (no parens)
password: randomly generated

M.IP '2' is set by IOTA for PAM capable devices as follows:
NAI: [username]@pam.sprintpcs.com
password: randomly generated

process is as follows, keep in mind this occurs on EVERY data-capable phone regardless of whether a data plan exists. ALL 3G accounts are assigned a plan code that automatically generates an NAI and associates it with the MDN/MSID combo. This plan code is REQUIRED for ANY sort of internet connectivity on the phone. You never see this plan code on your bill. Without an additional data pack, data usage is charged per-kb, i believe 2 cent/kb right now

brand spankin new phone:
API is set to 0 (from factory)
gets ##MSL#'d with MDN & MSID (phone number)
phone reboots
first time phone requests data connection, it references the API
API = 0 so phone uses M.IP 0 (M.IP's 1 & 2 are currently blank)
NAI of M.IP 0 is [hex esn]@hcm.sprintpcs.com, HCM = Handset Configuration Manager
HCM cross references the esn with the device's MDN/MSID, and initiates an IOTA***
IOTA automatically programs M.IP 1 (and M.IP 2 if the device supports PAM)
IOTA then changes the API to '1' so that the device will use M.IP 1 henceforth.

*** You MUST NOT edit M.IP '0', as if you do, though your data connection may still work (assuming you have a valid M.IP 1 and 2), if for whatever reason these fail, you will NOT be able to IOTA, as IOTA depends on a valid M.IP '0' BEWARE, there is NO reset (NONE WHATSOEVER) that will restore the M.IP 0 to defaults. If you edit it, you will need to visit a store for OTW (Over The Wire) provisioning should your M.IP 1 or 2 fail.


Newer sprint devices have the ability to detect when the device is tethered. when this occurs, the API is switched to '2', triggering the M.IP 2, with the NAI: [username]@pam.sprintpcs.com. (notice the PAM, for Phone As Modem)
when connecting to the server, this NAI tells the server the device is tethering. The server checks the customer's account for a PAM plan, and if none is found, the connection is refused. If a PAM plan IS found, the connection authenticates as usual.

Some have posited that the M.IP 2 (PAM NAI) redirects through a sprint proxy that does not compress jpeg images, like the regular M.IP 1, but i can neither confirm nor deny this.

the whole idea behind the "Disable Multiple NAI" reg hack is to disable the device's ability to switch from M.IP 1 to M.IP 2 when tethering is enabled. Thus fooling the sprint servers, and appearing as a normal M.IP 1 NAI, where the usage is billed straight to your 'vision pack'

I have not had time to test the "disable multiple NAI hack, but rest assured i will, and i will post my findings.

i have a few questions if anyone can give me definitive answers (please no "i think"s)

1. is wmodem ICS?

2. i know that using ICS over bluetooth does not use the DUN profile, rather it uses the PAN profile. while this is all well and good, is there a way to FORCE DUN instead of PAN

3. does the mogul/titan's bluetooth support multiple simultaneous connection over PAN?

4. I'm assuming the ICS via USB identifies as an NDIS device.. is there a way to FORCE it to identify as a MODEM?

5. the reg hacks that "unhide" BT, USB, and IRDA Dun (in the reg hacks thread)... do they do what i'm looking for? If so, after i have applied them, how can i 'find' the options to USE them? (they are NOT in ICS dropdown)

Thanks in advance for any answers to my question, and i hope this clears things up about the NAI/IOTA/blah blah issues.

please let me know if i can be more explicit. i'd be happy to, though it may be in a not-so timely manner