|
|
||||
Well that theory is out the window because there is no MIP.2 in use on the mogul. Look for yourself--dial ##PST# and click view. Then click the left softkey and you can see the MIPs for yourself. The Default is the ESN-based, the MIP Profile 1 is the user name auth added by IOTA. That's it--the rest are all blank.
BTW, I am moving this thread to the mogul/titan forum since it relates directly to that device. |
|
||||
Go read hunterdg's big post in the first page of this thread. According to him it is used. It's M.IP for PAM. Just because it's blank doesn't mean the phone doesn't use it. Example: even M.IP1 is blank when you first get the phone proir to it being provisioned.
|
|
||||
Quote:
You can't use a blank MIP connection. The MIP1 is blank when you get the phone because it doesn't have any of your personal data in it yet (how could it? That's how it ships from the factory). When you do an IOTA then that MIP gets filled in with your user name as the NAI. Similarly if the handset were PAM-enabled the IOTA would have populated the MIP 2 field with a NAI of: username@modem.sprintpcs.com If the phone has been provisioned and it doesn't have a modem NAI in it then there is no way for Sprint to know you're tethering. Hope that clears it up for you. |
|
||||
guys.. I had just 'assumed' (we all know what that does) that the mogul was PAM-enabled, and thus M.IP 2 was populated with [username]@pam.sprintpcs.com.
i have not eer verified this, i just 'assumed'... as of now, (and according to sprint, as a result of my removal of the 'pam' plan), my device is failing to IOTA.. (ticket has been opened on sprint's end) in my troubleshooting steps i have reset all the M.IP's so for me, M.IP 1 & 2 are blank till my device can once again IOTA. I will at that time double check the M.IP 2 field and verify luv2chill's statement that it is, infact, NOT used on the MOGUL.. I can only assume he's correct though, as he has a mogul.. if a phone is PAM-capable (or rather, capable of detecting tethering), regardless of whether a PAM plan is attached, BOTH M.IP's are populated as i described in my long post.. the code i mentioned briefly, that creates these two M.IP's, is called IP_BASIC. (i mention this so that no assumption is made that the M.IP 2 is not created/populated unless a PAM plan exists.. this is simply not true).. If the mogul infact, does NOT get M.IP 2 populated, this explains how users are able to tether without any usage charges. the M.IP nai disable myth is BUSTED!!! will keep you updated, although i trust that luv2chill knows what he's talking about p.s.... if an M.IP is blank, it is useless... Last edited by hunterdg; 10-05-2007 at 10:23 PM. |
|
||||
Then explain how I was able to do it on my Samsung A920. The long and the short of it is,the sprint phones are setup to log in to a different accound depending on whether they are tethering or not. The hacks we do make it log in under the same account as normal internet. Thats how the work around works.
Quote:
|
|
||||
hunterdg, I had to go through this with Sprint twice myself, so I think I may know the solution to your problem. Even after Sprint had attempted several things on their end to fix it, nothing worked. So the tech I had on the line told me to do a Master Reset of the phone. Before you do this though, you will need to go into the ##(MSL)# PST tool and get your MDN and your MSID (this will save you from having to call Sprint later to reactivate) I can't remember which ## code brings up the menu where you can do the master reset from... maybe someone else in here can shed some light on it. I would find it, but I am running colonel's hybrid rom on my Mogul, and most of the ## codes dont work... Anyway, once you get it master reset and it all comes back up, just ##(MSL)# back into PST and put in your MDN and MSID values you wrote down earlier and let the phone reset. Once thats done, the phone is reprogrammed and your first IOTA should work as normal now. The master reset wipes out ALL data on the phone, including your M.IP profiles and all provisional information. Basically its like pulling the phone out of the box again.
Its up to you if you want to try it... but thats more than likely what they will have you do anyway. It worked right away for me, so maybe it will help you out some. Ok... watery eyes... itchy eyes... its gotta be time for bed. ![]() |
|
||||
thanks for the sugg.. the code you're looking for is ##786#.. and i've done that about three times now along with a hard reset and an ##3282#>reset..
no worky... they said it's an error in Service Pro (provisioning server) on their end.. thanks for the valuable input though!! |
|
||||
Hey no prob.. I figured it wouldn't hurt to suggest. It seems to me that there are a LOT of people having random issues over the last few days with the Vision service... perhaps this is all just a phenomenon on Sprint's end, and we are all jumping to conclusions too soon. It wouldn't be the first time a major company had systemwide issues that brought down a good chunk of their network... I would almost lay the blame to them for now. I am sure they have gotten plenty of calls stating - "My vision is borked... FIX IT"
Beyond that, this is as good a time as any to call them up and tell them you want service credits for all the downtime! ![]() |
![]() |
|
|
|