Adding a second operator to our MMSC

Adding a second operator to our MMSC SearchSearch

SMS & MMS Technical Forum » NowSMS Support - MMS & Advanced Issues (Product Support Only) » Adding a second operator to our MMSC « Previous || Next »
Author Message
Antonio Medina Ortega
New member
Username: Antoniomedina

Post Number: 5
Registered: 07-2015
Posted on Monday, June 11, 2018 - 11:09 am:   

Hi all,

We are running NowSMS/MMS Gateway release v2016.03.28. At this moment, we are using it for just one operator and we are not allowing delivery of MMS to other operators, we mean, subscribers are not allowed to send MMS to other operators. We have the following configuration in place:

MMSC.INI --> MSISDNHeaderDefaultCountryCode=XYZ

MMSC Routing --> There are no MMSC Routes defined. We just use --> Default Route= Direct Delivery (internal MMSC)

SMSC: We have defined one SMSC to route messages for only prefixes +XYZ*.

We now need to use our platform for another operator with country code ABC. We want the same service for this new operator, we mean, subscribers for that new operator will not be allowed to send MMS to other operators.

We believe we need to do the following:

MMSC.INI --> Delete MSISDNHeaderDefaultCountryCode and configure the following:
MSISDNHeaderPrefixConvert=XYZ:+XYZ,ABC:+ABC
MMSC Routing --> No need to change anything
SMSC: We will define a new SMSC connection to only route messages for prefixes +ABC

Should we perform any other action?

In addition, the suggested configuration would allow a subscriber of operator 1 to send MMS to a subscriber of operator 2. Are we right? Is there any way to prevent that?

Thanks in advance.

Kind regards,
Antonio.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5928
Registered: 08-2008
Posted on Monday, June 11, 2018 - 08:38 pm:   

Hi Antonio,


quote:

We believe we need to do the following:

MMSC.INI --> Delete MSISDNHeaderDefaultCountryCode and configure the following:
MSISDNHeaderPrefixConvert=XYZ:+XYZ,ABC:+ABC
MMSC Routing --> No need to change anything
SMSC: We will define a new SMSC connection to only route messages for prefixes +ABC




Correct


quote:

Should we perform any other action?




If local number to international number conversion requires removing a prefix (often 0), see
https://support.nowsms.com/discus/messages/485/20148.html


quote:

In addition, the suggested configuration would allow a subscriber of operator 1 to send MMS to a subscriber of operator 2. Are we right? Is there any way to prevent that?




Correct.

The only way to prevent would be to implement an MMS routing callback, where you evaluated sender and recipient to determine whether or not to allow.

More info here:

https://www.nowsms.com/doc/mmsc-messaging-server/operator-mmsc-considerations/mo bile-number-portability-mnp-considerations

A short explanation of how it works...you create a script on a web server (for example a PHP script). You configure the MMSC to use this as a routing script.

Your script will receive an HTTP request similar to this:

http:// server.name/path?Type=MMSRouteCheck&From=%2B1234567&To=%2B9999999999

To reject, the script outputs the text

Route=BlockMessage

To process as direct delivery, output the text

Route=Direct


If a route response is received from the script, this overrides the static MMSC route configuration.

--
Des
NowSMS Support

Add Your Message Here, or click here to create a new discussion topic.
Post:
Bold text Italics Underline Create a hyperlink Insert a clipart image
Posting Information:
This is a private posting area. Only registered users and moderators may post messages here.
Click here to create an account.
Username:
Password:
Options: Automatically activate URLs in message
Action:

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