Easier way to manager delivery receipts - missing receipted_message_id and PDU Sequence Management

[alexanderomnix]

Thanks for the great work, is almost impossible to find content about SMPP implementations for the go language and other languages as well, in go, we can rely only in this and the linxGnu lib, I'm studying and even looking to contribute after understanding the implementation.

I have a feature request tho, about the Delivery receipt (DeliverSM), using the melroselabs SMSC simulator on python or java client I'm receiving the receipted_message_id as it's stated on the smpp 3.4 specifications but with go-smpp is not implemented, I even thought it would be the MessageID Field but it always returns empty, is this field missing or is that a way to capture it?
Another problem is to Manage the sequence between submitSM and DeliverSM, to correlate the ID some implementations leave the atomic integer id implementation to the developer, which usually using a message broker or a database is possible to control those sequences and correlate Receipts with the send Message is that a way that we can implement those features?

[tahseenjamal]

@alexanderomnix I am using this library and I receive message id on submission and also delivery receipts.

In this smpp library you get source, destination, message_id, text

So you don't have to co-relate. Share how you have written your code to point out the mistake