| Bug: MM4 flooding with MM4_forward.RES |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through July 28, 2006 ⬆ |
◄ ► |
| Author | Message | |||
| Dziugas Baltrunas New member Username: Menulis Post Number: 5 Registered: 02-2006 |
Hi, we're using NowSMS v5.51k as a MMSC. We noticed the following serious misbehaviour. If incoming message is coming via MM4 and routing callback returns Route=BlockMessage, then MM4_forward.RES is sent back to the foreign MMSC over MM4 with the following format: Wed Apr 5 08:01:15 EEST 2006 Received: from mmsc (unknown [x.x.x.x]) by x.y.tld (Mailer) with SMTP id DAB77A2181 for <system-user@xxx>; Wed, 5 Apr 2006 08:01:14 +0300 (EEST) X-Mms-3GPP-MMS-Version: 5.3.0 X-Mms-Message-Type: MM4_forward.RES Date: Wed, 5 Apr 2006 07:59:18 +0300 To: system-user@xxx Sender: system-user@yyy From: system-user@yyy X-Mms-Message-ID: "RDIEeAooawEAACy-AAAATAABvq0AAAAA" X-Mms-Transaction-ID: "RDIEeAooawEAACy-AAAATAABvq0AAAAA" X-Mms-Request-Status-Code: error-unspecified X-Mms-Status-Text: Unknown error occurred processing message Subject: MM4 Acknowledgement Message-ID: ED92946C@mmsc The message body is empty. However, after MM4_forward.RES is sent, original MMS stays in MMSCIN forever, so same MM4_forward.RES messages are repeated every scan of the MMSCIN, i.e. every second or so. I only came with ugly workaround to always return Route=Direct if the message is coming over MM4. In each of the .RFC file in MMSCIN folder where it stays forever the leading line is as folllows: X-MMSC-RCPT-TO: +xxxyyy/TYPE=DENY X-MMSC-Auth-User: VASP:x.x.x.x Just to note that this is not the case for MMS coming over MM1, where response "Unsupported recipient" is sent back for user in m-send-conf and MMS is removed from MMSCIN folder. Thanks, Dziugas | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5796 Registered: 10-2002 |
Hi Dziugas, In this particular circumstance, we are expecting the recipient to be blocked by an accounting pre-auth call, rather than the routing callback. The accouting pre-auth returning a deny response would block the message from entering the system at the MM4/SMTP envelope layer. Of course, what you are doing should work, and I agree that this needs to be fixed. We just did not anticipate this situation where the accounting callback is ok, but the routing callback indicates block. There is a patch scheduled for NowSMS 2006 early next week, which will include a fix for this problem. I'm going to see if we can also go back and apply the fix for a v5.51 patch. -bn | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5851 Registered: 10-2002 |
Update for NowSMS 2006 to correct this behavior at: http://support.nowsms.com/discus/messages/53/15129.html Still investigating to see if a v5.51 patch can be produced. | |||
