Not receiving MMS messages...How do I confirm MMS message is sent f...

Not receiving MMS messages...How do I confirm MMS message is sent f... SearchSearch
Author Message
akhila Lakshminarayanan
New member
Username: Akhilal

Post Number: 1
Registered: 05-2009
Posted on Monday, May 11, 2009 - 10:32 pm:   

We are trying to setup a local MMSC server that we can use for testing send/receive of MMS messages without using the GSM/modem/operator network but instead using SMPP over TCP/IP setting. I'm send MMS message usign the nowsms web interface and I don't see the message on the other end. I need to confirm if the message is sent properly from the server. How do I confirm this? Also, I need help making sure the configuration settings are accurate. Please see the attached configuration doc for the screenshots of the settings I have and the logs attached.
application/vnd.openxmlformats-officedocument.wordprocessingml.documentconfiguration settings
We are trying to setup a MMSC server in order to test MMS messages send.docx (163.6 k)
application/octet-streamMMSCDEBUG.LOG
MMSCDEBUG.LOG (20.1 k)
application/octet-streamSMSDEBUG.LOG
SMSDEBUG.LOG (2.9 k)
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 767
Registered: 08-2008
Posted on Tuesday, May 12, 2009 - 02:37 pm:   

Hi,

What are you trying to send the message to?

What is receiving the message on the other end?

Do you know for certain that the receiver is able to process MMS notifications?

It appears that you are trying to send MMS notifications to a short code, and I would not expect that to work.

Please read the "How MMS Works" link at http://www.nowsms.com/howmmsworks.htm.

Then, if you could explain a little bit more about what you're trying to accomplish, maybe I could offer some advice.

--
Des
NowSMS Support
akhila Lakshminarayanan
New member
Username: Akhilal

Post Number: 2
Registered: 05-2009
Posted on Tuesday, May 12, 2009 - 07:35 pm:   

Thanks for looking into this issue, Des. I'm trying to send a message to a mobile phone where the client is configured to listen to the the host name/IP/port of the server. We are using "Direct MMS delivery" where the server is setup as a MMSC.

Can you please explain the following statement a bit more?

"It appears that you are trying to send MMS notifications to a short code, and I would not expect that to work. "

On the client side, I'm not even getting a WAP push. I would like to first confirm the server is setup and configured correct. How do I confirm that the WAP push is actually sent from teh server? Is there anything else that I need to check on the server-side?
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 776
Registered: 08-2008
Posted on Wednesday, May 13, 2009 - 04:03 pm:   

When you send an MMS message to a phone number, the MMS delivery process is triggered by an MMS notification message sent via WAP Push over SMS.

It sounds like you are in a lab environment that wants to use WAP push over IP instead of over SMS.

If that is what you are trying to do, then you can find information about mapping phone numbers to IP addresses for MMS notifications here: http://support.nowsms.com/discus/messages/485/4184.html

If that is not what you are trying to do ... then I am not clear on what you are trying to do. What I see is that the MMS notification is being sent to 1234 via WAP push over SMS.

--
Des
NowSMS Support
akhila Lakshminarayanan
New member
Username: Akhilal

Post Number: 3
Registered: 05-2009
Posted on Thursday, May 14, 2009 - 09:42 pm:   

Des,
Note that we are not using the operator n/w. Ours is a test environment with the MMSC setup as a SMPP over IP and using Logica SMSC simulator to send the SMS to the client.

So, based on the SMSC/MMSC logs attached, can you please help me confirm that the server is actually sending the WAP push message to the client?

The issue may be one of the following:
1) incorrect client settings to connect to server (we are connecting using the servername/MMSC/SMSC port/username/pwd to the users defined in the MMSC users tab

2)issue with the logica SMSC similator sending the message to the client.

Is there a way to confirm #2 above? could there be other causes that can lead the client not getting the WAP push that I might be missing?

Is there any suggestions you have on how to troubleshoot this?

Thank you,
akhila
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 801
Registered: 08-2008
Posted on Friday, May 15, 2009 - 12:39 pm:   

Hi akhila,

Are you actually writing the MMS client? I've never seen a client that could actually retrieve WAP push messages from the Logica simulator.

The SMSOUT-yyyymmdd.LOG will show the details of any SMS messages that NowSMS has sent out. They are logged here at the point that the message leaves NowSMS (accepted by the SMSC connection). So you can verify that NowSMS is sending the MMS Notification over WAP Push over SMS by inspecting that log file.

--
Des
NowSMS Support
akhila Lakshminarayanan
New member
Username: Akhilal

Post Number: 4
Registered: 05-2009
Posted on Friday, May 15, 2009 - 08:00 pm:   

yes, our MMS test client tries to connect to the server and just polls to retrieve the message. The client works just fine with one of the servers but unable to connect to another server. I've already verified that the settings between the servers are exactly the same.

I do see the following entry in the SMSOUT log file:

2009-05-15 11:51:08,SAR-1234-b8-2-2.req,LocalSystem,1234,OK -- SMPP - vmpmxdtp3a:8801,SubmitUser=localsystem-mmsc;SMSCMsgId=Smsc2024;Binary=1;DCS=F5;U DH=0B05040B8423F00003B80202;Data=32312E4D4D533F69643D3132333400

Does the above confirm that there is no issue with the nowsms server or the logica SMSC(since as per your mail, the entry in the log file shows the message is sent by nowsms and accepted by the SMSC).
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 806
Registered: 08-2008
Posted on Monday, May 18, 2009 - 02:58 pm:   

It would mean that the Logica simulator accepted the message.

The UDH header is the second part of a segmented WAP Push message.