MMS under Mobile Number Portability

MMS under Mobile Number Portability SearchSearch

SMS & MMS Technical Forum » MMS & SMS Technical Discussions (unsupported) » MMS under Mobile Number Portability « Previous || Next »
Author Message
Lorenc Llukmani
New member
Username: Naksukau

Post Number: 1
Registered: 02-2012
Posted on Tuesday, February 07, 2012 - 03:36 pm:   

Hello,

Does the NowMMS support the Mobile Number Portability?
Which is the flow for a normal MMS send from A-party toward a B-party from the same mobile operator under Mobile Number Portability rules?
Which is the flow for a normal MMS send from A-party toward a B-party ported out to another mobile operator under Mobile Number Portability rules?

Thanks in advance.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 3761
Registered: 08-2008
Posted on Tuesday, February 07, 2012 - 03:58 pm:   

Hi,

The NowSMS MMSC provides hooks to allow you to implement Mobile Number Portability (MNP).

Different countries have different database providers and implementations for their MNP database.

The NowSMS MMSC allows you to define an HTTP callback for MNP. Basically, for each message, we issue an HTTP request to this callback, providing the recipient phone number, and the callback returns route information if the recipient is external.

It sounds a little complicated, but it's not. Basically you need to be able to query your MNP provider with a PHP script or something similar.

The normal operator interconnection method is MM4, which is SMTP based.

Typically you may have direct MM4 interconnections to other operators in your same country, and maybe to other operators in the same group ownership. And then also to a global interconnect such as Mach, Verisign, Aicent, Orange, etc.

Or some of our customers don't bother with interconnections to other operators in the same country and route all messages to an interconnect, or convert them to SMS with a web link.

The following article provides more information on the NowSMS MMSC callback for MNP: http://www.nowsms.com/doc/mmsc-messaging-server/operator-mmsc-considerations/mob ile-number-portability-mnp-considerations

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

Post Number: 3762
Registered: 08-2008
Posted on Tuesday, February 07, 2012 - 04:02 pm:   

For the sake of completeness, answers to other Q's:


quote:

Which is the flow for a normal MMS send from A-party toward a B-party from the same mobile operator under Mobile Number Portability rules?




1.) Message received by MMSC.

2.) MNP/Routing callback determines local recipient.

3.) MMSC sends MMS notification to initiate delivery to local recipient.


quote:

Which is the flow for a normal MMS send from A-party toward a B-party ported out to another mobile operator under Mobile Number Portability rules?





1.) Message received by MMSC.

2.) MNP/Routing callback determines remote recipient and returns name of route to be used.

3.) MMSC converts message to MM4 format and transmits to the other operator MMSC or interconnect as per MM4 connection configuration.

4.) Other operator MMSC or interconnect validates and converts back to MM1 format for delivery.

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