Routing problem with bearerbox (kannel svn 5280)

Edjé DOSSEH <[email protected]> Mon, 26 Aug 2019 04:58:51 +0000
Newsgroups gmane.comp.mobile.kannel.devel
Message-ID <CADmTjxr_QT5e1wzGd39iEnMYZ3d7cFmTiRTPyQOHQbQfsORNpw@mail.gmail.com>
--000000000000d651960590fe03cc
Content-Type: text/plain; charset="UTF-8"

Dear All,

  I'm facing with a problem on bearerbox. I installed kannel with
opensmppbox  (SVN 5285) on a centos 7 server. I set 2 SMSCs according with
Mobile operators links (Operators A and B). But we notice for push SMS
that, when messages are sent to Operator A, it can be routed to Operator B
SMSC (who doesn't accept it) so transmission is failed. I receive this
error:

2019-08-23 16:37:29 [41172] [6] DEBUG: SMPP PDU 0x7f36b4000a00 dump:
2019-08-23 16:37:29 [41172] [6] DEBUG:   type_name: submit_sm_resp
2019-08-23 16:37:29 [41172] [6] DEBUG:   command_id: 2147483652 = 0x80000004
2019-08-23 16:37:29 [41172] [6] DEBUG:   command_status: 11 = 0x0000000b
2019-08-23 16:37:29 [41172] [6] DEBUG:   sequence_number: 27 = 0x0000001b
2019-08-23 16:37:29 [41172] [6] DEBUG:   message_id: "25D512F6"
2019-08-23 16:37:29 [41172] [6] DEBUG: SMPP PDU dump ends.
2019-08-23 16:37:29 [41172] [6] ERROR: SMPP[OPERATOR B]: SMSC returned
error code 0x0000000b (Invalid Destination Address) in response to
submit_sm PDU.

In kannel config, i use *forced-smsc* for *sendsms-user *configuration.
And the URLs used for sending are set in a script according to the
destination address.

Please is it a well-known problem or due to a missed
compilation/installation or missed configuration? I notice that on stable
version (installed by rpm), i had'nt this problem.

Very thanks for your help in advance.

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

<div dir=3D"ltr">Dear All,<div><br></div><div>=C2=A0 I&#39;m facing with a =
problem on bearerbox. I installed kannel with opensmppbox=C2=A0 (SVN=C2=A05=
285) on a centos 7 server. I set 2 SMSCs according with Mobile operators li=
nks (Operators A and B). But we notice for push SMS that, when messages are=
 sent to Operator A, it can be routed to Operator B SMSC (who doesn&#39;t a=
ccept it) so transmission is failed. I receive this error:</div><div><br></=
div><div>2019-08-23 16:37:29 [41172] [6] DEBUG: SMPP PDU 0x7f36b4000a00 dum=
p:<br>2019-08-23 16:37:29 [41172] [6] DEBUG: =C2=A0 type_name: submit_sm_re=
sp<br>2019-08-23 16:37:29 [41172] [6] DEBUG: =C2=A0 command_id: 2147483652 =
=3D 0x80000004<br>2019-08-23 16:37:29 [41172] [6] DEBUG: =C2=A0 command_sta=
tus: 11 =3D 0x0000000b<br>2019-08-23 16:37:29 [41172] [6] DEBUG: =C2=A0 seq=
uence_number: 27 =3D 0x0000001b<br>2019-08-23 16:37:29 [41172] [6] DEBUG: =
=C2=A0 message_id: &quot;25D512F6&quot;<br>2019-08-23 16:37:29 [41172] [6] =
DEBUG: SMPP PDU dump ends.<br>2019-08-23 16:37:29 [41172] [6] ERROR: SMPP[O=
PERATOR B]: SMSC returned error code 0x0000000b (Invalid Destination Addres=
s) in response to submit_sm PDU.<br></div><div><br></div><div>In kannel con=
fig, i use <b>forced-smsc</b> for <b>sendsms-user </b>configuration.</div><=
div>And the URLs used for sending are set in a script according to the dest=
ination address.</div><div><br></div><div>Please is it a well-known problem=
 or due to a missed compilation/installation or missed configuration? I not=
ice that on stable version (installed by rpm), i had&#39;nt this problem.</=
div><div><br></div><div>Very thanks for your help in advance.</div></div>

--000000000000d651960590fe03cc--