Hi Kyriacos The MySQL field type was varchar(100) so that wasn't the problem. In the end we fixed it by asking Nexmo/Vonage to change the message ID types to match (hex) and then removed msg-id-type so the conversion was no longer needed.
Thanks Alex On Mon, 7 Aug 2023 at 01:04, Kyriacos/Netsmart <[email protected]> wrote: > And your mysql table create statement. It might be that you are using a > filed type that can not hold such large numbers. Can easily be converted to > a char based storage if you don't have extreme space limit issues on the DB > side. > > On 06/08/2023 6:16 pm, Mesbahuddin Malik wrote: > > Send your Smpp Config. > > On Sun, Aug 6, 2023 at 8:26 PM Alex Kinch <[email protected]> wrote: > >> Hi all, >> >> I've run into an issue with a certain SMS provider (Nexmo/Vonage) that is >> using message IDs greater than 9223372036854775807 (e.g. >> 6142530091694509440651642911224527237), which is in turn breaking DLR >> processing in Kannel. >> >> They use hex in submit_sm_resp and decimal in deliver_sm so I have to >> have msg-id-type=0x01 set, so it's not like I can remove it and have >> Kannel use a C literal instead. >> >> I've just tried the latest daily build and have the same issue. Using >> MySQL for DLR storage if that's relevant. >> >> Any help appreciated! >> >> Thanks >> Alex >> > > -- > Kyriacos Sakkas > Netsmart > Tel: + 357 22 452565 > Fax: + 357 22 452566 > Email: [email protected]http://www.netsmart.com.cy > > Taking Business to a New Level! > > ** Confidentiality Notice: The information contained in this email > message may be privileged, confidential and protected from disclosure. > If you are not the intended recipient, any dissemination, distribution, > or copying of this email message is strictly prohibited. > If you think that you have received this email message in error, please > email the sender at [email protected] ** > >
