| Can I receive MMS(via MM7) and deliver using MM4? |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through June 06, 2005 ⬆ |
◄ ► |
| Author | Message | |||
| Anonymous |
I've successfully configured the NowSMSC/MMSC so when I receive a MMS message from a VASP account over MM7 interface, the NowSMS/MMS gateway delivers that messages [Direct Delivery] successfully via SMS and WAP. The MM7 interface is my application. My SMSC connection is to SimpleWire, and NowMMSC gateway is internet accessible for WAP connections from wireless carriers. I am now looking to route specific destinations(phone numbers) to a MM4 route. Can NowSMS/MMS gateway support this configuration - to recieve in via MM7 and route out MM4? How? All my current configurations to support a specific route for MM4 fail. All MMS messages received continue to route through the SMS/WAP method. | |||
| frankgrygus@lucent.com Unregistered guest |
Bryce, My name if Frank Grygus, sorry for the previous ANON. I am trying to setup a trap for additional MMS OUTBOUND Routing, and I am unsuccessful. I want to use the MMSC GUI to compose a MMS message and specificy a unique recipient address which is also define in the Additional Route section of MMS Outbound Routing. That special route should go out MM4, versus the default Direct Delivery. It continues to use Direct Delivery default. It's simply using the Default everytime. | |||
| frankgrygus@lucent.com Unregistered guest |
My specific configuration files (.ini), and MMSC/SMSC debug files were sent to you via email. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3720 Registered: 10-2002 |
Hi Frank, Assuming that the phone number you are sending to definitely matches one that is listed in the recipient address mask ("Route messages to this account..." for the definition under "MMSC Routing"), then the most likely issue is that NowSMS always attempts MMS direct delivery to any phone number that is listed in the "MMSC Users" table. Based upon a quick look at the files that you e-mailed me, it does appear that you have the address masks defined correctly, so I would expect this "MMSC Users" issue. The problem with the "MMSC Users" table is that it has been adapted over time to have two purposes. The primary purpose was originally to define users to the MMSC. (Hence the assumption that direct delivery would always be used.) A secondary purpose was to allow e-mail to MMS for these users. There is a patch available if you need the e-mail to MMS without the MMSC support. It is described here: http://support.nowsms.com/discus/messages/485/6695.html | |||
| frankgrygus@lucent.com Unregistered guest |
Bryce, I followed the links, and downloaded the update. I also downloaded the latest NowSMSC Gateway. Back in August/September I worked with you on an issue with our ability to send binary SMS w/J2ME payload. You helped us identify our problem, and even provided a patch for the gateway. I am currently running the patched version [v5.51 (b20040815)]. Is the fix that I am speaking of included in the latest build of the gateway that I downloaded? or in the new patched version for disabling DirectDelivery still support the above fix? I am concerned that if I upgraded or patch my current release, I may break the functionality that I currently have. can you address this? Frank | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3733 Registered: 10-2002 |
Frank, All changes or fixes are cumulative. I'm not sure what your previous fix may have been, but based upon the date, it looks like it was a pre-release of v5.51. (The release version has a date code of 20040823.) I would suggest installing v5.51 (download the trial version from here and it will recognise your existing serial number). Next apply the patch referenced in the above thread. The patch just contains product updates after the v5.51 release version. So we've only tested it as an update to that release. -bn | |||
| frankgrygus@lucent.com Unregistered guest |
Bryce, Ok, the interface is working; that is MM4 Outgoing routing. I now have another problem. The SMTP server on the other end supports internet email and MM3(as I am being told) - not MM4. Can the NowMMSC Gateway convert MMS message that it receives from VASP accounts to MM3(or email) and deliver via MM3 or SMTP? What is the difference between MM3 and MM4? Frank | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3790 Registered: 10-2002 |
Just an on-line follow-up. Frank and I discussed this matter further via e-mail. In a recent update to NowSMS v5.51, we added a configuration setting when defining an "MM4/SMTP" route under "MMSC Routing" ... to allow you to specify whether MM4 message format should be used, or a generic SMTP e-mail format. -bn | |||
