| Problems in MM4. URGENT! |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through October 19, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| David Chkhartishvili New member Username: Datoch Post Number: 46 Registered: 06-2004 |
Hi Bryce, We're using MM4, version 5.5.0, message format: MM4. We have two problems: 1. Forward.RES not requested from our side. 2. No Expiry time is set. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6905 Registered: 10-2002 |
Hi David, I forwarded some information to Keith on this. My suggestion is that you update to the NowSMS patch that can be downloaded from http://www.nowsms.com/download/patch2007.zip. There has been a hidden VASP.INI option to enable the X-Mms-Ack-Request: Yes header for some time. But the latest version includes fixes for how this is implemented, in particular to address some problems with routing the acks (forward.RES) back correctly in all configurations, and in the handling of related acks for delivery and read reports. And, now that we have seen that this header is required by most MMS interconnect providers (but not required for most point-to-point connections), a configuration option has been added to the "MMSC Routing" dialog, where you can enable the "Request MM4 Ack" setting (without having to edit VASP.INI). Also, make sure that your "MMSC VASP" definition, which defines how you receive messages over the MM4 connection has an "MM4 Ack Routing" setting that routes the MM4 acks back to the appropriate "MMSC Routing" definition. In most situations, when connecting to one of these interconnect providers, they cannot use SMTP authentication to login to your server with a username and password. They can only authenticate based upon their IP address, and they may have multiple IP addresses. To accomodate this, you need to define multiple "MMSC VASP" accounts with these IP addresses as the account name. -bn | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6906 Registered: 10-2002 |
David, I forgot to address your 2nd question. The Expiry time parameter is an optional parameter. I don't see anywhere that it is defined as being required. The receiving system should apply its default. However, there is a way that you could insert it if necessary. At least, you could insert one of the defined value formats. The MM4 X-Mms-Expiry header can contain a value of either an absolute date/time stamp (e.g., Fri, 23 Feb 2007 12:32:04 -0000) or a relative time in seconds. X-Mms-Expiry: 259200 would signify a relative expiry time of 3 days (259200 seconds). X-Mms-Expiry: 604800 would signify a relative expiry time of 7 days. You may need to experiment to determine what value is acceptable by your interconnect partner. It is possible to insert an additional fixed header into outbound MM4 messages by editing VASPOUT\accountname\VASP.INI, and under the [VASP] header, add ExtraHeader=X-Mms-Expiry: 259200 If you want to insert multiple headers, put the text \r\n in between headers (which will cause a carriage return/line feed to be inserted). -bn | |||
| Michael New member Username: Michael123 Post Number: 2 Registered: 02-2007 |
Hi Bryce, Thank you, problems fixed. Now we got another problems: 2 days ago we installed this patch (now our version is v2007.02.14) and something strange happened with our NowSMS. 1. Service is restarting few times per day. There are no other info/errors in event log. 2. There are much more messages in queue than it was before. We have enabled message queue size alert and statistic is really different. By analyzing times when it happens, looks like it doesn't depends on service restart case. We can't find yet does those problems impact on normal operation of NowSMS, but think they should be fixed. Thank you in advance, Michael | |||
| Dziugas Baltrunas New member Username: Menulis Post Number: 16 Registered: 02-2006 |
Hi, there is an issue with NowSMS 2006 both with patch2007 applied and without regarding MM4 headers. Sometimes it's necessary for a outgoing MM4 route to specify X-Mms-Originator-System different from system-user@[Domain Name for MMS E-Mail]. Having ExtraHeader=X-Mms-Originator-System: user@domain set in VASP.INI results in MM4_forward.REQ request with double X-Mms-Originator-System header, i.e. X-Mms-Originator-System: system-user@mms.mnc002.mcc246.gprs [..more headers..] X-Mms-Originator-System: user@domain I guess this is because ExtraHeader only appends headers instead of merging. Is it possible to have a separate setting for custom X-Mms-Originator-System in particular MMS route or make ExtraHeader to override existing headers (if ones exist)? Thanks, Dziugas Baltrunas | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6992 Registered: 10-2002 |
Hi Dziugas, There is another setting that you can apply in the VASP.INI file: MMSOriginatorSystem=user@domain -bn | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6993 Registered: 10-2002 |
Hi Michael, I'm sorry that I missed your previous message. Are you still experiencing these restart problems? I've updated the download link referenced above ... http://www.nowsms.com/download/patch2007.zip to the 2007.03.15 version. There are only minor differences, but earlier 2007 versions had a change in how MMS accounting callbacks work, and this seemed to be causing problems on busier systems, where the accounting callbacks could become backlogged. Or ... actually ... if you're the Michael that works with David ... then you already have an update. If this is the case, there is no need to download rhis update, as there is little difference between this version and what you are running. However, there is one MM4 related issue that was just addressed in 2007.03.15 that may be of interest. If you are connecting to MACH, there is an issue that they cannot support transaction IDs larger than 50 characters. Depending on the length of your MMSC host name, recent changes in the format of the MM4 X-Mms-Transaction-Id field could cause this ID to exceed 50 characters, causing problems with interconnections to MACH. The 2007.03.15 update addresses this MM4 specific issue. -bn | |||
| David Chkhartishvili New member Username: Datoch Post Number: 47 Registered: 06-2004 |
Hi Bryce, Thanks! David | |||
| Dziugas Baltrunas New member Username: Menulis Post Number: 17 Registered: 02-2006 |
Hi, there is definitely an incorrect usage of X-Mms-Originator-System header in MM4_delivery_report.REQ. According to specifications, no X-Mms-Originator-System is present in MM4_delivery_report.REQ. Instead Sender header should be used for that purpose and it's definition coincides with X-Mms-Originator-System in MM4_forward.REQ. However, NowSMS (v2007.02.14) uses both X-Mms-Originator-System and Sender headers with the same value (equal to MMSOriginatorSystem set in VASP.INI) which might confuse some of interconnect hubs: X-Mms-3GPP-MMS-Version: 5.9.0 X-Mms-Message-Type: MM4_delivery_report.REQ X-Mms-Transaction-ID: "60755231.94578772@mmsc" X-Mms-Message-ID: "148478240@mms.hub" X-Mms-Ack-Request: Yes X-Mms-Originator-System: system-user@mmsc.lt Message-ID: <60755231.94578772@mmsc> Date: Tue, 8 May 2007 12:18:32 +0300 Sender: system-user@mms.bi.lt From: +123456/TYPE=PLMN To: +654321/TYPE=PLMN X-Mms-MM-Status-Code: Retrieved X-Mms-Status-text: Retrieved Is it possible to make a fix so that X-Mms-Originator-System header wouldn't be used in MM4_delivery_report.REQ? Thanks, Dziugas Baltrunas | |||
| Dziugas Baltrunas New member Username: Menulis Post Number: 18 Registered: 02-2006 |
Sorry, example provided had incorrect values - X-Mms-Originator-System and Sender headers values are actually the same, i.e.: X-Mms-Originator-System: system-user@mmsc.lt Sender: system-user@mmsc.lt Dziugas | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7131 Registered: 10-2002 |
Hi Dziugas, Ok. I would not expect the presence of this header to cause a problem, as it is always possible to include more headers in an SMTP format message than are formally defined. But for consistency, we will remove it for "MM4_delivery_report.REQ" and "MM4_read_reply_report.REQ" requests, as this header is not explicitly defined for those requests. This will be reflected in versions after 2007.05.16. If you are facing an actual problem due to the presence of this header, then let me know, and I will try to get an update to you. -bn | |||
