Rejecting MMS for certain prefixes

Rejecting MMS for certain prefixes SearchSearch
Author Message
Antonio Medina Ortega
New member
Username: Antoniomedina

Post Number: 6
Registered: 07-2015
Posted on Monday, June 11, 2018 - 01:15 pm:   

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*.

When a subscriber attempts the delivery of a MMS to another operator, it fails because there is no SMSC route to notify the receiver. However, from the point of view of the sender, the MMS has been sent. Is there any way of configuring NowSMS/MMS Gateway to make the sender aware of it is not possible to send the MMS to that destination? At least, to provide him/her an error instead of accepting the MMS

Thanks in advance.

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

Post Number: 5926
Registered: 08-2008
Posted on Monday, June 11, 2018 - 10:03 pm:   

Hi Antonio,

The easiest way to handle this is to create an MMSC route of type direct, and give it a prefix of +XYZ*. Then set the default MMSC route to Block/Reject Message.

Or even better, use a prefix of +XYZ????????? padding with ? to match the number of digits in a supported number.

--
Des
NowSMS Support
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5927
Registered: 08-2008
Posted on Monday, June 11, 2018 - 10:08 pm:   

These screen shots should help clarify my comments:


Add Your Message Here, or click here to start a new topic.
Post:
Bold text Italics Underline Create a hyperlink Insert a clipart image
Options: Automatically activate URLs in message
Action: