| Direct route on NextGen is invalid route |  Search
|
|
NowSMS Support Forums ⬆ NowSMS NextGen Support ⬆ |
◄ ► |
| Author | Message | |||
| Jürgen Pulles New member Username: Jyrgen Post Number: 1 Registered: 01-2022 |
Hello In ini file settings documentation following is said: https://nowsms.com/doc/advanced-configuration-settings/ini-file-settings To specify which of the routes defined in the “MMSC Routing” list should be used to route this message, the URL must return a standard HTTP 200 OK response, and include the following text somewhere in the response: Route=xxxxxxx “xxxxxxx” should match an “Account Name” defined in the “MMSC Routing” list, or it can use the predefined values of “Direct” (signifying MMSC Direct Delivery) or “WAPPush” (signifying “Convert to Multimedia WAP Push”). But somehow it is not working, this is from SMSDEBUG.LOG: 14:09:08:824 [139899622606592] m=227,0 RetrieveURL: HTTP/1.1 200 OK Date: Mon, 10 Jan 2022 12:09:08 GMT Vary: Accept-Encoding, User-Agent Content-Length: 14 Server: Jetty(9.4.0.v20161208) Route=Direct 14:09:08:824 [139899622606592] m=227,0 RetrieveURL: Saving keep-alive socket 14:09:08:824 [139899622606592] m=227,0 RetrieveURL: got success response 14:09:08:824 [139899622606592] m=227,0 RetrieveURL: 14:09:08:824 [139899622606592] m=227,0 RetrieveURL: OK 14:09:08:824 [139899622606592] m=227,0 MMSRoutingCallback: HTTP/1.1 200 OK Date: Mon, 10 Jan 2022 12:09:08 GMT Vary: Accept-Encoding, User-Agent Content-Length: 14 Server: Jetty(9.4.0.v20161208) Route=Direct 14:09:08:824 [139899622606592] m=227,0 MMSRoutingCallback: Got route from callback 14:09:08:824 [139899622606592] m=227,0 MMSRoutingCallback: Direct 14:09:08:824 [139899622606592] m=227,0 InvalidMMSRoute: Direct 14:09:08:824 [139899622606592] m=227,0 MMSRoutingCallback: Invalid route All other routes that have been added in VASP OUT are working as intended when their route name is given back by MMS router. Version in use is: NowSMS NextGen Version 2021.10.20 Default Route is Direct Delivery (internal MMSC). Is there some VASP missing that needs to be added? Kind regards, Jürgen | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 8467 Registered: 10-2002 |
Hi Jürgen, I can confirm that this was a bug that crept into a recent release. We added a validation on the MMSC route returned by a routing callback, because this was resulting in messages getting stuck in the queue. However, this validation did not allow "Direct" as a response. The current version (2021.12.14) definitely does not have this bug. If your.server is able to connect to the internet, go to the Admin/System Configuration page in the web interface, and an "Upgrade" button should be displayed near the top of the page. Alternatively, download the latest version manually (see links here https://nowsms.com/techsupport/nextgen-install), extract and run NowSMSInstall, which will provide an option to update. Regards, Bryce Norwood NowSMS Support | |||
| Jürgen Pulles New member Username: Jyrgen Post Number: 2 Registered: 01-2022 |
Hello Bryce, I got MMSC updated and this bug is now fixed. It does say that the route is invalid, but continues with sending MMS. 11:26:55:283 [140454941165312] m=248,0 RetrieveURL: Saving keep-alive socket 11:26:55:283 [140454941165312] m=248,0 RetrieveURL: got success response 11:26:55:283 [140454941165312] m=248,0 RetrieveURL: 11:26:55:283 [140454941165312] m=248,0 RetrieveURL: OK 11:26:55:283 [140454941165312] m=248,0 MMSRoutingCallback: HTTP/1.1 200 OK Date: Wed, 12 Jan 2022 09:26:55 GMT Vary: Accept-Encoding, User-Agent Content-Length: 14 Server: Jetty(9.4.0.v20161208) Route=Direct 11:26:55:283 [140454941165312] m=248,0 MMSRoutingCallback: Got route from callback 11:26:55:283 [140454941165312] m=248,0 MMSRoutingCallback: Direct 11:26:55:283 [140454941165312] m=248,0 InvalidMMSRoute: Direct 11:26:55:283 [140454941165312] m=248,0 MMSRoutingCallback: Checking user database 11:26:55:283 [140454941165312] m=248,0 MMSRoutingCallback: +XXXX/TYPE=PLMN 11:26:55:284 [140454941165312] m=248,0 MMSRoutingCallback: User is provisioned 11:26:55:284 [140454941165312] m=248,0 MMSRoutingCallback: +XXXX/TYPE=PLMN | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 8470 Registered: 10-2002 |
Hi Jürgen, Thanks for sharing that observation. I asked our engineering team to review why "InvalidMMSRoute: Direct" appears in the debug log, and to verify that this isn't a potential cause for concern. They assure me that it is just a debug log reference that occurs because "Direct" is only a valid route name in the context of the routing callback. The underlying logic is sound, but the additional logic that processes the "Route=Direct" response does not write any information to the debug log. Regards, Bryce Norwood NowSMS Support | |||
