RE: Bug in sms_split() ?

The behaviour you describe is a know bug and it was fixed recently (I
think two or three weeks ago). are you uptodate on the CVS ?

--
Oded Arbel
m-Wise Inc.
[email protected]

[..]
A 16-head Cray C90 with some reasonable amount of disk costs $40M
For $40M, you could buy 4000 workstations and have enough left over to
buy a really cool switch with which to hook them together.

So what would you rather have pulling your wagon, 16 oxen or 4000
chickens
with a frictionless harness?
[..]
	-- Larry Meadows		The Portland Group


> -----Original Message-----
> From: Paul Keogh [mailto:[email protected]]
> Sent: Thursday, March 07, 2002 5:11 PM
> To: Kannel Development List (E-mail)
> Subject: Bug in sms_split() ?
> 
> 
> 
> I've a problem when I send a 160 character message (7BIT coding)
> to an M20 - the M20 fails with a CMS 304 because the 
> charset_latin1_to_gsm()
> function *increases* the size of the message to 163 characters due to
> GSM code escaping.
> 
> I think sms_split() should figure this in for the SMS box. If 
> you insert the
> lines;
> 
>     list = list_create();
> +
> +	if (octstr_len (temp->sms.msgdata) > max_part_len)
> +		max_part_len = max_part_len - (sms_msgdata_len (temp) -
> +			octstr_len (temp->sms.msgdata));
> +
>     do {
> 
> you adjust max_part_len accordingly. This is quite coarse as 
> ideally you'd
> figure out which part-> contains characters to be expanded 
> and only reduce
> its
> max_part_len rather than reduce all part->'s.
> 
> Comments ?
> 
> Paul Keogh
> ANAM Wireless Internet Solutions
> http://www.anam.com
> +353 1 284 7555 (wired)               +353 86 234 6047 (wireless)
> Castle Yard, Saint Patrick's Road, Dalkey, County Dublin, Ireland
> 
> 
> 
>