| Length of binary sms |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through October 31, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| Nick Kirilov New member Username: Tatsumaki Post Number: 1 Registered: 08-2007 |
hi, I tried to send 192x50 oplogo-type sms message via web interface and the server always returns error. smaller messages like 72x28 are ok though. is there message length limit or something like that? thanks in advance. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7460 Registered: 10-2002 |
Hi, I'd need an example, and details of the error that you are seeing. Larger objects do need to be sent as multipart messages. Normally that gets handled automatically. But to be honest, an image of that size doesn't work very well being sent using Nokia Smart Messaging or EMS. It's better to send with WAP Push. Was the error that you received "Picture is too large for selected output format"? NowSMS will return this error if you try to send an image and it results in more than a 6 part SMS. This edit check is done as sort of a sanity check, because most phones that support Nokia Smart Messaging can't handle messages with a lot of parts ... and we don't want users to make a mistake that generates a lot of garbage SMS. But ... if you have a legitimate reason for exceeding this 6 segment limit (or testing), you can change it by manually editing the SMSGW.INI file, and under the [SMSGW] header adding MaxRingToneFragmentCount=##, where ## is the new limit on the number of parts to allow for a Nokia Smart Message or EMS. In fact, that's probably what happened ... if you send a 192x50 image as a Nokia Smart Message, that is going to require 10 SMS messages. So NowSMS will return an error that the object is too large unless you use the above setting. If you're trying to send a color operator logo to a Nokia phone, you want to use WAP push. The old Nokia Smart Messaging format pretty much only dealt with monochrome images. -bn | |||
