| Operator MMSC can send MMS but not receive |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through April 05, 2007 ⬆ |
◄ ► |
| Author | Message | ||||
| Joseph Smith New member Username: Falangjoe Post Number: 1 Registered: 08-2006 |
I am trying to set up the Now SMS/MMS Gateway as an operator MMSC. I am using a Logica WAP gateway and port 9900 for the MMSC. The phones can send MMS messages and they receive the SMS notification, but they can't download the MMS messages. Is this a problem with not using port 80?
| ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6473 Registered: 10-2002 |
Hi, That is bizarre. The receiving client is connecting back to tell us that it received the notification, and that the actual downloading of the message has been deferred to later. I don't understand why this would be. The only time that I remember seeing this particular type of response in the past was with some phones that have a setting to block "anonymous" messages. Anonymous messages are messages that don't have a sender. (There is an MMSC.INI setting to not include the sender address in the notification ... so you don't want to use that, otherwise some phones might consider all messages to be anonymous.) But I wouldn't expect that to be the problem that you are experiencing, because it would be odd to apply that configuration setting in a new setup. I'm thinking that maybe there is a problem with the URL that is being sent out in the notification. Does your MMSC "Host Name" match the host name in the MMSC messaging server URL that you have configured in your phones? I can see that the phones have no problem connecting to the messaging server URL, so if NowSMS is generating a URL it will be putting this configured "Host Name" in the notification URL, so you'd want it to be the same. Based upon my read of your log, I think that you are using "166.230.5.11" as the value in both, which should be fine. Do you see the same thing if you have a phone send to itself? Is it possible to consult the WAP gateway log to see if the phone is trying to request the URL in the notification (it would look like this: 166.230.5.211/20060829/15/4A4F3A14.mms). I'm puzzled ... I don't see port 8900 as being an issue, as long as there is a clear path of connectivity, which there appears to be because the phones (even the receiver) can clearly connect to the MMSC. Maybe there will be a clue if you can go over some of the items that I've mentioned above. One other thought ... I don't think it should be a problem, but I would suggest changing the post URL to remove "/mm1" ... just leave it as "/". I don't think this would cause a problem, but normally "/mm1" is used only for a VASP connection. -bn | ||||
| Joseph Smith New member Username: Falangjoe Post Number: 2 Registered: 08-2006 |
I removed the mm1 part from the wap push and the phones. They can now send and receive. Thanks, Joseph | ||||
| Joseph Smith New member Username: Falangjoe Post Number: 4 Registered: 08-2006 |
Sorry, I meant wap pull not wap push. Thanks, Joseph | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6482 Registered: 10-2002 |
Thanks for feedback...it was a stretch for me to even think that might have been the problem! | ||||
MMSCDEBUG FILE
