i wasnt aware that there was a thread regaurding this problem. i have been working on this since the first tachi htc messaging client was released (191
. Just to clarify a couple things...
no matter if you use:
http ://mms.sprintpcs.com/servlets/
http ://mms.sprintpcs.com/servlets/mms?X-SPRINT-MDN
http ://mms.sprintpcs.com/servlets/mms?X-SPRINT-MDN=+1XXXXXXXXXX
http ://mms.sprintpcs.com/servlets/mms?X-SPRINT-MDN=1XXXXXXXXXX
http ://mms.sprintpcs.com/servlets/mms?X-SPRINT-MDN=XXX-XXX-XXXX
http ://mms.sprintpcs.com/servlets/mms?X-SPRINT-MDN=XXXXXXXXXX
http ://mms.sprintpcs.com/servlets/mms?X-message-id
http ://mms.sprintpcs.com/servlets/mms?X-message-id=+1XXXXXXXXXX
http ://mms.sprintpcs.com/servlets/mms?X-message-id=1XXXXXXXXXX
http ://mms.sprintpcs.com/servlets/mms?X-message-id=XXX-XXX-XXXX
http ://mms.sprintpcs.com/servlets/mms?X-message-id=XXXXXXXXXX
your recieve will work, send will say it sent, and we all know what happens.
i really believe the solution has to do with this key. "ph1uzoe52iuw"
Can somebody sniff the information being sent while using arcsoft, then one using htc messaging client?
i am still working hard at getting this working myself, and will keep this thread updated on my progress. nice to know others are hard at work at it as well.
-deck