Routing MMS to VASP (MM7)

Routing MMS to VASP (MM7) SearchSearch

SMS & MMS Technical Forum » NowSMS Support - MMS & Advanced Issues (Product Support Only) » Archive through July 14, 2004 » Routing MMS to VASP (MM7) « Previous || Next »
Author Message
Posted on Monday, May 03, 2004 - 07:52 am:   

I am testing the Now SMS/MMS gateway 5.01 (b20040120)

I need to route all incoming MMS that match a specific regular expresion to my VASP.

For example,


this Regular Expresion means that all MM sent to a number that starts with 042 and has 7 characters whatever they are, will be routed to the VASP

Is possible to do that?

Another question.. Where I specified the url of the http VASP server? (MM7)


Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2448
Registered: 10-2002
Posted on Monday, May 03, 2004 - 01:36 pm:   


In NowSMS, you would specify that pattern as 042??????? (or 042* if you didn't really care how many characters followed 042).

Normally, this would be configured in the "MMSC Routing" dialog, where you would define an outbound route.

"Account name" and "Account Description" are just internal ids that are used for routing within NowSMS.

"Default Sender Address" is used to override the sender address specified in a message.

"Allow Sender Address Override" should be checked if you want to pass through the original sender address in the submitted message.

"Route messages to this account for recipient phone number(s)" is where you would specify the address mask described above. This list can contain a comma delimited list of these address masks (avoid any space characters in the list).

"Route messages to VASP via" would be set to MM7.

"Server address" would contain your MM7 URL (with or without the HTTP prefix) ... e.g.,

"Login name" and "Password" can be specified to use HTTP Basic Authentication for connecting to the server.

I hope that answers your questions.

Posted on Monday, May 03, 2004 - 06:04 pm:   

Thanks Bryce, but is not working :-(

This error appear in the log...

2004-05-03 14:40:42,MMSIN,,,,User Not Defined,FAILED

I think that is because the Radius Accounting is not activated.
I can't activate because the GPRS is not available (maybe in jun.)

And the current Access Server for the CSD connection sent the number to the authentication port (not accounting).

So, is possible to put a "virtual source number", so I can continuing testing?

Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2462
Registered: 10-2002
Posted on Monday, May 03, 2004 - 06:14 pm:   

I'm not sure how that relates to the above.

Unless the first message was about your ultimate goal ... but you haven't gone through the basic configuration yet.

If you do not have a RADIUS accounting feed that allows the WAP proxy to provide user idenitification to the MMSC, then you need to configure the MMSC Server URL in the phone to include a username and password.

Typically, you would configure the URL to be

Where username and password correspond to an account that is defined in the "MMSC Users" list.

Define at least 2 accounts in this "MMSC Users" list, as we have had some sporadic reports of the user not being properly identified when only one user is defined in that list.

The Now.WAP proxy is pretty flexible about accepting both RADIUS auth and accounting packets. Kent Williams can answer questions about that better than I. But I do recall one installation where the access server would not provide complete accounting information unless the RADIUS auth server allocated IP addresses on behalf of the access server. There is a discussion of this type of configuration in the following thread:

The access server still needs to support RADIUS accounting. We've just found that some access servers get confused if the RADIUS auth server is not allocating IP addresses for the access server.


Login Login / Register Logout Logout Search Last 30 Days Topics Topics