| MM4 routing |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through December 19, 2005 ⬆ |
◄ ► |
| Author | Message | |||
| Gaby Unregistered guest |
How can I route an MMS received from MMSC-A to MMSC-B? Is there any API to an external application for address resolution? Thanks! | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4680 Registered: 10-2002 |
Hi Gaby, Yes, in v5.51 or later, this is possible. Here is the explanation of how this works from the readme for v5.51: * Added HTTP-based routing callback for dynamic routing of MMS messages. When the MMSC receives a message, it will connect to a configurable customer-provided URL, passing the message recipient to the URL. The customer provided URL can return a response to indicate that the message should be routed via a specific route defined in the "MMSC Routing" page of the NowSMS configuration dialog. The MMS routing callback URL is defined in the MMSC.INI file, under the [MMSC] section header: MMSRoutingURL=http://server.name/path The variables listed below will be added to the MMSRoutingURL when the URL is executed by the gateway as HTTP GET (CGI-style) parameters. Type=MMSRouteCheck (Note: Future "Type" values may be added in the future.) From=SenderPhoneNumber or e-mail address VASPIN=VASPname (present if the message was received via a specific account defined in the "MMSC VASP" list) To=RecipientPhoneNumber Example: http://server.name/path?Type=MMSRouteCheck&From=%2B1234567&VASPIN=test&To=%2B999 9999999 (Note: The "%2B" in the above examples is URL escaping for the "+" character.) 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"). If it is possible to route the message via one of several defined routes, multiple routes can be returned in the response, separated by ":". For example: Route=xxxxxxx:yyyyyy:zzzzzz In this case, the message could be routed through any of the listed routes. | |||
