| Forward.RES |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through July 07, 2009 ⬆ |
◄ ► |
| Author | Message | |||
| Michael New member Username: Michael123 Post Number: 6 Registered: 02-2007 |
Hello, We have few MM4 connections with other MMSCs. In debug.log I see that we aren't sending forward.res when it's requested from other side (I see forward.req). Can we enable forward.res? Thanks, Michael | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 835 Registered: 08-2008 |
Hi Michael, FORWARD.RES is enabled automatically when it is requested by the sender. The problem is likely that the MMSC does not know how to properly route it back to the sending system. All you should have to do is in the "MMSC VASP" definition that accepts the MM4 connection, set the "MM4 Ack Route" parameter to point to the "MMSC Routing" definition where the RES should be sent. There's some more information here: http://blog.nowsms.com/2008/06/mmsc-mm4-interconnection-basics.html If you're still having problems, tell me about the configuration settings and what you are seeing. -- Des NowSMS Support | |||
| Michael New member Username: Michael123 Post Number: 8 Registered: 02-2007 |
Hi Des, Thank you for quick reply. MM4 Ack Route is set to right value. In debug.log I see that MM4_forward.REQ is receiving by our system and "X-Mms-Ack-Request" set to "Yes". There are no forward.RES from our side. Maybe problem is in MM4_forward.REQ format which is sent to us? Regards | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 836 Registered: 08-2008 |
Hi Michael, What version are you running? There are a few different issues that could apply. There is supposed to be an "X-Mms-Orignator-System :" header that is present which indicates where the Ack should be sent back to. Some MM4 implementations forget to include that header. At some point, NowSMS started also using the "Sender:" header. For "MM4_delivery_report.REQ" and "MM4_read_reply_report.REQ", there is no "X-Mms-Originator-System:" header defined in the spec, and you are supposed to send the ACK back to the "Sender:". I believe starting in the 2007 release, if "X-Mms-Originator-System:" is not present, we would fall back to using the "Sender:" header. (Even though the spec does require "X-Mms-Originator-System:" in the "MM4_forward.REQ", we figure that real world interoperability is more important than the spec.) Then late in 2008, we found that some MM4 implementations were failing to provide either "X-Mms-Originator-System:" or "Sender:" headers! (You're probably wondering why we can't use the "From:" header, that's because that is defined as being the phone number of the MMS message sender, not the system MMSC address.) Beginning with the 2008.08.26 release, we started falling back to the "MAIL FROM:" command in the SMTP envelope as the recipient of the ACK if none of the required headers are present. So there's a good possibility that this is what you're encountering ... a system that is failing to include the required headers for telling us where the MM4 ack should be delivered back to. There were a lot of changes in late 2008, so if you are encountering this issue, at this point, I'd suggest updating to the 2009 release candidate which can be downloaded at http://www.nowsms.com/download/nowsms2009rc.zip. Or tell the interconnect that required headers are missing and see if they can fix it. -- Des NowSMS Support | |||
| Michael New member Username: Michael123 Post Number: 9 Registered: 02-2007 |
Hi Des, I install new version, but situation is the same. Here is a part from debug (hope it's a right part). Both, "X-Mms-Originator-System:" and "Sender:" are presented here, but we still have no forward.res 09:05:48:697 [9] ThreadRouteSMTPIn: DCE7757A.RFC 09:05:48:697 [9] ThreadRouteSMTPIn: X-MMSC-RCPT-TO:NUMBER/TYPE=PLMN 09:05:48:697 [9] ThreadRouteSMTPIn: X-MMSC-Auth-User: VASP:IP Add 09:05:48:697 [9] ThreadRouteSMTPIn: X-MMSC-Received-From: IP Add 09:05:48:697 [9] ThreadRouteSMTPIn: X-MMSC-ENV-MAIL-FROM: <NUMBER@DOMAIN> 09:05:48:697 [9] ThreadRouteSMTPIn: From: +NUMBER/TYPE=PLMN 09:05:48:697 [9] ThreadRouteSMTPIn: Sender: NUMBER/TYPE=PLMN@DOMAIN 09:05:48:697 [9] ThreadRouteSMTPIn: To: NUMBER/TYPE=PLMN 09:05:48:697 [9] ThreadRouteSMTPIn: Subject: 09:05:48:697 [9] ThreadRouteSMTPIn: Content-Type: multipart/related; type="application/smil"; start="<SMIL.TXT>"; boundary="--- 80.1244610346648" 09:05:48:697 [9] ThreadRouteSMTPIn: X-Mms-Originator-System: system-user@DOMAIN 09:05:48:697 [9] ThreadRouteSMTPIn: X-Mms-Message-Type: MM4_forward.REQ 09:05:48:697 [9] ThreadRouteSMTPIn: X-Mms-Transaction-ID: "GE0Tebe81defb4" 09:05:48:697 [9] ThreadRouteSMTPIn: X-Mms-Message-ID: "GE0Debe81d4c6a" 09:05:48:697 [9] ThreadRouteSMTPIn: X-Mms-Delivery-Report: Yes 09:05:48:697 [9] ThreadRouteSMTPIn: X-Mms-Read-Reply: Yes 09:05:48:697 [9] ThreadRouteSMTPIn: X-Mms-Ack-Request: Yes | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 927 Registered: 08-2008 |
Hi Michael, Those headers look normal. The "X-Mms-Originator-System:" header is present and "X-Mms-Ack-Request:" is set to "Yes", so we should be generating a MM4_forward.RES. (The above was talking about what happens when X-Mms-Originator-System is not present, and that is not a problem here.) Other than issues with "X-Mms-Originator-System:" not being present, and how different versions of the MMSC fall back to using "Sender:" or "MAIL FROM:" when this occurs, I don't see anything that would stop the MMSC from generating the MM4_forward.RES. I would expect that the MMSC is generating the MM4_forward.RES, but there is a problem occurring routing it. Newer versions of the MMSC queue the MM4_forward.RES in an MMSCACK directory (previous versions queue in the MMSCOUT directory). Maybe it would help to manually verify the configuration files to make sure everything is configured correctly. "X-MMSC-Auth-User: VASP:IP Add" tells us where the message came from. Look at VASPIN\IP Add\VASP.INI, and under the [VASP] header, check that MM4AckRoute is pointing to the correct outbound route. Next look at VASPOUT\"MM4AckRoute"\VASP.INI and verify that those parameters look correct. Unless there is a backlog in the MMSCACK directory, I can't imagine what would be going wrong. Are you sure that no MM4_forward.RES is being sent? The MMSCDEBUG.LOG doesn't show much information about the MM4_forward.RES. You'll see an SMTP connection initiated back to the other server, but we only log the SMTP commands for that connection, not the data ... so you don't see the actual MM4_forward.RES message. -- Des NowSMS Support | |||
| Michael New member Username: Michael123 Post Number: 10 Registered: 02-2007 |
Hi Des, Looks like after upgrading to new version MM4_forward.RES is sending. You are right, I can't see it in MMSCDEBUG.LOG, but partner operator confirmed that it was sent. Thanks a lot, Michael | |||
