Re: SMPP message ID greater than 9223372036854775807 breaking DLRs

--000000000000d854a10602f8737c
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

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=E2=80=AFPM Alex Kinch <[email protected]> wr=
ote:
>
>> Hi all,
>>
>> I've run into an issue with a certain SMS provider (Nexmo/Vonage) that i=
s
>> 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=3D0x01 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]://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] **
>
>

--000000000000d854a10602f8737c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Kyriacos<div><br></div><div>The MySQL field type was va=
rchar(100) so that wasn&#39;t the problem. In the end we fixed it by asking=
 Nexmo/Vonage to change the message ID types to match (hex) and then remove=
d msg-id-type so the conversion was no longer needed.</div><div><br></div><=
div>Thanks</div><div>Alex</div></div><br><div class=3D"gmail_quote"><div di=
r=3D"ltr" class=3D"gmail_attr">On Mon, 7 Aug 2023 at 01:04, Kyriacos/Netsma=
rt &lt;<a href=3D"mailto:[email protected]">[email protected]=
</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:=
0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
 =20
   =20
 =20
  <div>
    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&#39;t have extreme spac=
e
    limit issues on the DB side.<br>
    <br>
    <div>On 06/08/2023 6:16 pm, Mesbahuddin
      Malik wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div dir=3D"ltr">Send your Smpp Config.</div>
      <br>
      <div class=3D"gmail_quote">
        <div dir=3D"ltr" class=3D"gmail_attr">On Sun, Aug 6, 2023 at 8:26=
=E2=80=AFPM
          Alex Kinch &lt;<a href=3D"mailto:[email protected]" target=3D"_b=
lank">[email protected]</a>&gt;
          wrote:<br>
        </div>
        <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex=
;border-left:1px solid rgb(204,204,204);padding-left:1ex">
          <div dir=3D"ltr">Hi all,
            <div><br>
            </div>
            <div>I&#39;ve run into an issue with a certain SMS provider
              (Nexmo/Vonage) that is using message IDs greater
              than=C2=A09223372036854775807 (e.g.
              6142530091694509440651642911224527237), which is in turn
              breaking DLR processing in Kannel.=C2=A0</div>
            <div><br>
            </div>
            <div>They use hex in submit_sm_resp and decimal in
              deliver_sm so I have to have=C2=A0<span style=3D"font-family:=
monospace">msg-id-type=3D0x01=C2=A0</span>set,
              so it&#39;s not like I can remove it and have Kannel use a C
              literal instead.=C2=A0</div>
            <div><br>
            </div>
            <div>I&#39;ve just tried the latest daily build and have the
              same issue. Using MySQL for DLR storage if that&#39;s
              relevant.</div>
            <div><br>
            </div>
            <div>Any help appreciated!</div>
            <div><br>
            </div>
            <div>Thanks</div>
            <div>Alex=C2=A0</div>
          </div>
        </blockquote>
      </div>
    </blockquote>
    <br>
    <pre cols=3D"72">--=20
Kyriacos Sakkas
Netsmart
Tel: + 357 22 452565
Fax: + 357 22 452566
Email: <a href=3D"mailto:[email protected]" target=3D"_blank">kyriac=
[email protected]</a>
<a href=3D"http://www.netsmart.com.cy" target=3D"_blank">http://www.netsmar=
t.com.cy</a>

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 <a href=3D"mailto:[email protected]" target=3D"_b=
lank">[email protected]</a> **</pre>
  </div>

</blockquote></div>

--000000000000d854a10602f8737c--