| No X-Mms-Originator-System header in MM4 message |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through July 14, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| Mindaugas Riauba Unregistered guest |
It seems that NowSMS does not set X-Mms-Originator-System header in outgoing MM4 message. How to fix this? Or I'm just missed something in documentation. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 2541 Registered: 10-2002 |
That is correct. The "X-Mms-Originator-System" header is only required if the "X-Mms-Ack-Request" header is set to Yes. And we do not ask for an MM4 ack (although we will generate them if requested for messages that we receive over an MM4 connection). I have heard rumours that some MMS interconnections are expecting to identify connected partners based upon this header. If you need to be able to set this field, what value are you expected to set here? We can easily add a parameter to allow this header to be included, but we'd like some more detail about your interconnection to understand why it is required. If there is potentially sensitive information involved, feel free to send it via e-mail to nowsms@now.co.uk if you are not comfortable posting here. -bn | |||
| Mindaugas Riauba Unregistered guest |
Do not know what are they doing with that header but our interconnect MMSC drops the message with error message "missing originator system". And the value I'd expect is something like system@[Domain Name fo MMS E-Mail] or mms@[....]. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 2548 Registered: 10-2002 |
Ok. That sounds like the interconnect provider has an arbitrary requirement for the inclusion of a header that is defined in the specification as optional. (Actually, upon further read, the spec does not clearly say if this is an optional or required field, but my interpretation is definitely that it is optional unless the "X-Mms-Ack-Request" header is set present and set to Yes.) But no matter, we'd rather deal with the problem than debate interpretations of the specification. There is a configuration parameter that can be used to deal with this requirement. I should have thought of that before my previous reply to you. The following feature is in v5.50:
So, just edit the appropriate VASP.INI file, and under the VASP header, add: ExtraHeader=X-Mms-Originator-System: system@[domain name for MMS e-mail] -bn | |||
