| US DNO blocked route |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ |
◄ ► |
| Author | Message | |||
| Chris Henn New member Username: Chrishenn Post Number: 10 Registered: 09-2017 |
I see how I can create a block route with a specific number list. I have a few questions about that method. 1: What is the DLR response that would be sent back to the source (undeliverable would make the most sense)? 2: If we just want to build the outbound route and have our routing engine response with that route name will it work (without any numbers in the "Outbound Routing Prefix List"? Original Article I'm working from: https://nowsms.com/doc/mmsc-messaging-server/connecting-to-an-operator-mmsc/sending-mms-messages/blockreject-message | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 8540 Registered: 10-2002 |
Hi, Your assumption in #2 is correct. As to the response, whether or not the sender receives a DLR depends. NowSMS will refuse to accept the message at the transport protocol layer. For example, if messages are being posted via MM4 or SMTP, the “RCPT TO” command response will be “550 Recipient Unknown” Regards, Bryce Norwood NowSMS Support | |||
| Chris Henn New member Username: Chrishenn Post Number: 13 Registered: 09-2017 |
Bryce, There were a few things I found with creating a MMS Connection configured as "Blocked Route" You can not have your http callback route populated with the blocked route's name ex: MMS Route named DNO with the configuration of a BLOCKED ROUTE. It will just see there isn't a matching route to the route callback and never wrote a message log and queued the message. The solution was to create an MM4 Route named DNO with an address of 127.0.0.1 and fake credentials that would fail to authenticate and mark the message as failed with the DNO route name. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 8541 Registered: 10-2002 |
Chris, Are you running on Linux or Windows? I recall a report where the callback response only worked properly if it used the hard coded name, Route=BlockMessage. Regards, Bryce | |||
| Chris Henn New member Username: Chrishenn Post Number: 14 Registered: 09-2017 |
This is experienced on Linux, we want the route name to be specific DNO for reporting and knowing the difference in this and unallocated numbers. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 8542 Registered: 10-2002 |
What version are you running? I'm trying to recreate the problem, but not having any luck yet. | |||
| Chris Henn New member Username: Chrishenn Post Number: 15 Registered: 09-2017 |
NowSMS NextGen Version 2023.12.07 | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 8543 Registered: 10-2002 |
Chris, What protocol are you using to submit messages? I'm assuming MM4/SMTP? I'm still not able to recreate the problem with version 2023.12.07. I do agree that it is not logged (which is an oversight, as it should be), but messages are not accepted or queued when the routing callback returns Route=DNO and DNO is a blocked/reject route. Regards, Bryce | |||
| Chris Henn New member Username: Chrishenn Post Number: 16 Registered: 09-2017 |
Bryce, That is correct, it is coming in MM4 and when the route callback returns Route=DNO and DNO is built as a blocked/reject route the logs show no matching route found. | |||
