[CAMEL-6116] Populate all optional parameters from DeliverSm (if it is DeliveryReceipt)

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.9.7, 2.10.5, 2.11.0
• Component/s: camel-smpp
• Labels: optional parameters
• Patch Info: Patch Available
• Estimated Complexity: Unknown
• Assignee: Christian Müller
• Reporter: Ioannis Alexandrakis
• Created: 01/Mar/13 15:15
• Updated: 08/Mar/13 04:33
• Resolved: 08/Mar/13 04:33

Description

Hello all,

I am currently working on a project requiring the use of camel-smpp. I stumbled upon some problems integrating with the customer's SMSC, and I modified the code of camel-smpp in order to fit my needs (just adding some functionality though, not removing any).

More specifically, for submitting a new message, the delivery receipt held the corresponding submit_sm id in the optional parameters (as receipted_message_id). With the current trunk code, I did not get the optional parameters of the delivery receipt, so I could not match the delivery receipt to the outgoing sms. As a solution I just looped all the optional parameters and put them into a map as a header (and instead of checking each optional parameter name, I just put whatever jsmpp was sending back, so if someone wants to put other optional parameters to jsmpp too, they would simply automatically be populated back in camel-smpp.)

Please find the patch attached