| MMSC Routing of Additiona Routes when using ForceRoutingCallback |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ |
◄ ► |
| Author | Message | |||
| Robert Barretto Frequent Contributor Username: Barretto Post Number: 74 Registered: 09-2019 |
Hi all, In my normal configuration of the MMSC, I use ForceRoutingCallback=Yes in combination with a MMSRoutingURL=https://w.x.y.z/some_route_script to select the outgoing MM4 route. My default route is Direct Delivery (internal MMSC). All of that works like a champ. Is it possible to add an additional MMSC VASP route, say test-mm4-route, that uses a specific MSISDN in the Route message to this account for recipient phone number(s) field to select a different route than what would normally come back from the MMSRoutingURL? For example, I have a one off number to test a potential new MM4 interconnect. This number is not provisioned in our core so the MMSRoutingURL script doesn't know anything about the new number or the new route. If the e.164 recipient number is defined in an Additional Route definition, would that override the MMSRoutingURL because it's an exact match, or since I have ForceRoutingCallback and the MMSRoutingURL defined, the route can never be selected, unless the MMSRoutingURL returns it? I don't have the number nor the MM4 interconnect to test yet, but I wanted to see if that's possible before I try to go down that route, no pun intended. 😆 Cheers, //Robert | |||
| Robert Barretto Frequent Contributor Username: Barretto Post Number: 76 Registered: 09-2019 |
* "Additional Routes" not "Additona Routes". Sorry, didn't catch that before I posted. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 8609 Registered: 10-2002 |
Hi Robert, In the scenario that you describe, you would need to modify the routing script to return this route for the test number. Regards, Bryce | |||
| Robert Barretto Frequent Contributor Username: Barretto Post Number: 77 Registered: 09-2019 |
Hi Bryce, Cool. That's what I was thinking, but I wanted to confirm with y'all first. Since I can't alter the current VAS servicing the MMSRoutingURL, what I'll do is add an openresty proxy to front my current MMSRoutingURL and SMSAccountingURL addresses. I can use Lua to do the logic to select a special route for my test number, otherwise just forward the request on to the real VAS URL. Thanks! //Robert | |||
