Hi
In the case of SMPP delivery reports from SS7_SMSC, the ESME account is selected based on number range. This brings up 2 issues when you have multiple ESME accounts.
1-- To route SMS to SS7 from SMPP, I have to set every SMPP account with a fake routing range so that SMS doesn't get routed between SMPP and fall to SS7. Hence I set all ESME routing range to 6666.
2-- In the case where routing range is setup as a fixed number in ESME, the DLRs from SS7 can't reach any of SMPP accounts as they have real numbers.
Hence, I am stuck in the situation where I can send SMS to SS7 and have no DLRs routed back.
Moreover, it is usually preferred to have DLR on same ESME account which received SUBMIT_SM.
I have looked into the code and I can see that during routing originalEsmeAccount is checked and if it exists the SMS is routed to that cluster. This doesn't happen for DLRs as during createReceipt part the originalESME account is not copied to Sms object and hence number routing is the only way SMSGateway can route that DLR.
Can someone tell me if I am missing something? May be I can use a message processing rule?
I can also easily patch code as with 1 line and fix this to send DLR back to originating ESME.
Thanks