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. 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.) Related issue : https://issues.apache.org/jira/browse/CAMEL-6116 - The same customer's SMSC, did not accept any service_type. It just wanted it to be empty. Otherwise I was getting "invalid service type" error. I just commented out the default "CMT" service type value and worked like a charm. If I wanted to set it, I could do it in the uri or the exchange's header. But I wasn't able to put empty in any of those ways. Related issue : https://issues.apache.org/jira/browse/CAMEL-6117 I is the first time I tried to post and create an issue, so I do not know if I did everything right (I don't know if the priority was correct, and I just left the default. Also, because of the simplicity of the change I did not create any tests for it ) -- View this message in context: http://camel.465427.n5.nabble.com/camel-smpp-improvements-show-optional-parameters-of-delivery-receipt-and-allow-empty-serviceType-tp5728360.html Sent from the Camel Development mailing list archive at Nabble.com.
