Also, EVEN with dlr-mask = 15 I get delivery messages type = 16. Is it
expected and correct too?
Steps to reproduce:
1. Stop smsc (using web-interface)
2. Try to send message through that stopped smsc
3. Look at logs: "GET
/delivery.php?id=20110525131717363839&provider_id=3&type=16&message_id=
HT
Nope. When THERE IS NO active SMSC connected - kannel ALSO sends type 16.
Is it possible to get somehow in dlr-url information either dlr type 16 came
from SMSC itself or generated by kannel (because of no active SMSC)?
On Wed, May 25, 2011 at 12:55 PM, Rene Kluwen wrote:
> Rejected is an smsc
Rejected is an smsc issue in both cases.
Kannel just obeys what your smsc says.
- Oorspronkelijk bericht -
Van: Ivan Kurnosov
Verzonden: woensdag 25 mei 2011 3:39
Aan: Rene Kluwen
CC: Nikos Balkanas ; us...@vm1.kannel.org
Onderwerp: Re: Stopping reconnecting after unbing
So you think th
So you think that type: 16 does it work fine? I cannot determine if it was
kannel issue or smsc issue. In both cases I get "REJECTED" and I have no
idea why it is rejected.
Am I missing something?
On Wed, May 25, 2011 at 12:36 PM, Rene Kluwen wrote:
> I think your smsc is "incorrect" rather tha
I think your smsc is "incorrect" rather than Kannel.
Issue a support ticket with them, because Kannel does the right thing (tm).
- Oorspronkelijk bericht -
Van: Ivan Kurnosov
Verzonden: woensdag 25 mei 2011 2:53
Aan: Nikos Balkanas
CC: us...@vm1.kannel.org
Onderwerp: Re: Stopping recon
So, looking at the sources and documentation I've come to the fact that in
such cases I'm not able to determine whether type: 16 was caused by real
reject by SMSC or by kannel itself.
Any ideas of how could I determine it in my dlr scripts?
After today's morning accident I've got 20 messages that
Also the weird thing is that after SMSC has been disconnected - all messages
that have been tried to sent through that broken kannel instance was marked
as "16: smsc reject". In this case I'm not able to get in my program side
whether it was rejected by my SMSC or by broken kannel. I think it is
ab
But this is still an issue for me. What if that happened in the night - then
until I came to work it wouldn't send messages :-(
if (pdu->u.bind_transceiver_resp.command_status ==
SMPP_ESME_RINVSYSID ||
pdu->u.bind_transceiver_resp.command_status ==
SMPP_ESME_RIN
Hi,
The SMSc error you got was one of invalid username. I don't know why your
SMSc returned this error, since you can obviously connect fine, but since
this is a terminal error that cannot be corrected by itself, there is no
sense in reconnecting. Of course you don't need to restart kannel, yo
Hi there.
Just some minutes ago something strange has happened that I cannot explain:
2011-05-25 10:17:51 [11434] [6] DEBUG: SMPP[sv]: Got PDU:
2011-05-25 10:17:51 [11434] [6] DEBUG: SMPP PDU 24d080 dump:
2011-05-25 10:17:51 [11434] [6] DEBUG: type_name: unbind
2011-05-25 10:17:51 [11434] [6] D
10 matches
Mail list logo
