Hi all, When sending long messages using native Kannel concatenation functionality based on UDH, we are experiencing problems with matching delivery receipts of the submitted messages.
The problem arises from the fact that not all carries send back all delivery receipts. Some send only one receipt and it's not not necessarily #1. Basically there are 3 scenarios: 1) Carrier/Provider #1 sends back 1 delivery receipt and message_id correspondents to segment #1. Bearer_box matches by message_id, and forwards 1 delivery receipt to sms_box. This is the most desirable path. 2) Carrier/Provider #2 sends back 1 delivery receipt and message_id correspondents to last segment. Bearer_box cannot match by message_id, and does NOT forward a delivery receipt to sms_box at all. Delivery receipt is lost. 3) Carrier/Provider #3 sends back all delivery receipts for each segment. The order is random, lat say 5-segment message migh come back as 3,5,1,4,2. Bearer_box cannot match 3,5, matches 1 , cannot match 4,2 . It forwards only a delivery receipt for segment # 1 to sms_box. The other 2,3,4,5 would stay in dlr-storage and eventually expire. This scenario is not prefect, but acceptable. Question: Can we tell Kannel to save all submit_sm_resp message_id to dlr-storage? Is there any kind of kannel config switch to accommodate this? Do we have to patch and recompile bearer_box ourselves? Thanks and best Regards, Lelik.
