Possible bug in splitting messages?

"Arne K. Haaje" <[email protected]>
Newsgroups gmane.comp.mobile.kannel.devel
Organization Eurobate ASA
Message-ID <[email protected]>
When sending a Nokia ringtone through the /cgi-bin/sendsms interface it is 
treated correctly, but when fetched with a service it look like it is treated 
as a text message - even though there is an UDH present.

Take a look at this log extraxt;

Fetched with a service;
2003-09-04 16:01:29 Sent SMS [SMSC:T2_72320] [SVC:default] [ACT:] [from:72320] 
[to:46736402830] [flags:1:0:-1:-1:-1] 
[msg:146:024A3A5D35254D4D253D38041E7F18A2742942742942742942742942742742942B42D42F431431020C31020C37021023021031020C31020C2D02102F021031020C31020C3702102302] 
[udh:12:0B0504158100000003130201]
2003-09-04 16:01:58 Sent SMS [SMSC:T2_72320] [SVC:default] [ACT:] [from:72320] 
[to:46736402830] [flags:1:0:-1:-1:-1] 
[msg:72:1031020C31020C2D02102F02103703102642143703102442143703102242103702300000] 
[udh:12:0B0504158100000003130202]

Sent through the HTTP interface. Don't mind the FAILED status, it is cased by 
not using the correct sender.
2003-09-04 16:06:00 FAILED Send SMS [SMSC:T2_72320] [SVC:eurobate] [ACT:] 
[from:150] [to:736402830] [flags:-1:1:-1:-1:-1] 
[msg:109:024A3A5D35254D4D253D38041E7F18A2742942742942742942742942742742942B42D42F431431020C31020C37021023021031020C31020C2D02102F021031020C31020C37021023021031020C31020C2D02102F02103703102642143703102442143703102242103702300000] 
[udh:7:06050415810000]

When fetching with the service I use the X-Kannel-UDH header.

Any ideas? Is this a bug, or have I forgot something when using a service?
-- 
Med vennlig hilsen,
Eurobate ASA

Arne K. Haaje
Senior Network Engineer
--------------------------------------------------------------------
    Eurobate ASA - Postboks 4589 Nydalen - 0404 Oslo - Norway
Phone: +47 23 22 73 73 - Fax: +47 23 22 73 74 - Mob: +47 92 88 44 66
                    http://www.eurobate.com/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.