SMPP message ID greater than 9223372036854775807 breaking DLRs

2023-08-03 Thread Alex Kinch
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

Re: SMPP message ID greater than 9223372036854775807 breaking DLRs

2023-08-06 Thread Mesbahuddin Malik
Send your Smpp Config. On Sun, Aug 6, 2023 at 8:26 PM Alex Kinch 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 > pro

Re: SMPP message ID greater than 9223372036854775807 breaking DLRs

2023-08-06 Thread Kyriacos/Netsmart
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

Re: SMPP message ID greater than 9223372036854775807 breaking DLRs

2023-08-15 Thread Alex Kinch
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/Netsmar