SMS Max Length 150 Characters | Search |
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through April 05, 2007 ⬆ |
◄ ► |
Author | Message | |||
Jorge L Soto P New member Username: Jsoto Post Number: 1 Registered: 09-2006 |
Some of my SMSC connections only support SMS of 150 characters max and don’t support segmentation. Is there a way for nowsms to limit the length of messages for those connections? Cut messages from SMS users to max 150 characters for those smsc connections. | |||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6577 Registered: 10-2002 |
Hi Jorge, There is no current facility to truncate messages in this fashion. This is something that we could investigate adding support for. What happens when you try to send a message longer than 150 characters (or a segmented message)? -bn | |||
Jorge L Soto P New member Username: Jsoto Post Number: 2 Registered: 09-2006 |
Bryce, The message goes to the query of my SMSC and stays there until the SMSC understands that the message can not be delivered, in between that all messages that get through my SMSC for that number are gonna stay there also, and are gonna be deleted with the longer one. | |||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6586 Registered: 10-2002 |
Jorge, Can I see error information from the SMSOUT log? Is this your only SMSC connection, or do you have others that don't have such restrictions? I'm trying to determine what the best way to handle this would be ... It would be easy to add a configuration option to truncate messages on a particular SMSC connection to 150 characters (or an arbitrary value). But it would be difficult to figure what to do with multipart segmented messages. There is a configuration option where you could tell NowSMS that the connection should be used for text messages only ... and a multipart segmented message is considered to be binary, so NowSMS would not attempt to deliver it via the connection. You can specify this by putting BinaryOrTextOnly=Text under the [SMPP - host:port] header. If that solution works for dealing with the segmented messages, then the option to truncate text messages could probably be implemented fairly quickly. | |||
Jorge L Soto P New member Username: Jsoto Post Number: 3 Registered: 09-2006 |
Bryce, I'm gonna use the BinaryOrTextOnly=Text under my SMPP connections, and for the truncate the implementation is just for some connections. | |||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6591 Registered: 10-2002 |
Ok. Let me see what we can do about truncation. Are you on NowSMS 2006? | |||
Jorge L Soto P New member Username: Jsoto Post Number: 4 Registered: 09-2006 |
Yes | |||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6598 Registered: 10-2002 |
Jorge, I should have something for you late Monday, if not sooner. -bn | |||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6602 Registered: 10-2002 |
Jorge, Here's a sooner than expected follow-up. There is an update patch for NowSMS 2006 that is currently available for download at http://www.nowsms.com/download/20060928.zip. This update includes support for a setting under the [SMPP - server:port] section of SMSGW.INI. Put TruncateText=### under this section header, and text messages will be truncated at ### bytes. -bn | |||
Jorge L Soto P New member Username: Jsoto Post Number: 5 Registered: 09-2006 |
Bryce, It's not working.I place under my two outgoing SMPP ports TruncateText=###. Example: TruncateText=145 Test at 150 characters, the SMPP still send 150 characters. TruncateText=100 Test at 150 characters, the SMPP still send 150 characters. TruncateText=70 Test at 150 characters, the SMPP still send 150 characters. | |||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6606 Registered: 10-2002 |
Jorge, Hmm ... what other settings do you have under the [SMPP - server:port] section header. I'm wondering if another setting might conflict. Do you have the SMSC character set configured for ISO-8859-1/Latin by any chance? It looks like the truncation logic that we inserted will not work if the SMSC is configured for that character set. On a hunch that this is the issue, I'm going to update the same URL as above with an updated SMSSMPP.DLL. If that doesn't resolve the issue, then let me know what other configuration options are listed in your [SMPP - server:port] section. -bn | |||
Jorge L Soto P New member Username: Jsoto Post Number: 6 Registered: 09-2006 |
Bryce, Yes, both of my SMPP outgoing ports are configured ISO-8859-1/Latin. Here is my port configuration: [SMPP - 172.17.80.10:3705] SMPPVersion=v3.4 UserName=xxxx Password=**** SenderAddressOverride=Yes Receive=Yes ReceiveMMS=No UseSSL=No LongSMSAlt=Yes ReceiveSingleConnection=Yes RoutePrefOnly=Yes SMSCCharset=iso-8859-1 | |||
Jorge L Soto P New member Username: Jsoto Post Number: 7 Registered: 09-2006 |
Bryce Did you post the new SMSSMPP.DLL file??? | |||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6616 Registered: 10-2002 |
Yes, it was posted to the same URL as mentioned above. Sorry if that was not clear! |