|
The handler gets called while the SMS is not received. client.set_message_received_handler(lambda pdu: handle_deliver_sm(pdu))
I printed some fields of the client.listen(auto_send_enquire_link=False)
...
client.send_message(
source_addr_ton=smpplib.consts.SMPP_TON_ALNUM,
source_addr_npi=smpplib.consts.SMPP_NPI_UNK,
source_addr=config.SOURCE_NAME,
dest_addr_ton=smpplib.consts.SMPP_TON_INTL,
dest_addr_npi=smpplib.consts.SMPP_NPI_ISDN,
destination_addr=phone_number,
short_message=part,
data_coding=encoding_flag,
esm_class=msg_type_flag,
registered_delivery=True,
)Am I missing sth? |
Replies: 1 comment 3 replies
|
👋 I'm afraid our example is a little incorrect:
|
|
I changed The |
|
This is odd, I'd ask the SMPP service provider about why this happens |
|
Turns out we have a SMSC with version 3 and the flag isn't supported until version 5. Second mistake was that the messages are actually older confirmations that haven't been processed. The SMSC seems to send those confirmations occasionally when not received yet. |
Turns out we have a SMSC with version 3 and the flag isn't supported until version 5.
Second mistake was that the messages are actually older confirmations that haven't been processed. The SMSC seems to send those confirmations occasionally when not received yet.