| Redundant "X-Mms-Originator-System" in MM4 |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through July 07, 2009 ⬆ |
◄ ► |
| Author | Message | |||
| Janek Shein |
Hi. Our fellow IC operator is complaining about multiple "X-Mms-Originator-System" headers in the MM4_forward.REQ We are running version 2008.06.03 Is there a way to fix this situation? Trace of headers follows. X-Mms-3GPP-MMS-Version: 5.3.0 X-Mms-Message-Type: MM4_forward.REQ X-Mms-Transaction-ID: "20081205.truncated" X-Mms-Message-ID: "20081205.truncated" X-Mms-Ack-Request: No X-Mms-Originator-System: system-user@mms.mncyyy.mcczzz.gprs Message-ID: <20081205.12.81D94C8C@a.b.c.d> Date: Fri, 5 Dec 2008 12:35:34 +0200 Sender: +xxxxxxxxxxx/TYPE=PLMN@mms.mncyyy.mcczzz.gprs From: +xxxxxxxxxxx/TYPE=PLMN To: +xxxxxxxxxxxx/TYPE=PLMN X-Mms-Priority: Normal X-Mms-Delivery-Report: No X-Mms-Read-Reply: No Subject: Multimedia Message X-Mms-Originator-System: mm4@mms.mncyyy.mcczzz.gprs Content-Type: multipart/related; start="<1354128737>"; type="application/smil"; boundary="---mime-boundary-2B9A9689.51AF7DCA---" | |||
| Janek Shein New member Username: Janek Post Number: 2 Registered: 04-2004 |
And I've found a cause for that. Sorry if I made someone waste his time. We had an "ExtraHeader" value in the VASP.INI with the "X-Mms-Originator-System: mm4@mms.mncyyy.mcczzz.gprs" in it. Obviously we were required to transmit this header and do this exactly this way, but I can't remember why anymore. And since this ExtraHeader did not replace the header, but instead added a duplicate - it started confusing the receiving MMSC. The only question still bugging me is: what is the intended behaviour for NowMMSC in this case: add a header or replace a header? wbr, Janek | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 304 Registered: 08-2008 |
Hi Janek, I was about to guess that it had to be that type of setting, so I'm glad you noticed it. The ExtraHeader setting is working as intended, although it would be nice if it could replace a header instead. I'm not sure why you might have needed this setting at one time. My guess would be that you had an issue with an older version where this headed might have been excluded for some request types other than forward ... Like perhaps delivery receipts or read receipts. The spec doesn't define this header for one or both of these message types, but some MM4 implementations still want to see it there. Current versions do always include that header in all requests. -- Des NowSMS Support | |||
