| Getting Support |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through September 15, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| Keith (Keith) |
This list is the best way to get your support questions answered, our technical people will be monitor this regularly. | |||
| Antony |
Hi, Thanks guys; I've been testing with your 60 day demo MMSC app. So far very cool. Great job guys. Quick question; I'm having probs getting inbound email to be accepted by the MMSC. MMSCXXX.log file just reports REJECTED every time. SMS & MMSC User set correctly, MMSC domain name and relay host set okay also. Email being address and sent to alias@setdomainname etc. Any ideas? Ta. | |||
| Bryce Norwood - NowSMS Support (Bryce) |
Antony, I've checked into this, and the only conditions that should cause this to occur are: 1.) "alias" from "alias@setdomainname" does not eixst. 2.) "setdomainname" from "alias@setdomainname" is not defined as either the "Domain Name for MMS E-Mail" or the "Local Host Name or IP Address" on the MMSC configuration tab. It sounds like you believe that is set correctly, which leads me to think that maybe the relay host is adding some unexpected information. I'd suggest that you go into the program directory that you installed NowSMS into ... and edit the MMSC.INI file. Under the [MMSC] section header, add the following statement: Debug=Yes Restart the MMSC service. Repeat your test. Stop the MMSC service. In addition to the other log file, there should be an MMSCDEBUG.LOG. E-mail that file to nowsms@now.co.uk, and we'll take a look at it. My suspicion is that we're getting some unexpected data in the SMTP "RCPT TO" header. Remove the statement from the MMSC.INI file, and restart the service. -bn | |||
| Gareth |
Hi I've downloaded the 60 day trial which - on the face of it seems GREAT! and is just what we are after. I am particularly interested in the MMSCLite aspect however when my 7650 connects to the gateway I can see an http 502 always being returned to the wap server. Consequently the phone never sends the message. The wap gateway and the now gateway are on the same box, the homepage of the mmsc is set to http://myboxip:8001/myusername=mypassword I can see that the service grabs the port and is listening on it. however there is no other communication taking place?! Any suggestions? Thanks Gareth | |||
| Bryce Norwood - NowSMS Support (Bryce) |
I don't see anywhere that our gateway would return a 502 error. That kind of sounds like a gateway error, where the gateway does not like the response that it is getting back from the MMSC. MMS does do some communication through WAP gateways that is unusual. (Segmentation and Reassembly - SAR - needs to be supported for transferring large data. HTTP response code 204 is used for some responses. And, of course, MIME type can be an issue.) What WAP gateway are you using? It may not be a WAP gateway issue at all, but at first glance, that is what it sounds like. We may be able to get a better look at what is going on by reviewing a debug log from the MMSC. Manually edit the MMSC.INI file, and under an [MMSC] section header, add the statement Debug=Yes. Restart the MMSC service. Repeat your test. E-mail the MMSCDEBUG.LOG file to nowsms@now.co.uk, and we'll take a look at it to see what it suggests. -bn | |||
| gareth |
debug log shows the following: 09:54:14:911 [0] main: Now MMSC Web server started on port number 8001 09:54:16:914 [2] ThreadListenSMTPIn: Now MMSC SMTP server started on port number 25 09:54:16:914 [0] main: 57 Days remaining in trial version 10:00:00:428 [0] main: 57 Days remaining in trial version ----------------------------------------- thats it? Is like the mmsc does not get the request from the wap server. The wap server i am using is the Nokia Activ server.... Any further thoughts? | |||
| Bryce Norwood - NowSMS Support (Bryce) |
Gareth, Yes, it looks like the request is never making it off of the gateway and to the MMSC. Is this Nokia Activ Server under your control, or is it located elsewhere? (I'd be curious what its logs report.) One thing comes to mind is a firewall type of issue. We've seen this with a number of operator WAP gateways, and it could conceivably be an issue in your own environment as well. Basically, there are a number of operator WAP gateways that are firewalled from connecting to content servers on ports other than 80. That could stop the WAP gateway from talking to your MMSC which I can see is on port 8001. How about if you try to send to the phone? Try sending an MMS message to the phone through the gateway, and look at the "FAQ" section of the web site where there is an entry "Problem: I receive an MMS notification message, but am unable to access the MMS message". Let me know how you proceed, or if you could use some more suggestions! -bn | |||
| tendyliu |
Hi, I use the web menu interface to send a short message. The English words does well while Chinese words changed into corrupted chars. Have you ever thought using Unicode encoding to send the MMS/SMS? Thanks. We wish Now SMS/MMS will support Double Byte enconding and we plan to buy it if it does. Thanks. | |||
| Bryce Norwood - NowSMS Support (Bryce) |
Hi tendyliu, We're working on Unicode support. If you're not already in contact with us, please e-mail nowsms@now.co.uk, and we'll work with you to make test versions with Unicode support available to you for testing. -bn | |||
| Anonymous |
Hi, I've a nokia 7650. I use Now SMS/MMS Gateway. I 've configured my phone with: GPRS APN myoperator_APN Username [blank] Password [blank] WAP GW 213.48.20.10 Home page http://my_NowSMSMMSGateway_IP:81/myuser=mypsw I can send and receive mms. Can I use another wap gateway? For example the ip where the Now SMS/MMS Gateway is installed (naturally, the ip is public); it's a wap gateway isn't it? Thank you for your help. | |||
| Bryce Norwood - NowSMS Support (Bryce) |
Sure, you can use any WAP gateway that supports SAR (segmentation and reassembly), and that provides unrestricted access to internet content. Most operator gateways will even work ok. However, some operators will not connect to content servers on ports other than 80, which could be a problem with your current gateway configuration. You might want to try configuring your device to use our gateway at 213.48.20.10. -bn | |||
| Anonymous |
have a problem with sending messages Event Log ****************************************** warning: SMS message could not be sent to +xxxxxxxxxxx, Invalid Source Address ****************************************** how do I set Source Address | |||
| Bryce Norwood - NowSMS Support (Bryce) |
Hi, Based on that error message, I assume that you are using an SMPP or UCP/EMI connection to an SMS service provider. In the configuration of the SMSC connection, there is a field called "Sender Address". The "Invalid Source Address" message is an error coming from the SMSC directly, so I would assume it means that it wants to see a "Sender Address" specified. -bn | |||
