| Problem sending MMS from phone to email |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through September 15, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| Alvin Khor |
I've installed the sms/mms gateway 4.11 in a private LAN environment for testing. The phone is a GX10 configured to do CSD dialup to a RAS machine connected in the LAN. DNS in the LAN environment is setup to resolve all the names correctly. I was able to send MMS from phone to a phone number successfully, but fail when sending to an email address (from phone too). The MMSC-20030423.log doesn't show any error at all. The recipent email address shows up correctly in the log file. 1. What is wrong? I've ensure that the MMSC user has the correct phone number and alias (which will be used for email matching). 2. The SMTP relay also doesn't seems to work. 3. Is there a feature in NowSMS to 'integrate' with an external mail server? | |||
| Bryce Norwood - NowSMS Support (Bryce) |
Hi Alvin, Sorry for the delay getting back to you. I suspect that the messages are currently queued in the MMSCOUT directory, but there is a configuration error that prevents them from being sent out. When the NowSMS MMSC has a message to deliver to e-mail, it queues it in the MMSCOUT directory, and then to send that message out to the SMTP world, it connects to the SMTP server configured as the "SMTP Relay Host" on the MMSC page of the configuration dialog. Basically, all SMTP outbound messages will be routed via SMTP to the "SMTP Relay Host" configured. I suspect that the relay host is either not configured correctly, or is refusing to accept messages from the MMSC. You can find more information about what is going on by enabling the debug log in the MMSC. You can do this by manually editing the MMSC.INI file and under the [MMSC] section header, adding Debug=Yes. After you restart the MMSC service, there will be an MMSCDEBUG.LOG that logs debug information about the MMSC processing. Please feel free to send that file via e-mail to nowsms@now.co.uk if you need assistance in figuring out what something means in that log file ... the debug log was really intended for our own support purposes, but often you can get a quick idea of what is going wrong by looking at it yourself. -bn | |||
