| Control of destination on MMS-IN request |  Search
|
|
NowSMS Support Forums ⬆ NowSMS NextGen Support ⬆ |
◄ ► |
| Author | Message | |||
| marc bazimon Frequent Contributor Username: Marc_orange Post Number: 150 Registered: 01-2007 |
Hi Nowsms support , we have some loop on our MM4 interface due to mis-using of portability from our MMS HUB carrier. let me explain exactly what happen, let s take an example, a subscriber from Orange Reunion( a number ) send a MMS to a number of our competitor ( B number ) who did a portability from Orange to the competitor. So B Number has got a MSISDN that was initially belonging to Orange but now belong to our competitor. SO when A send a mms to b , MMSC will send the MMS through MM4 to an HUB that is supposed to route the MMS to our competitor.Unfortunatly , the HUB doesn't manage portability correctly and do the routing only with the number range. as the number is initially from Orange , they send back the MMS to us. MMSC take this MMS and resend it back to HUB as B number is not bleonging to our network anymore. and this occurs every 3 mns Is there any control on MM4 interface that check the b Number , and control that the b number is well belonging to our network , and if not the MMS is not resending back but deleted ? if not , it could be a good thing to add trhis to the next version, because we have the OUTBOUND MMS queue that increase and this is add some delay in the delivery. currently we have 211 messages in the queue, and we can see that the 211 messages is generated every 3 mns. another board effect from that is that we pay for each mms going through the HUB , even if we know that the fault is on hub side and not the mmsc. Hope it is clear , Thanks beforehand for your feedback , Br Marc | |||
| marc bazimon Frequent Contributor Username: Marc_orange Post Number: 151 Registered: 01-2007 |
It could be also , a check on the OUTBOUND MMS queue that the A number should be belonging to orange reunion before sending. | |||
