| One MMS message costs 2 or 3 SMS messages. Is this normal |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through December 19, 2005 ⬆ |
◄ ► |
| Author | Message | |||
| winner.tako Unregistered guest |
Hi! I got everything set up: nowsms/mms 5.11b / clickatell HTTP interface with credits. When I send an MMS message from my mobile phone to myself through the NowSMS/MMS gateway it all works fine. But.... Somehow NowSMS sends two or even three sms messages through clickatell to send me the MMS message. I thought only one SMS message (3 credits) would be enough. Is this correct? The log of the connection is shown below: ///// SMSOUT: 2005-08-30 18:05:42,SAR-+31623856108-fd-2-1.req,MMS user +31623856108 (winner.tako),+31623856108,OK -- HTTP - api.clickatell.com:80,SubmitUser=localsystem-mmsc;Binary=1;DCS=F5;UDH=0B05040B84 23F00003FD0201;Data=FD06226170706C69636174696F6E2F766E642E7761702E6D6D732D6D6573 7361676500AF848C82983243373537313338008D908918802B33313632333835363130382F545950 453D504C4D4E008A808E02022A88058103093A8083687474703A2F2F3133302E38392E362E323333 2F32303035303833302F31382F3243373537 2005-08-30 18:05:46,SAR-+31623856108-fd-2-2.req,MMS user +31623856108 (winner.tako),+31623856108,OK -- HTTP - api.clickatell.com:80,SubmitUser=localsystem-mmsc;Binary=1;DCS=F5;UDH=0B05040B84 23F00003FD0202;Data=3133382E4D4D533F69643D253262333136323338353631303800 ///// SMSDEBUG: 18:05:14:616 [0] main: Now SMS/MMS Gateway Web server started on port number 8800 18:05:16:648 [0] main: 59 Days remaining in trial version 18:05:38:360 [2] ThreadProcessModem: Processing SAR-+31623856108-fd-2-1.req... 18:05:38:780 [2] ThreadProcessModem: GET /http/sendmsg?api_id=150250&user=winnertako&password=[not shown]&to=31623856108&text=FD06226170706C69636174696F6E2F766E642E7761702E6D6D732 D6D65737361676500AF848C82983243373537313338008D908918802B33313632333835363130382 F545950453D504C4D4E008A808E02022A88058103093A8083687474703A2F2F3133302E38392E362 E3233332F32303035303833302F31382F3243373537&udh=0B05040B8423F00003FD0201&Data=FD 06226170706C69636174696F6E2F766E642E7761702E6D6D732D6D65737361676500AF848C829832 43373537313338008D908918802B33313632333835363130382F545950453D504C4D4E008A808E02 022A88058103093A8083687474703A2F2F3133302E38392E362E3233332F32303035303833302F31 382F3243373537 HTTP/1.1 User-Agent: Now SMS/MMS Gateway v5.51b (b20050428) Host: api.clickatell.com Accept: */* Connection: close 18:05:42:406 [2] HttpResponseWait: Chunked response Ok 18:05:42:406 [2] ThreadProcessModem: HTTP/1.1 200 OK Date: Tue, 30 Aug 2005 16:05:15 GMT Server: Apache/1.3.33 (Unix) PHP/4.3.11 mod_ssl/2.8.22 OpenSSL/0.9.7a X-Powered-By: PHP/4.3.11 Connection: close Transfer-Encoding: chunked Content-Type: text/html ID: e2e8d26f9ba4908d28efad25484265ab 0 18:05:42:416 [2] ThreadProcessModem: Processing SAR-+31623856108-fd-2-2.req... 18:05:45:730 [2] ThreadProcessModem: GET /http/sendmsg?api_id=150250&user=winnertako&password=[not shown]&to=31623856108&text=3133382E4D4D533F69643D253262333136323338353631303800& udh=0B05040B8423F00003FD0202&Data=3133382E4D4D533F69643D253262333136323338353631 303800 HTTP/1.1 User-Agent: Now SMS/MMS Gateway v5.51b (b20050428) Host: api.clickatell.com Accept: */* Connection: close 18:05:46:371 [2] HttpResponseWait: Chunked response Ok 18:05:46:371 [2] ThreadProcessModem: HTTP/1.1 200 OK Date: Tue, 30 Aug 2005 16:05:38 GMT Server: Apache/1.3.28 (Unix) mod_ssl/2.8.15 OpenSSL/0.9.7d PHP/4.3.4 X-Powered-By: PHP/4.3.4 Connection: close Transfer-Encoding: chunked Content-Type: text/html ID: 25aaf4a63ad63052ae7f2c70fae44d09 0 | |||
| Wolfgang Röckelein Unregistered guest |
Well, you can use different settings to bring the length down. From my notes from this forum: In the MMSC.INI file, under the [MMSC] section header, add the parameter CompactMMSURL=Yes. This shortens the length of the MMS message URL that the MMSC generates. Also under this same section header, add MMSNotificationNoSubject=Yes, which removes the subject line from being included in the MMS notification. (If the MMS client prompts before download, it will be less friendly without the message having a subject before you download, but that is a small price to pay.) MMSNotificationNoSender=Yes This removes the sender from the MMS notification envelope. We have observed that some phones, most notably the SonyEricsson T68i cannot reply to a message where the sender is not included in the notification. I believe some other phones (Sharp GX-1?) will also ignore the message completely. Nokia3510Compatible=No This uses a more compact encoding for the MMS notification ... but we have observed that it causes problems with the original release of the Nokia 3510 ... and we have also observed that the Panasonic GD87 does not understand the notification when this format is used. Added support for configuration parameter Nokia3510Compatible=No in MMSC.INI file. (Default value is Yes.) When MMS message notifications are sent via SMS in a way that is compatible with the Nokia 3510, this causes the notifications to be 31 bytes longer than the short notification format used in versions prior to v4.0. The longer notifications cause more MMS notification messages to be sent out as multiple SMS messages instead of single SMS messages. If Nokia 3510 compatiblity is not important for your installation, use this setting to enable the shorter MMS notification message format. Make sure that the "Local Host Name or IP Address" that is specified on the "MMSC" page of the NowSMS configuration is as short as possible. | |||
