data_encoding calculate in latest CVS

Yury Mikhienko <[email protected]>
Newsgroups gmane.comp.mobile.kannel.devel
Organization Mobicom-Kavkaz
Message-ID <[email protected]>
In last CVS version of kannel data_coding field in PDU wrong calculating

For example, I set the following headers 
   if(!response.containsHeader("X-Kannel-Coding"))
   {
    response.addHeader("X-Kannel-Coding",new String("2"));
   }else
   {
    response.setHeader("X-Kannel-Coding",new String("2"));
   };


   if(!response.containsHeader("X-Kannel-MClass"))
   {
    response.addHeader("X-Kannel-MClass","1");
   }else
   {
    response.setHeader("X-Kannel-MClass","1");
   };

and get the wrong data_coding:

2003-09-11 13:45:44 [6] DEBUG:   esm_class: 3 = 0x00000003
2003-09-11 13:45:44 [6] DEBUG:   protocol_id: 0 = 0x00000000
2003-09-11 13:45:44 [6] DEBUG:   priority_flag: 0 = 0x00000000
2003-09-11 13:45:44 [6] DEBUG:   schedule_delivery_time: NULL
2003-09-11 13:45:44 [6] DEBUG:   validity_period: NULL
2003-09-11 13:45:44 [6] DEBUG:   registered_delivery: 0 = 0x00000000
2003-09-11 13:45:44 [6] DEBUG:   replace_if_present_flag: 0 = 0x00000000
2003-09-11 13:45:44 [6] DEBUG:   data_coding: 25 = 0x00000019 <--- WHY?

in previouse version of kannel I get data_coding properly:
2003-09-11 14:37:24 [6] DEBUG:   esm_class: 3 = 0x00000003
2003-09-11 14:37:24 [6] DEBUG:   protocol_id: 0 = 0x00000000
2003-09-11 14:37:24 [6] DEBUG:   priority_flag: 0 = 0x00000000
2003-09-11 14:37:24 [6] DEBUG:   schedule_delivery_time: NULL
2003-09-11 14:37:24 [6] DEBUG:   validity_period: NULL
2003-09-11 14:37:24 [6] DEBUG:   registered_delivery: 0 = 0x00000000
2003-09-11 14:37:24 [6] DEBUG:   replace_if_present_flag: 0 = 0x00000000
2003-09-11 14:37:24 [6] DEBUG:   data_coding: 20 = 0x00000014 <--- CORRECT
2003-09-11 14:37:24 [6] DEBUG:   sm_default_msg_id: 0 = 0x00000000

Where is error?

-- 
 
Best regards,
Yury Mikhienko.
IT engineer, ZAO "Mobicom-Kavkaz"
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.