| Fields "from, to, cc, bcc" in file .hdr ignored. |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through October 19, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| whiskyconorujo New member Username: V800 Post Number: 5 Registered: 05-2007 |
Hello, my name is Antonio, and I've created some mms with smil and header files,(with mmscomp), but when i try to send this mms with the web interface of now.SMS (send MMS Message) i'm forced to specify a phone number in the web form, but I've specified a phone number in the header file already, and the fields in the header file are ignored. Is there any line-command utility in order to send mms files using the header specifications? Thanks you a lot!  | |||
| whiskyconorujo New member Username: V800 Post Number: 6 Registered: 05-2007 |
Sorry, I forgot to say that I'm using a Sony Ericsson V800 as a modem connected to the PC with an USB cable. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7207 Registered: 10-2002 |
Hi Antonio, No there is not. If you submit a precompiled MMS file via the web interface, we always override the recipient list. If you really want to submit that raw MMS message file, you could perform a direct HTTP POST via the MM1 interface. Define an "MMSC VASP" account in NowSMS. (And check "Allow Sender Address Override", otherwise the sender address specified in your MMS message will be ignored.) Then issue an HTTP POST transaction like this: POST /mm1/VASPaccountname=password HTTP/1.0 Content-type: application/vnd.wap.mms-message Content-length: ***** <insert blank line here> <insert data from raw MMS file here> You need to replace the "*****" with the actual length of the raw MMS file. Depending on what development environment you are working in, there may be an easy way to perform such a POST. -bn | |||
| whiskyconorujo New member Username: V800 Post Number: 7 Registered: 05-2007 |
Hi! I'm Antonio again. Thanks for your answer, but there are some things that I don't understand very well. First of all, my configuration is a laptop connected to a gprs modem (SONY ERICSSON V800) via the USB cable (MM1). The laptop can also be connected to the web network via Ethernet. Here are my questions : - how to create and configure a VASP account ? Can we use our gprs modem (with operator SIM card) to create this VASP account and how ? Or should we order a special account with the operator to create it ? - With a VASP account, can we receive and store some received MMS that we will resend after? How? Can we modify these received files to change the recipient number for example (by decompiling, modifying header parameters and recompiling received MMS)? - If the VASP account cannot be created via gprs modem, is there another solution to send the compiled MMS (filename.MMS) via a HTTP POST ? - The NowSMS web interface overrides some header parameters such as "from", "to", "cc" and "bcc". Are there any other parameters that are override ? Thanks a lot! | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7214 Registered: 10-2002 |
Hi Antonio, The "MMSC VASP" account doesn't care what type of connection you have for outbound MMS sending. Our terminology may be a little confusing, but when we say "MMSC VASP" in the NowSMS configuration, this is referring to an account that is allowed to submit MMS messages through NowSMS using one of the MMSC protocols (MM1, MM4, MM7 and/or EAIF). Essentially, it defines an account that allows an application to submit MMS messages into NowSMS.
No. You need to resubmit a modified message if you want to do that submitting as a VASP through the MM1 interface.
The "Send MMS Message" option in the NowSMS web interface was created primarily to allow for the submission of content objects that NowSMS would package into a binary MMS message. Since so many people seemed to want to send a pre-compiled binary MMS message, we look for a file with a ".mms" extension and treat it specially. I don't believe that we override any of the headers except for To/Cc/Bcc, which are replaced with the recipient list specified in the submission. However, the message will go through some transformation when it goes through message routing and goes out to the GRPS modem. In particular, some specialised headers might be removed if they are headers that are not normally generated by NowSMS. I'm sorry, but I do not have a list of headers that will or will not be removed. This particular area is something that we reviewed prior to our upcoming new release (pre-release at http://www.nowsms.com/download/nowsms2007.zip). In NowSMS 2007, for this type of routing, we will only remove any headers from the MMS message that are not valid for an MMS submission. (For example, X-Mms-Previously-Sent-By is valid in a retrieved MMS message, but it is not valid in a normal MMS message submission, so it would be removed.) Additionally, in NowSMS 2007, you can set the MMS version number for the MM1 connection to the operator over the GPRS modem, and we remove any headers that are not valid for the specified MMS version in order to prevent interoperability problems. -bn | |||
