Hello All, Very thanks, i set allowed-smsc (with SMSC parameters) and smsc in push url. And it's ok. Very thanks Guys.
Best Regards. On Mon, Aug 26, 2019 at 7:10 PM Edjé DOSSEH <edos...@gmail.com> wrote: > Hello Ahmed, Davor, > > Very thanks. Tomorrow i'll work on the servers and revert back to you. > > Best regards. > > On Mon, Aug 26, 2019 at 7:02 AM Ahmed Shabana <a.shab...@cequens.com> > wrote: > >> Check allowed-smsc and preferred-smsc parameters >> >> >> >> >> >> >> Best regards , >> >> Ahmed Shabana >> >> +20 1003325373 >> >> >> >> *From:* devel <devel-boun...@kannel.org> *On Behalf Of *Edjé DOSSEH >> *Sent:* Monday, August 26, 2019 6:59 AM >> *To:* devel@kannel.org >> *Subject:* Routing problem with bearerbox (kannel svn 5280) >> >> >> >> 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. >> >
