Error log on MMSC - REJECTED-FAILED

Error log on MMSC - REJECTED-FAILED SearchSearch
Author Message
Rambeloson Andry Juvenale
New member
Username: Andry_juvenale

Post Number: 11
Registered: 01-2014
Posted on Monday, August 04, 2014 - 06:39 am:   

Dear Support,
Could you Explain us what means these errors logs on the MMSC please and thank you to tell us what's wrong because since last Friday our service doesn't work.
You find attached an extract of the Logs on MMSC.
Best regards
Andry Juvenale
Orange Madagascar
application/octet-streamextract Log on MMSC
MMSC-20140801.LOG (1.2 k)
Rambeloson Andry Juvenale
New member
Username: Andry_juvenale

Post Number: 12
Registered: 01-2014
Posted on Monday, August 04, 2014 - 12:08 pm:   

Hi,
Thank you to give us a return please. the service MMS doesn't work till now.
You find attached an extract log the day the problem appeared (MMS-20140731.LOG).
Best regards
Andry Juvenale
Orange Madagascar
application/octet-streamlog 31/07/2014
MMSC-20140731.LOG (0.6 k)
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4972
Registered: 08-2008
Posted on Monday, August 04, 2014 - 04:23 pm:   

Hi Andry,

None of these logs contain any meaningful transactions.

If MMS clients are attempting to send messages, those messages are not getting as far as the MMSC.

I can explain what is in the logs, but these are not MMS transactions. So this explanation will not help resolve whatever is wrong with your service.


quote:

2014-08-01 12:07:22,MMSRETRIEVE,192.168.25.99,,,,FAILED
2014-08-01 12:07:22,MMSRETRIEVE,192.168.25.99,,,,FAILED
2014-08-01 12:07:22,MMSRETRIEVE,192.168.25.99,,,,FAILED
2014-08-01 12:08:17,MMSRETRIEVE,192.168.25.99,,,nice ports,/Trinity.txt.bak,FAILED
2014-08-01 12:08:28,MMSRETRIEVE,192.168.25.99,,,sip:nm,FAILED
2014-08-01 12:10:04,MMSRETRIEVE,192.168.25.99,,,,FAILED
2014-08-01 12:10:14,MMSRETRIEVE,192.168.25.99,,,,FAILED
2014-08-01 12:11:34,MMSRETRIEVE,192.168.25.99,,,server-info,FAILED
2014-08-01 12:12:39,MMSRETRIEVE,192.168.25.99,,,,FAILED




These are HTTP GET requests. Someone (or an automated scanner) is trying to connect to the MMSC as a web server and probably trying to test if it is a web server with a known vulnerability that can be exploited.

To avoid this, you'd use a firewall to block access to the MMSC HTTP port from outside your network.

This has nothing to do with any MMS service problems.


quote:

2014-08-01 14:29:01,MMSIN,,localsystem-resend,+261320752090,19/15/752090,unknown,695




An MMS message was not picked up by the recipient and it is being resent in SMS format with web link.


quote:

2014-08-01 15:36:57,SMTPIN,192.168.25.99,test_1@example.com,test_2@example.com,REJECTED,REJ ECTED
2014-08-01 15:36:57,SMTPIN,192.168.25.99,test_1@example.com,test_2@example.com,REJECTED,REJ ECTED
2014-08-01 15:38:17,SMTPIN,192.168.25.99,openvas@VM,root+:"; sleep 8 ;",REJECTED,REJECTED
2014-08-01 17:13:45,SMTPIN,192.168.25.99,test_1@example.com,test_2@example.com,REJECTED,REJ ECTED
2014-08-01 17:13:45,SMTPIN,192.168.25.99,test_1@example.com,test_2@example.com,REJECTED,REJ ECTED
2014-08-01 17:14:27,SMTPIN,192.168.25.99,openvas@VM,root+:"; sleep 8 ;",REJECTED,REJECTED




Similar to the HTTP GET issue, an SMTP app or scanner is looking for SMTP vulnerabilities.

It is odd that all of these HTTP and SMTP transactions are coming from 192.168.25.99, which is a private IP address in your network.

But again, this has nothing to do with any MMS service problems.


quote:

2014-07-31 06:37:01,MMSIN,,localsystem-resend,+261320205389,99/94/205389,unknown,106061
2014-07-31 14:28:46,MMSIN,,MMS.Delivery@mms.orange.mg,+261320752090,20140731/14/2362EE4F,SA R-+261320752090-52-2-1.req,711
2014-07-31 14:28:46,MMSIN,,MMS.Delivery@mms.orange.mg,+261320752090,20140731/14/2362EE4F,SA R-+261320752090-52-2-2.req,711
2014-07-31 16:05:01,MMSIN,,localsystem-resend,+261320706441,29/05/706441,unknown,45019
2014-07-31 17:46:00,MMSIN,,localsystem-resend,+261327316264,59/05/316264,unknown,697
2014-07-31 18:14:01,MMSIN,,localsystem-resend,+261320781567,89/05/781567,unknown,701




The local system-resend entries are MMS messages that were not picked up by the recipient and are being resent in SMS format with web link.

The MMS.Delivery entry is a delivery report. I do not have enough information to understand what might have triggered this, except maybe someone read an MMS that had been converted to SMS with web link.


If these are the only entries in your log, then this suggests there is a fundamental connectivity problem on your network. MMS clients perform an HTTP POST transaction to submit an MMS message. There is no indication of any such transactions being received by the MMSC.

Has something else changed on your network?

--
Des
NowSMS Support
Rambeloson Andry Juvenale
New member
Username: Andry_juvenale

Post Number: 13
Registered: 01-2014
Posted on Tuesday, August 05, 2014 - 08:11 am:   

Dear Support,

Thank you for these explanation, it helps us greatly to understand the situation.
the problem is solved. you can close this topic as solved.
thank you for your support.

Best regards
Andry Juvenale
Orange Madagascar