| Receiving mms but not converting data |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through September 15, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| Martin Portman |
hi, my system is set up to receive and process/split mms messages into a directory, but it doesn't happen. i receive a .ini and a .mms file in the MMSCDATA directory, both files look ok, but the processing doesn't take place. all log files look ok (no howling error messages). i definately have the 'process mms' option selected and the dir nominated. where is the dir name stored? i couldn't find it anywhere! i'm using a sony/ericsson GC75 card and W2KPro, v4.11 of the gateway. thanks, martin | |||
| Bryce Norwood - NowSMS Support |
Hi Martin, The .MMS message in the MMSCDATA subdirectory is not related to 2-way MMS. When you send a message phone-to-phone through the MMSC, the way that MMS works is that the MMSC stores a copy of the MMS message (under the MMSCDATA subdirectory), and builds a dynamic URL that can be used to retrieve the message from the MMSC. The MMSC then sends a binary MMS notification message (over SMS) to the recipient mobile. The MMS notification message contains header information about the MMS message, and a URL pointer that tells the recipient how to retrieve the content of the MMS message. The recipient device then retrieves the MMS message content over a WAP session (or it could be direct HTTP). So what you are seeing on your system is the in-transit MMS message (and actually the MMSC keeps messages around for a default of 30 days). This is not related to the "2-way MMS". For "2-way MMS", the gateway is configured to receive SMS messages, and when the received SMS message is an MMS notification ... then the message is received as an MMS (and parsed and stored in the MMS-IN subdirectory). Perhaps the best way to start troubleshooting your problem is to verify that you can receive SMS messages properly with the gateway. Assuming that "Receive SMS" is enabled (it would have to be in order for "Receive MMS" to be enabled), and that you don't have any commands defined for processing SMS ... then a received SMS message would be depositied in the SMS-IN subdirectory. Are you able to send an SMS message to the phone number associated with your modem, and have it appear there? If not ... then we'd have to start by troubleshooting that capability. If that works ok, then you'd need to enable the debug log to see what is going on with the received MMS notifications. (Edit SMSGW.INI, and add Debug=Yes under the [SMSGW] section header ... then restart the gateway.) SMSDEBUG.LOG logs activity about SMS message flow, and the processing of received SMS and MMS messages. One issue that you can run into is if the MMS message was sent through an operator MMSC, some operator MMSCs have firewalls around their MMSC, and while the gateway can receive the MMS notification message over SMS, it cannot retrieve the MMS message content from the notification URL. (We're going to introduce a solution to this in the upcoming v5.0 release, which should be out to beta in mid-June.) -bn | |||
