| Send MMS with Java WAP Push not working? |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ |
◄ ► |
| Author | Message | |||
| Robert Barretto New member Username: Barretto Post Number: 35 Registered: 09-2019 |
Hi all, I'm trying to programmatically send an MMS to a phone using "WAP Push with Web Link" but the SMPP message I'm seeing doesn't look proper. I was expecting to see "application/vnd.wap.mms-message" in the SHORTMESSAGE element of the SMPP SUBMIT_SM message. I'm using the information from the Send MMS Message with Java page to build the MMS message. I'm setting the following parameters in the request: "PhoneNumber" = "+14697771234" "From" = "+15558889999" "MMSText" = "just some text" "MMSFile" = some binary image data "MMSWAPPush" = "Yes" "MMSCRoute" = "my_term_route" The MMSC route I'm passing in is defined on the NowSMS MMSC, and it is configured as "Route messages using WAP Push with Web Link". The NowSMS MMSC accepts my POST, but the SMPP message that is being sent out my chosen MMSCRoute is of the form (I removed the unprintable characters to make it easier to read): mms.redacted.com/20201208/09/7225DC48.WML?id=%2b14697771234+15558889999 - Multimedia Message If I don't use the Web form to send the message, for example, I send in an MM4 to the NowSMS MMSC, it selects the same "my_term_route" outbound route and sends an SMPP message out of the form (I altered http to h_tp so that it won't format as a link): application/vnd.wap.mms-message 41256549 +15558889999/TYPE=PLMN h_tp://mms.redacted.com/20201208/11/41256549.MMS?id=%2b14697771234 I originally did not include "MMSWAPPush" in my POST message body, because I thought the selected "my_term_route" MMSCRoute (defined to route using "WAP Push with Web Link") would determine the format of the SMPP SUBMIT_SM message, but it did not. I tried adding "MMSWAPPush" set to "Yes", thinking that would add the missing "vnd.wap.mms-message" stuff to the SMPP message, but it didn't. I also tried "MMSSMSPush" and that did not have an effect on the SUBMIT_SM message body either. The MMSWAPPush and MMSSMSPush options didn't seem to have any effect at all. If I use the NowSMS Web Interface directly (i.e., not using my application at all) to send the MMS using the same route, I get the same format as when I use my application. The web page form doesn't have options for MMSSMSPush or MMSWAPPush on it, so maybe that's why when I add them programmatically they don't have any affect on the outgoing message. Am I doing something wrong? My NowSMS MMSC is v2020.01.15, if that helps. Thanks, //Robert | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 8383 Registered: 10-2002 |
Hi Robert, You should definitely not be including MMSWAPPush=Yes. Also, set the default route to "Direct Delivery". "WAP Push with Web Link" means something different. (An outdated idea that made a little sense 15 years ago that isn't worth explaining.) Regards, Bryce Norwood NowSMS Support | |||
| Robert Barretto New member Username: Barretto Post Number: 36 Registered: 09-2019 |
Hi Bryce, I must have had a old MMS Outbound Routing definition with the WAP Push setting(perhaps from when I originally integrated the MMSC into our network). It's not actually used. I use the MMSRoutingURL hook to select the correct route, and totally forgot for terminations I return 'Direct'. I'll drop out the WAPSMSPush parameter and change MMSCRoute to "Direct", that should make it work. I'll let you know how it goes. Thanks! //Robert | |||
| Robert Barretto New member Username: Barretto Post Number: 37 Registered: 09-2019 |
Hi Bryce, Just a follow up. It's working. I tried two ways and they both work. I used "MMSCRoute" = "Direct" and that makes it work like I was expecting. I also updated the "my_term_route" MMSC Routing definition from "WAP Push with Web Link" to "Director Delivery (Internal MMSC)", and then set "MMSCRoute" = "my_term_route" and it routed just like using "Direct". Thanks for the help in jogging my memory about the "Direct" route. Getting old sucks. lol Thanks again! //Robert | |||
