About MMSC Routes,i add more MMSC Routes!

About MMSC Routes,i add more MMSC Routes! SearchSearch
Author Message
Anonymous
 
Posted on Thursday, September 29, 2005 - 09:46 am:   

In NOW SMS/MMS Gateway v5.51b.
If more than one MMSC ROUTES (GPRS modem) have been set in MMSC ROUTES, i want to know whether NowSMS can choose one of the routes when sending MMS????
thank....
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 5033
Registered: 10-2002
Posted on Tuesday, October 04, 2005 - 09:55 pm:   

The routing logic works similar to the SMS routing logic.

For each route, there is a "Route messages to this account for recipient phone number(s)" field.

This is similar to the "Preferred SMSC Connection for" list in the SMSC list. However, in the MMSC Routing list, it is a comma delimited list instead of a more formal list.

But it supports the same wildcards, where "*" represents 0 or more characters, and "?" represents exactly 1 character.

So, for example, "+44*" would represent all numbers that start with "+44". And you can have multiple entries by comma delimiting.

When NowSMS routes a message, if it sees that the message recipient matches an entry in one of these lists, it will only be routed outbound by one of the routes that has a matching entry in the list.

When NowSMS evaluates this list, it looks for the longest match. So, for example, "+447*" is longer than "+44*". If a message was being routed to "+4477777777", and there were three routes defined that included "+44*" in the list, and two routes that included "+447*" in the list, the message would only be routed outbound via one of the routes that had "+447*" in the list.

There is also the capability to perform sender based routing. Each MMSC Routing has a "Default Sender Address" associated with it. If the sender address in a message matches the sender address in a route, then this route will be used (instead of the recipient routing), as this is a way that you can explicitly specify a route.

If you need to consult a database of phone numbers in order to determine the appropriate route, it is also possible to configure an HTTP callback so that NowSMS issues an HTTP request to ask how the message should be routed. This callback is described below:


quote:

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.




-bn