1. interex's Avatar
    Is it possible to use a custom MMS Gateway? I have edited the URL that is listed under the MMS Transfer Service Book, but it doesn't seem to contact the other MMS Gateway to try and send. It just fails.

    Anyone know of any way in getting this to work? I currently am with Sprint on an 8330m without BIS/BES and am told this is why MMS does not send.

    I'd like some way to use MMS if all possible, even through 3rd party.

    Thanks.

    BB OS 4.5.0.175
    12-20-09 01:56 PM
  2. interex's Avatar
    Ok, so here is an update on what I've done. (hxxp should be read as http)

    I have a Sprint 8330m on Boost Mobile with the Anworm Browser SB. As most people who have messed with Boost CDMA know, you have NO outgoing MMS. I called Sprint and they verified that I have tried to send MMS out and it's listed in "queue" to be sent. She did not know why it was not being sent out.

    She went and spoke with another rep who said because I was on Boost and needed to use the boost MMSC.

    So now I've pulled out the MMS Transfer [WPTCP] Service Book and pulled out tore it apart and this is what I get. First is MMS Transport, Second one is MMS Client.


    <record uid="0x1121e801">
    <field type="1">01000000</field>
    <type>0</type>
    <ruid>0x1121e801</ruid>
    <name>MMS Transport</name>
    <dsid/>
    <userid>-1</userid>
    <uid>MMS trans</uid>
    <cid>WPTCP</cid>
    <appdata>010d18687474703a2f2f6d6d732e737072696e747 063732e636f6d020101030101100b582d7063732d5b4d444e5 d</appdata>
    <compression>1</compression>
    <encryption>1</encryption>
    <description>MMS transport service book</description>
    <source>2</source>
    <field type="18">00000000</field>
    <field type="24">0a55b049</field>
    <hrt>
    <field type="10">04</field>
    <name>Any network</name>
    <npc>0x40</npc>
    <ip>0.0.0.0</ip>
    <ports>9201:8205</ports>
    </hrt>
    </record>

    <record uid="0xf92cf8ae">
    <field type="1">01000000</field>
    <type>0</type>
    <ruid>0xf92cf8ae</ruid>
    <name>MMS Client</name>
    <dsid/>
    <userid>-1</userid>
    <uid>MMS 001</uid>
    <cid>MMS</cid>
    <appdata>000112020100170101</appdata>
    <compression>1</compression>
    <encryption>1</encryption>
    <description>MMS client</description>
    <source>2</source>
    <field type="18">00000000</field>
    <field type="24">0a55b049</field>
    </record>

    -----------------------------------------------------

    In the MMS Transport, inside <apdata> you have in HEX, the following:
    hxxp://mms.sprintpcs.comX-pcs-[MDN]

    I am pretty confident if we can get this changed to reflect "hxxp://mm.myboostmobile.com" somehow we might get MMS on BoostBerry CDMA.

    Now... I have been able to change "hxxp://mms.sprintpcs.com" to "hxxp://mm.myboostmobile.com" and left the rest intact but instead of saying it sent, but didn't, it automatically fails to send (Red X). I also tried using "hxxp://mms.sprintpct.com/servlets/mms" and even from other providers and they all never work.

    So, I'm beginning to think that it might also be a part of the WPTCP vs WAP too.

    Anyone who might have any idea as to a solution, maybe some ideas, hints, pointers, etc... Please respond.
    Last edited by interex; 12-20-09 at 06:29 PM.
    12-20-09 06:02 PM
  3. interex's Avatar
    Wow, all the viewers and not one person has any idea? Crazy.
    12-21-09 07:09 PM
LINK TO POST COPIED TO CLIPBOARD