| MMS default route problem |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through May 02, 2013 ⬆ |
◄ ► |
| Author | Message | |||||
| FRaveau New member Username: Fraveau Post Number: 15 Registered: 06-2012 |
Hi I can send and receive MMS on our production platform since today. Text SMS also work from the Web interface. I have difficulties in setting the default MMS route. I choose the “Convert to SMS with Web link” option and try to send and MMS to a customer that is not in the MMS user list. I expect the customer to receive an SMS with a web link as I don’t have any additionnal route configured. Am I right? But it doesn't work. The receipient doesn't receive anything. The SMSDebug log file shows that NOW.SMS tries to send a message that correspond to my binary template in the SMSC Connection box. It’s not normal isn’t? Thank you
| |||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4049 Registered: 08-2008 |
Hi, There seems to be a strange character in the subject line of the MMS message which is causing the confusion. The space character between "TR" and ":" is not a normal space character. It is a no-break space, which is sometimes used in word processors. The presence of that character is causing confusion in the resulting SMS message. NowSMS does not understand it, and because of the presence of this character, it is assuming that to preserve the message content, the text message needs to be sent using Unicode encoding. That fails, as the HTTP SMSC interface being used does not understand. (Separate issue: How does this SMS provider support Unicode messages?) As a temporary work-around, in the HTTP SMSC definition, try changing the character set to UTF-8. This will likely result in a garbage character in the SMS instead. -- Des NowSMS Support | |||||
| FRaveau New member Username: Fraveau Post Number: 16 Registered: 06-2012 |
Hi, The space character between "TR" and ":" is added by my HTC when I forward an MMS. So it's a pretty much common use case isn'T? I already was in UTF-8 I've unchecked the option "Use hex encoding for unicode message" and it works better. Any explanation? Thanks | |||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4052 Registered: 08-2008 |
Hi, I don't disagree that it is a somewhat common use case. I don't like to get into rationalisations of why, but I wouldn't consider this to be a major problem. We've just not noticed it because in a normal configuration, the result would be sent out as a Unicode format SMS. No one would know that the SMS message was in Unicode format, unless they analysed the log files ... or if their SMSC connection had an issue with Unicode messages. Sending Unicode SMS is usually only a problem when using an HTTP SMSC connection, because of inconsistenices and lack of a standard to define the parameter interface. A typical MMSC configuration would use an SMPP SMSC connection, and Unicode SMS would just work. In any event ... 1.) In future versions, we will add a translation for the Unicode non-breaking space character (0xA0) to the GSM space character when converting to SMS. 2.) I should have mentioned the "Use hex encoding for Unicode message" setting. I'm glad you tried it. By default, if a message contains non-GSM unicode charcters, we use the binary template for HTTP SMSC connections. If this setting is UNchecked, we use the text template, encoding the text in the character set specified. -- Des NowSMS Support | |||||
LOGS
