Before submitting a message via MM1, a VASP (Value Added Service Provider) account must be defined to the Now SMS & MMS Gateway. This account is defined on the “MMSC VASP” configuration dialog.
To post to the Now SMS & MMS Gateway via MM1, you must connect to the HTTP port configured for the MMSC on the “MMSC” configuration dialog. And you must perform an HTTP POST of the MM1 content to a URI of “/mm1”, which is how the gateway knows that the VASP intends to submit in the MM1 format.
The HTTP headers of your POST must include a “Content-length:” header. To specify the account name and password of the VASP account, you must either include an “Authorization:” header for Basic authentication using the account name and password configured for the VASP account, or the account name and password can be specified on the request URI (e.g., /mm1/account=password). Alternatively, the request must originate from an IP address that matches the name configured for the VASP account. (If your software cannot generate an “Authorization:” header, it is possible to configure the account name for the VASP as an IP address, and in this case, the MMSC will recognise any connections from that IP address as being for this VASP account.)
The “Content-type:” header in the POST should be “application/vnd.wap.mms.message”, and the message should be a binary MMS message of the m-send-req format, formatted according to the MMS Encapsulation Specification, published by the Open Mobile Alliance.
Consistent with HTTP specifications, a “400” or “500” series HTTP response would be considered an error condition. The MMSC might return a “200” series response even if an error did occur, in which case information would be included in the “X-Mms-response-status” field of the MM1 response (MIME type “application/vnd.wap.mms-message”, X-Mms-Message-Type of “m-send-conf”) would contain a response-status value other than Ok.