| SS7 HLR lookup |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ |
◄ ► |
| Author | Message | |||
| marc bazimon New member Username: Marc_orange Post Number: 41 Registered: 01-2007 |
Hi I go back on an old subject that we start discuss about regarding a HLR lookup interfacing. https://support.nowsms.com/discus/messages/485/71497.html As you should know , MMSC from other supplier like nokia , Ericsson , Xura has got a SS7 interface that is used in order to manage the routing of message terminating ( let's call it MT as sms ;)) This is useful for the PNM (the number portability). In order to manage this currently , we use the mmsrouting callback , that request a server connected to customer DB in order to know of the customer had been leave the network and where. This is quite laborious because all the competitor that supposed to fill the portability don't do that.The effect is that some MMS are failed because , it is sent to the wrong network. Anyway , sigtran ( SS7 over IP ) could be use to do a SRI for SM ( send routing information for short message ) on the target HLR in order to retrieves the IMSI of a customer. This IMSI is the indicator of the network. I know that linux system has got openSS7 or equivalent in order to do that but i don't know about windows. The solution for you is to have a connection between the MMSC and the STP ( switch SS7 that belong to the operator network ) in sigtran. the MMSC will be alowed to make SRI request to HLR, (there's three version of map ) , the HLR will return back the IMSI and also the location ( but you need only the IMSI ). THe best way is to have a routing table that will make the correspodance between IMSI , and the specific route. i can send you SRI request on each map version if you are interested in ? I think it could be a major update , this will lead of being at the same step than other MMSC supplier for a lower cost. does it seems possible to do such thing ? Br Marc | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5822 Registered: 08-2008 |
Hi Marc, I just wanted to follow-up on this. One of my colleagues has corresponded with you via email, and I understand their next step is to run some tests with an emulator to evaluate feasibility. Estimate is early May for that activity. -- Des NowSMS Support | |||
| marc bazimon New member Username: Marc_orange Post Number: 48 Registered: 01-2007 |
Hi Des, We have some exchanges with Brett Warthen. i will forward it to you. The action point was on my side. The SRI_for_SM is a thing but before arrive on this step, there is couple of things that happen on the SS7 layer. I ask advices to my colleague from NSS that are SS7 expert and they seem pessimist because of the quantity of step. Firstable we have the sigtran to build with the association set. before having exchange with the HLR ( through STP ( SS7 switch )) there is couple of control message that check the parameter on both side in order to be compliant. After the SCTP layer , we should think about the M3UA layer where a point code will be discuss , then the SCCP layer ( where a GT address and a SSN ( subsystem number ) will be check ). After this step , we will have to take care about the TCAP layer that are a layer that allow the exchange between the sccp and the MAP layer. So we arrive on the MAP layer that will be the base for the sms application message ( the SRI for SM ). After this, we will have to manage all the error messages that could come from the HLR on all the layers. For exemple, the response from a SRI for SM , could be absent subscriber , paging failed , IMSI detached , etc.. Let me try to commit all these informations step by step. i can forward to you the Norm for all these layer if you want. Br Marc | |||
| Larry Hurwitz New member Username: Larryhsa Post Number: 1 Registered: 07-2017 |
Hi Marc Based upon your input you seem to be our saving grace. Please can I chat to you asap. I am on GST +2 and can be reached at larryhsa@gmail.com or larryh@3dtgroup.com Thank you so much in advance. Cordially, Larry. | |||
