Sending DLR in case multiple clients binded
See original GitHub issueHello,
How to make sure that DLR is sent to client with whom it belongs to? Normally when DLR received here is how i am sending it back to client.
session.on('pdu', function(pdu){ if(pdu.command === 'deliver_sm'){ session.send(new smpp.PDU('deliver_sm', { esm_class: 4, short_message: pdu.short_message.message, source_addr: pdu.source_addr, destination_addr: pdu.destination_addr, receipted_message_id: client.id })); } })
Thanks,
Issue Analytics
- State:
- Created 3 years ago
- Comments:7
Top Results From Across the Web
Deploying Device Level Ring within a Converged Plantwide ...
DLR application use case for single Industrial Ethernet Switch (IES) ring ... The DHCP snooping binding table contains data such as the client...
Read more >SMS channels/SMS POI - Alaris Labs
In case the client sends bind requests with a different system type, the SMS switch will reject them. Service type is used in...
Read more >Can a Lawyer Bind a Client to a Settlement Agreement ...
As strange as it may sound the answer is yes. Lawyers are client's agents and as such their actions can bind their clients....
Read more >Attorneys Must Manifest Express Authority in Order to Create a ...
an attorney may enter into a binding settlement agreement on behalf of his client only if the attorney is acting with express au-...
Read more >DLR Routing failure in Kannel in a situation where there is a ...
It seems that Kannel saves the DLR immediately after the submit_sm with the smsc_id set to the tx_bind [ the sender's SMSC id...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
In the end I would not try to look too hard on the session id, because your client could close the connection and reconnect back, in that case the session id would change and you wouldn’t be able to send the DLR back to him
What I’d do instead is
I don’t recommend you to blindly proxy submit_sm and deliver_sm, but develop your solution in the mmiddle to handle communication from/to your client and to/from your provider
Closing as it feels like the issue is resolved