| MMS defective error message for the recipients |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through July 28, 2006 ⬆ |
◄ ► |
| Author | Message | |||
| Frans Sunarya New member Username: Franssunarya Post Number: 2 Registered: 05-2006 |
Hello, I have several questions : 1. I am trying to send an MMS by using NowSMS/MMS web interface. I have completely filled header and content form fields. Unfortunately, only the header can be received by the recipient while the content(such as text, image or audio) cannot. I am using Siemens S65 as the GPRS Modem and I am currently using my university LAN which means, my PC IP address is not accessible from outside. And one more thing, if the recipient uses Siemens, they obtain "MMS Defective" error message in their handphones. Does anyone know how can I send an MMS completely(not merely the header)? 2. I have created a new routing account in MMSC Routing so that I can forward an MMS to a specific operator. I have filled +62* for the recipient numbers that will be routed to this connection and I have tested the connection and it works. I have set it as the default route as well. But I don't see any effect at all. The example is that whenever I am sending an MMS by using Now SMS/MMS web interface, the MMS message seems to be kept in the local gateway, not forwarded to the specific MMS operator that I have defined in the MMSC Routing tabs. And the recipients still can't obtain the whole message (only can get the header) and for those who use Siemens got "MMS Defective" error message in their handphones while they try to retrieve the MMS message. Does anyone know solutions for my problems? Thank you very much and feedbacks are really highly appreciated. You can also contact me at franssunarya@yahoo.com Regards Frans | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6009 Registered: 10-2002 |
Hi Frans, I don't have enough detail to answer your questions. The "MMS Defective" error sounds like it would be caused by NowSMS trying to act as a direct delivery MMSC. In that type of configuration, without a dedicated IP (or in many cases even with a dedicated IP), the receiver is going to only receive the MMS notification header, and will be unable to fetch the content. (Please see http://www.nowsms.com/howmmsworks.htm.) It sounds like in question #2, you have tried to set up an "MMSC Routing" definition so that messages are delivered to the operator MMSC over GPRS. If you make this the default route, then messages should be routed via that route ... the only exception is that if a user account is in the "MMSC Users" list, then NowSMS will always try to perform direct delivery to the recipient. (There is an MMSC.INI setting to disable this behaviour.) If this does not answer your question, then I believe that I would need to see debug logs from your system in order to understand your configuration. Enable the SMSDEBUG.LOG and MMSCDEBUG.LOG from the "Serial #" page of the NowSMS configuration. Repeat your sending attempts, and then ZIP those logs and post in reply to this thread. -bn | |||
