View Single Post
  #124 (permalink)  
Old 12-20-2009, 05:17 PM
ziggy471's Avatar
ziggy471
Geek with a Gun
Offline
Location: NoVA
 
Join Date: Oct 2009
Posts: 744
Reputation: 6575
ziggy471 is a trusted member of the communityziggy471 is a trusted member of the communityziggy471 is a trusted member of the communityziggy471 is a trusted member of the communityziggy471 is a trusted member of the communityziggy471 is a trusted member of the communityziggy471 is a trusted member of the communityziggy471 is a trusted member of the communityziggy471 is a trusted member of the communityziggy471 is a trusted member of the communityziggy471 is a trusted member of the community
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: Native HTC messaging MMS fix (collaboration)

Quote:
Originally Posted by mswlogo View Post
Thanks Ziggy, be very interested in what you find.

How can you debug Sprint if you are on Verizon though?
Because I can still look at the raw data sent.

What's happening is that the messaging client is inserting the 'insert address token', in other words, it's expecting that the MMSC will insert the Originator address, your phone number. However, most CDMA carriers are expecting that the client inserts the Originator address. We have found the override for VZW and USC, but Sprint has obviously changed their server in the last 6 months, because what I had found was a fix dated 6 months ago stating that X-SPRINT-MDN should work.

I have found the registry key that should fix it, but haven't figured out where it should go. The registry key is IsInsertAddressTokenEnable, my guess is that it's a dword, and should be a zero. It's in the mms.dll file, located near a registry reference to Software\%s\MMS\OEM, which there are two of those, since %s should be a string and could either be 'Jataayu' or "Jataayu\Messaging" and are under HKLM.

There are other keys of interest in the messaging.dll:
CDMAOperatorName close to Software\OEM\RIL
ActiveProfileCDMA we already know of this one
CDMAUnreadCount should be under HKLM\\SOFTWARE\Jataayu\Messaging\MsgCount

In MessagingService.dll:
CDMASendOptionsErrorFlag

In mms.dll:
CDMAHeaders
GSMorCDMA
MDNorMIN
MDNPrefix

If you turn on logging, HKLM\SOFTWARE\Jataayu\MMS\SP, then when you send a message with WAP=NONE, there should be a send.dat and a recv.dat created under the \ErrorRep directory on the phone. If you look at the send.dat file, should be around position 18, assuming you delete all the text at the top, there is a 0x89, start of the From: field, then it's length, which is currently 0x01, and then 0x81, Insert Address Token, 0x97, start To: field, then the destination number.

If we can get the Jataayu client to insert the MDN instead of the insert address token, then we should see two phone numbers here. The other thing we need is to get the phone into 'true' CDMA mode for the MMS client, which we can not do yet until we figure out where to put the GSMorCDMA key. I deleted all references to GSM and set the MMSPreferredNetwork and SMSPreferredNetwork to 1 (0=Choose, 1=CDMA, 2=GSM), and renamed the HKLM\SOFTWARE\Jataayu\Messaging\MMS\Profile\GSM to CDMA. This should set it in CDMA mode, but if you go into MMS servers, there is no default server and receive doesn't work, but send does, since MMSPreferedNetwork is 1, I assume now this is for send only.

Sorry for such a long reply to a simple question, just wanted everyone to know the 'fun' I've been having. I don't plan on working on this any longer today, spent over three hours for five of us to dig our driveway out from the 18+ inches of snow, and I'm tired.

Everyone feel free to start experimenting from where I've left off, just make sure you make a backup of the registry prior to starting, someone forgot to do this and had to do a hard reset this morning, he'll remain nameless, but was punished with shoveling snow for three hours. lol



Z
Reply With Quote
This post has been thanked 2 times.