| Issue in the FWD-RES format sent by the MMSC |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through June 09, 2011 ⬆ |
◄ ► |
| Author | Message | |||
| David New member Username: Legolas23 Post Number: 1 Registered: 03-2011 |
Hello, I have the version 2010.02.09. I meet an issue when a foreign MMS tries to send a MM4_FWD_REQ to the Now MMS. The platform Now MMS responds with a X-Mms-Message-ID with the separator "/" instead of "." Example of messages : In the FWD-REQ, X-Mms-Message-ID: "20110224.00.8C47C922@193.251.160.246" In the FWD-RES, X-Mms-Message-ID: "20110224/00/8C47C922@193.251.160.246" Based on 3GPP standard, X-MMS-Message-ID is the identification of one MMS. X-Mms-Message-ID is supposed to remain same in FWD-REQ, FWD-RES, DR-REQ and DR-RES. Can you help me? Is there a workarround which permit to correct this point ? Regards | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3005 Registered: 08-2008 |
Hi David, This is a known issue with a fix at the following link: http://www.nowsms.com/update-patch-2010-11-26 -- Des NowSMS Support | |||
| David New member Username: Legolas23 Post Number: 6 Registered: 03-2011 |
Hello, I installed the patch version 2010.11.26, however the issue continues to occur. So, it seems now that the MM4_forward_RES is not sent for all messages MM4_forward_req received. Is there possible to trace or monitore the MM4_forward.RES with the logs (and if yes, with which logs?)? In the MMSCDEBUG.LOG, the trace shows the MM4_FORWARD.REQ but not the response in the complete format : MM4_FORWARD_REQ : -----mime-boundary-10D2E6E9.D317D62A-- 00:07:07:656 [3] ThreadProcessConnectionSMTP: 250 Message Accepted 00:07:07:984 [3] ThreadProcessConnectionSMTP: QUIT 00:07:07:984 [3] SendCommand: 221 Goodbye 00:07:07:984 [3] ThreadProcessConnectionSMTP: 221 Goodbye 00:07:08:093 [3] ThreadProcessConnectionSMTP: Closing SMTP Connection 00:07:08:093 [3] ThreadProcessConnection: Thread ended 00:07:08:250 [7] ThreadRouteSMTPIn: 0117897D.RFC 00:07:08:250 [7] ThreadRouteSMTPIn: X-MMSC-RCPT-TO: +590690410864/TYPE=PLMN 00:07:08:250 [7] ThreadRouteSMTPIn: +590690410864/TYPE=PLMN 00:07:08:250 [7] ThreadRouteSMTPIn: X-MMSC-Auth-User: VASP:64.124.202.164 00:07:08:250 [7] ThreadRouteSMTPIn: X-MMSC-Received-From: 64.124.202.164 00:07:08:250 [7] ThreadRouteSMTPIn: X-MMSC-ENV-MAIL-FROM: <+590690595030/TYPE=PLMN@na-mms.aicent.grx> 00:07:08:250 [7] ThreadRouteSMTPIn: Content-Type: multipart/related; type="application/smil"; start="<SMIL.TXT>"; boundary="---mime-boundary-10D2E6E9.D317D62A" 00:07:08:250 [7] ThreadRouteSMTPIn: From: +590690595030/TYPE=PLMN 00:07:08:250 [7] ThreadRouteSMTPIn: Sender: +590690595030/TYPE=PLMN@na-mms.aicent.grx 00:07:08:250 [7] ThreadRouteSMTPIn: Subject: Je sort avek william ! 00:07:08:250 [7] ThreadRouteSMTPIn: To: +590690410864/TYPE=PLMN 00:07:08:250 [7] ThreadRouteSMTPIn: X-Mms-Ack-Request: Yes 00:07:08:250 [7] ThreadRouteSMTPIn: X-Mms-Delivery-Report: Yes 00:07:08:250 [7] ThreadRouteSMTPIn: X-Mms-Message-ID: "20110415.00.BADFD332@193.251.160.246" 00:07:08:250 [7] ThreadRouteSMTPIn: X-Mms-Message-Type: MM4_forward.REQ 00:07:08:250 [7] ThreadRouteSMTPIn: X-Mms-Originator-System: admin@na-mms.aicent.grx 00:07:08:250 [7] ThreadRouteSMTPIn: X-Mms-Transaction-ID: "21754320110415040753467mms-exchange.opentransit.grx@mms-exchange.opentransit.grx@mms.mnc020.mcc340.gprs" 00:07:08:281 [7] MMSRoutingCallback: +590690410864/TYPE=PLMN 00:07:08:281 [7] MMSRoutingCallback: +590690410864/TYPE=PLMN 00:07:08:296 [7] DeliverMMSMessage: +590690410864/TYPE=PLMN 00:07:08:296 [7] DeliverMMSMessage: Found Phone Recip 00:07:47:343 [3] ThreadProcessConnection: Thread started 00:07:47:343 [3] ThreadProcessConnectionSMTP: Processing SMTP connection from 64.124.202.164... 00:07:47:343 [3] SendCommand: 220 SMTP Ready 00:07:47:343 [3] ThreadProcessConnectionSMTP: 220 SMTP Ready 00:07:47:468 [3] ThreadProcessConnectionSMTP: EHLO na-amr.aicent.grx 00:07:47:468 [3] SendCommand: 250-Ok 250-AUTH LOGIN 250 HELP 00:07:47:468 [3] ThreadProcessConnectionSMTP: 250-Ok 250-AUTH LOGIN | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3110 Registered: 08-2008 |
Hi David, If an ACK is not being generated, that is a very different issue than the one where the MessageID is different. For the "MMSC VASP" defined with account name 64.124.202.164, is the "MM4 Ack Route" set to the correct route for them to be sent back to? Are any MM4_forward.RES packets ever sent out? Or is this an occasional issue? (I don't think you'd actually see MM4_forward.RES in the log file, just an outbound SMTP connection, and a message going back to the X-Mms-Originator-System address.) It would help if I could see a longer excerpt from MMSCDEBUG.LOG. If you could ZIP or RAR and e-mail to nowsms@nowsms.com with "Attention: Des" in the subject line, I would like to see if I notice a pattern. -- Des NowSMS Support | |||
| David New member Username: Legolas23 Post Number: 9 Registered: 03-2011 |
Hello, Please find my answers about the differents questions : About the lack of MM4-FWD-RES : - A MMSC VASP have been created with a MM4 Ack routing correctly defined About the MM4_forward.RES received randomly For example, on 5150 messages sent at 16&17 April 2011, they received 135 FWD-RES (all of them with the correct format "." instead of "/") I will send you the trace and more details by email this morning. Regards | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3123 Registered: 08-2008 |
Hi David, I'm anxious to see the files you send me (especially MMSCDEBUG.LOG). There's got to be something different about the few messages that have MM4_forward.RES generated, compared to those that do not. -- Des NowSMS Support | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3127 Registered: 08-2008 |
Hi David, I replied to your email late last night after receiving the partial log files, so hopefully you received that and have been able to address the problem. I suspect there are a very large number of MM4 acks that are queued for processing, but that were generated prior to the "MM4 Ack Route" setting being configured. These old acks are clogging up the queue because NowSMS is trying to route them via email, but cannot figure out how to do so. If you manually delete them, the problem should resolve itself. The acks can be found in the MMSCACK directory. I would suggest deleting any files in that directory older than a few hours. Assuming the "MM4 Ack Route" is now correctly configured, there should be no further problem with a backlog. -- Des NowSMS Support | |||
| David New member Username: Legolas23 Post Number: 10 Registered: 03-2011 |
Hello, I have just checked the MMSCACK directory and we had 21761 files found. I deleted 13641 files (until as the 20 th April included - Installation date of the version 2010.11.26) Regards I will give you a feedback i Thanks | |||
| David New member Username: Legolas23 Post Number: 11 Registered: 03-2011 |
Hello, The modification works. We will keep monitor the traffic and will let you if problem occurs. Thanks for your help Regards | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7950 Registered: 10-2002 |
Hi David, As long as the MM4 Ack Route is set for all MM4 VASP accounts, the problem should not reoccur. The backlog occurs when the route cannot be determined for these MM4_Forward.RES packets. We are making several changes to prevent a backlog of this nature from occurring. A separate queue will be used only for ACKs where the route is known, so that unknown route ACKs will not clog the queue. We are also reducing the lookup time period that causes these messages to be processed extremely slow. -bn | |||
