| Strange notifications into the smsOUT |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ |
◄ ► |
| Author | Message | |||
| marc bazimon Frequent Contributor Username: Marc_orange Post Number: 95 Registered: 01-2007 |
Hi , checking the sms queue file that was really compare to usual , ( 800 sms instead of 30 ), i did check the log on the SMSOUT log and i found lot of notification that should not appear here. let me explain, on the SMSOUT , we should see only our subscriber as it is supposed to being in the MMS DB. but as you can see the mmsc try to send to number that not belong to us. Despite this , you can see that this smell as a fraud because the numbers are concomitant do you have a idea what use case can generate this ? thanks beforehand for your feedback Br Marc 2020-11-15 07:00:53,SAR-+352655100007-ed-2-1,,+352655100007,Retry Pending - ERROR: Throttling error (ESME has exceeded allowed message limits) - ESME_RTHROTTLED (0x58) -- SMPP - 10.241.42.12:3339,SubmitUser=localsystem-mmsc;Sender=mms 2020-11-15 07:00:53,SAR-+352655100010-ed-2-1,,+352655100010,Retry Pending - ERROR: Throttling error (ESME has exceeded allowed message limits) - ESME_RTHROTTLED (0x58) -- SMPP - 10.241.42.12:3339,SubmitUser=localsystem-mmsc;Sender=mms 2020-11-15 07:00:53,SAR-+352655100013-ed-2-1,,+352655100013,Retry Pending - ERROR: Throttling error (ESME has exceeded allowed message limits) - ESME_RTHROTTLED (0x58) -- SMPP - 10.241.42.12:3339,SubmitUser=localsystem-mmsc;Sender=mms 2020-11-15 07:00:53,SAR-+352655100014-ed-2-1,,+352655100014,Retry Pending - ERROR: Throttling error (ESME has exceeded allowed message limits) - ESME_RTHROTTLED (0x58) -- SMPP - 10.241.42.12:3339,SubmitUser=localsystem-mmsc;Sender=mms 2020-11-15 07:00:53,SAR-+352655100015-ed-2-1,,+352655100015,Retry Pending - ERROR: Throttling error (ESME has exceeded allowed message limits) - ESME_RTHROTTLED (0x58) -- SMPP - 10.241.42.12:3339,SubmitUser=localsystem-mmsc;Sender=mms 2020-11-15 07:00:53,SAR-+352655100018-ed-2-1,,+352655100018,Retry Pending - ERROR: Throttling error (ESME has exceeded allowed message limits) - ESME_RTHROTTLED (0x58) -- SMPP - 10.241.42.12:3339,SubmitUser=localsystem-mmsc;Sender=mms 2020-11-15 07:00:54,SAR-+352655100019-ed-2-1,,+352655100019,Retry Pending - ERROR: Throttling error (ESME has exceeded allowed message limits) - ESME_RTHROTTLED (0x58) -- SMPP - 10.241.42.12:3339,SubmitUser=localsystem-mmsc;Sender=mms 2020-11-15 07:00:54,SAR-+6857215603-ed-2-1,,+6857215603,Retry Pending - ERROR: Throttling error (ESME has exceeded allowed message limits) - ESME_RTHROTTLED (0x58) -- SMPP - 10.241.42.12:3339,SubmitUser=localsystem-mmsc;Sender=mms 2020-11-15 07:00:54,SAR-+6857215621-ed-2-1,,+6857215621,Retry Pending - ERROR: Throttling error (ESME has exceeded allowed message limits) - ESME_RTHROTTLED (0x58) -- SMPP - 10.241.42.12:3339,SubmitUser=localsystem-mmsc;Sender=mms 2020-11-15 07:00:54,SAR-+6857215670-ed-2-1,,+6857215670,Retry Pending - ERROR: Throttling error (ESME has exceeded allowed message limits) - ESME_RTHROTTLED (0x58) -- SMPP - 10.241.42.12:3339,SubmitUser=localsystem-mmsc;Sender=mms 2020-11-15 07:00:54,SAR-+6857215670-ed-2-1,,+6857215670,Retry Pending - ERROR: Throttling error (ESME has exceeded allowed message limits) - ESME_RTHROTTLED (0x58) -- SMPP - 10.241.42.12:3339,SubmitUser=localsystem-mmsc;Sen | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 6199 Registered: 08-2008 |
Hi Marc, These are likely misdirected/misrouted MMS messages, or possibly MMS delivery reports. Searching for the number and/or SAR-1 (ID) reference in MMSC-yyymmdd.LOG should reveal the original transaction. (One of the nice enhancements in the Linux version is enhanced tools for searching and filtering log issues to more quickly get details. For example, from the status page in the web interface, you can click on statistic headers such as SMS Retried or SMS Failed to filter the log for only those entries. Click on an MSISDN to see more transactions involving that number.) How are your MMS routes selected -- accounting callbacks or based on number prefix? Regards, Des NowSMS Support | |||
| marc bazimon Frequent Contributor Username: Marc_orange Post Number: 96 Registered: 01-2007 |
Hi Des , We troubleshoot and found why. We are using routing callback. but as the MSISDN is quite exotic for our network , the routing Gateway respond with no route ( response are empty ). The Behaviour of the MMSC in this use case , is to send to the MM1 interface. In order to avoid this , we will send all this type of MMS on a "unknown" route that reject the message. Thnalks for your quick feedback , have a nice day , Br Marc | |||
