Hi all,

 

Yes these will work for the WAP PUSH notification but the MMS will not get 
downloaded, because ported out subscribers have MMS settings of a different MMS 
center.

 

What Mbuni needs is the logic to send the WAP PUSH to the subscribers belonging 
to your network. So parameter local-prefixes = 040;+38640;38640 is of no use. 
You have to define different parameter to indicate the local subscriber which 
is based on the RN (Routing Number).

 

Example:

 

In Slovenia we have two big operators Mobitel and Simobil. Mobitel CC= 386 
NDC=41 and Simobil CC=386 NDC=40. ATRP which is an agency for 
telecommunications, gave Mobitel RN=9800 and Simobil RN=9801.

 

So what Simobil did is implement LDAP server where all portedin or portedout 
subscribers are inserted. When MMS center wants to indicate the RN for the 
subscriber first checks the LDAP DB and if there is an entry for the subscriber 
the routing is done according to the RN specified. If subscriber is not found 
in the DB then routing is done according to prefix.

 

I was thinking of my own implementation of MNP on the Mbuni by setting my own 
SMTP server and send all messages to the SMTP server. SMTP server then 
implements MNP LDAP functionality and if the subscriber is identified as local 
subscriber SMTP server just adds the right domain to match local-mmsc-domains 
parameter and sends MMS back to MMS proxy. This message will be delivered to 
the local subscriber. If MMS is identified as foreign, different domain will be 
added and send to the sendmail SMTP server. In this way MSISDN is not relevant 
for the routing of the MMS. 

 

There is no need for implementing the LDAP functionality in exact manner I 
described. It is possible to have a portedin, portedout database of any kind 
(Mysql, PostgreSQL, SQLite). There is also possibility to have it in the 
configuration file but changing configuration for every ported subscriber is 
not a good idea.

 


________________________________

From: [EMAIL PROTECTED] on behalf of Paul Keogh
Sent: Fri 4/7/2006 12:26 PM
To: Mbuni MMS Gateway Developers
Subject: Re: [Devel] MNP on Mbuni




On 3/30/06, Jaka Nemanic <[EMAIL PROTECTED]> wrote: 


        Is MNP hard to implement on Mbuni?

        We will not implement CSD so we can skip the authorization MNP check, 
we only need the routing MNP functionality.

         


Do you mean MNP for the MMS notifications over an SMS bearer ?

If so, can you not use the same solution as application to person (A2P) SMS 
messaging uses in your network ?


<<winmail.dat>>

_______________________________________________
Devel mailing list
Devel@mbuni.org
http://mbuni.org/mailman/listinfo/devel_mbuni.org

Reply via email to