| Upgrade for NowSMS MMSC issue - Orange Madagascar |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through July 28, 2014 ⬆ |
◄ ► |
| Author | Message | |||
| Rambeloson Andry Juvenale New member Username: Andry_juvenale Post Number: 1 Registered: 01-2014 |
Dear Support, We create this discussion with you, because we had a prblème on the new version of NowSMS MMSC We have well finished installing the new NowSMS MMSC application you provided, and some day after we meet a problem with the new version because from the Logs we have a code of " 0X00000411 error ", could you tell us, why we encountered this kind of problem after upgrade, note that everything is fine before (with the old version). Could you give us the procedure for the uninstalling the current application (vew version), and thank you to tell us how to reinstall the old version. If possible, provide us a proforma regarding the uninstallation of the new version and the reinstallation of the old version. Note that we no longer have the old version. Best regards Andry Juvenale Orange Madagascar | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4793 Registered: 08-2008 |
Hi Andry, First things first ... to re-install the old version, you just run the install program for the older version and let it install over the top of the newer version. (This is the exact same way you install a newer version.) Never uninstall, as this will lose your configuration. If you no longer have access to the install for the version you are running, advise the version number and I will locate it for you. I would also like to address the problem that you are experiencing, and will post another reply shortly to specifically address that issue. -- Des NowSMS Support | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4794 Registered: 08-2008 |
Hi Andry, I share your frustration that you have been unable to resolve the problem of the "0x00000411" error. However, I want you to understand that this error is not coming from NowSMS. This error is coming from your SMPP Server (SMSC) when NowSMS tries to submit an SMS message over SMPP. These SMS messages are the MMS notification trigger which initiates an MMS message delivery process. As I understand it, the following error is occurring in your SMSOUT log, and no SMS messages are actually sent: Retry Pending - ERROR: SMS Provider Specific Error Code 0x00000411 This means that every time NowSMS tries to submit an SMS message over SMPP, the SMSC rejects it with error 0x00000411 (i.e., hexadecimal number 411). We cannot tell you why this error is occurring, because 411 is a "provider specific" error code. This means that the error number is not defined in the standards, but the vendor of your SMSC has defined it as having a particular meaning for your SMSC. Whoever maintains your SMSC should be able to tell you what this error 411 means and why these SMS message submissions are being rejected. I would be very surprised if downgrading NowSMS made any difference as I cannot think of any fundamental differences in our SMPP implementation between versions. My best guess is that something else in your configuration was changed, coincidentally with the upgrade. The most common issue that leads to unexpected SMPP errors is the use of a sender address that the SMSC will not allow, or that is in a format that the SMSC will not allow. If you wish to troubleshoot this problem further, please: 1) Provide detail on the configuration settings for the SMPP connection in NowSMS, including those under "Advanced Settings". 2) Ask whoever maintains your SMSC what error 411 means on that system. 3) Enable the SMSDEBUG.LOG...let the system try sending a few messages, then collect the SMPPDEBUG.LOG and email to nowsms@nowsms.com. In the subject line of the message, put Attention: Des ... and post a reply on this discussion thread to tell me you have sent the log file. If I look at the SMPPDEBUG.LOG, this will help me understand your SMPP configuration settings so that I can suggest settings that might be changed to fit your SMSC's expectations. -- Des NowSMS Support | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4795 Registered: 08-2008 |
One more thing ... I was reading over an e-mail exchange between one of your colleagues and one of my colleagues and noticed your colleague said this:
What exactly does this mean? For all we know, error 411 from the SMSC might mean that the account being used to send SMS has an IP address restriction and 10.100.1.118 is not allowed while 10.100.1.117 is allowed. | |||
| Rambeloson Andry Juvenale New member Username: Andry_juvenale Post Number: 2 Registered: 01-2014 |
Dear Support, Thank you very much for your reply and your explanation, but we would always like to know why this error does not appear when the application is not updated yet ? 1 - Before the update , the application works fine and this error code does not appear so frequently . 2 - After update, this error code 0x00000411 appears . We still expect a return from the SMSC side about this error code. I 'll let you know as soon as I got feedback. And we confirm that there is not a restriction on SMPP SMSC address . And we have not done any configuration SMPP before and after the update . As you said : "If I look at the SMPPDEBUG.LOG , Will this help me Understand Your SMPP configuration settings so That I can Suggest That settings might be changed to fit your SMSC 's expectations." Could you tell us where can we find this file " SMPPDEBUG.LOG " We just would like to ask you: 3 - could you give us the old version because we do not have the source(.exe file). We need to downgrade this application. Thank you for your understanding. You will find in attached the configuration of the old version. Kind regards Andry Juvenale | |||
| Rambeloson Andry Juvenale New member Username: Andry_juvenale Post Number: 3 Registered: 01-2014 |
Hi, I can't attached the file containing the configuration of the old version. you find below: version : v2010.11.04 Installation reference code :3A2FEAB6 Serial#000036 Kind regards Andry Juvenale | |||
| Rambeloson Andry Juvenale New member Username: Andry_juvenale Post Number: 4 Registered: 01-2014 |
Hi, You find below, a feedback from our SMSC support : " For a normal MMSC, when service is switched, the ip should be switched from node 1 to node 2. For example, if node1 use 10.100.1.117 this ip address to send sms. After service switch, this ip should be switch to node 2. Then, node 2 can use this ip to send sms. Smsc have no the ip restriction function. And in our smsc, the 0x00000411 equals 1041. 1041 Maximum Submission Number Exceeded Error Code Description When the number of SMs that are sent from an SP and buffered in the memory of the SMS system reaches a specified upper limit: l If the called SME of an SM sent from the SP is in working or waiting-to-be-redelivered state, the SMS system fails to create an SM and thus the error code is returned. l If the called SME of an SM sent from the SP is not in working or waiting-to-be-redelivered state, the SM can be successfully submitted and no error code is returned. Solution Check whether the maximum submission number is specified for the SP in the service attribute table. If not, the maximum submission number specified for ordinary mobile subscribers is used as the maximum submission number of the SP. It is recommended that you set the maximum submission number for the SP in the service attribute table to 30% of the maximum number of SMs that can be stored in the memory. But now, the MMSC use different ip to send sms. I don’t know the node 1 and node 2 from MMSC side use same account to send sms or not?(need your confimation). " Best regards Andry Juvenale | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4796 Registered: 08-2008 |
Hi Andry, I want to answer all of your questions, but I want to deal with the most important issues first. I will follow-up with answers to other questions later. Let me recap what is happening: Every time a subscriber sends an MMS message, the MMSC needs to send an SMS message (MMS notification) to the recipient(s). (Usually the MMS notification is actually compromised two SMS messages.) When your MMSC tries to send this SMS message using SMPP, the SMSC rejects the attempt with error 0x411. This error code is not defined in the SMPP specification and is an implementation specific error code that has a meaning specific to the SMSC. According to your SMSC team, this error means "1041 Maximum Submission Number Exceeded". Based upon the explanation given, this seems to indicate that the SMSC has received too many messages from the MMSC that the SMSC is still trying to deliver. That is the choice of the SMSC, but as long as the SMSC continues to return this error, it will be impossible for the MMSC to deliver any messages. A functional working SMSC connection is required for the MMSC. To resolve this problem, it is necessary to resolve how to overcome this SMSC policy or limitation. When this error occurs, by default the MMSC will wait a delay period and then retry the SMS submission up to 20 times. It is possible to change the number of retries attempted by adjusting the retry settings as described at http://www.nowsms.com/smpp-error-code-handling-in-nowsms. However, this will only adjust how long the MMSC keeps retrying when the SMSC returns error 0x411. Until the SMSC can deliver the MMS notification, the MMS message cannot be delivered. I hope this explanation helps resolve the underlying service problem. If you do wish to go back to the earlier version of the MMSC, you can download and run the installer at http://www.nowsms.com/download/nowsms20101104.zip (the installer is in the ZIP archive). I have no reason to expect this version to behave any differently with regard to this error, because the required MMS delivery process and protocol has not changed. -- Des NowSMS Support | |||
| Rambeloson Andry Juvenale New member Username: Andry_juvenale Post Number: 5 Registered: 01-2014 |
Hello, Other than code 0x00000411 error, we also found the error code 0x00000412 After discussions with our support SMSC, they said: « 1.1.1 1042 Maximum Delivery Number Exceeded Error Code Description The error code is returned when the number of SMs that are buffered in the memory and destined to the same called party reaches the specified maximum delivery number. The maximum delivery number refers to the maximum number of SMs buffered in the memory for a subscriber when the subscriber acts as a called party. » « The error code is returned when the number of SMs that are buffered in the memory and destined to the same called party reaches the specified maximum delivery number. The maximum delivery number refers to the maximum number of SMs buffered in the memory for a subscriber when the subscriber acts as a called party. Check whether the maximum delivery number is specified for the SP in the service attribute table. If not, the maximum delivery number specified for ordinary mobile subscribers is used as the maximum delivery number of the SP. It is recommended that you set the maximum delivery number for the SP in the service attribute table to 30% of the maximum number of SMs that can be stored in the memory. ». We think reactivate old version. This is to find out if it is really a problem of "maximum delivery number." knowing that the service is on the node 1 (10.100.1.117) with the old version that does not have this problem, and has the same configuration as that of node 2 (10.100.1.118 with new version). Do you agree with us? If not, thank you to propose other solution. Regards Andry Juvenale | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4799 Registered: 08-2008 |
Hi Andry, I don't see how anything in the MMSC update could cause the SMSC to report these errors. But if everything worked before (were there two MMSCs before?) ... then I don't see the harm in downgrading, I just don't expect the version to make a difference. As you do not have a current support and maintenance agreement for the MMSC, and the update was provided as a courtesy request, it would make sense to go back to the old version, as you believe these problems were caused by the new version. I expect that the problems will persist. These errors are outside of the MMSCs control. The MMSC is trying to deliver an MMS message with an MMS notification over SMS, and the SMSC will not accept the SMS because it believes the MMSC has sent too many SMS messages. I just don't see the logic of SMSC policy placing such limiting constraints on an MMSC. I can think of a few possible scenarios that may cause excessive SMS traffic ... An overly aggressive "Retry MMS Delivery Notifications" setting on the "MMSC" configuration page. This will cause the MMSC to resend MMS notifications generating more SMS traffic. An "UndeliverableRouteToSMS" setting in MMSC.INI to reroute MMS messages that have not been picked up and converting them to SMS. In 2010 versions, this setting only worked with "SMS with web link (code)" routes. In 2013, the setting was expanded to also work with "SMS with web link (direct)" routes. So it could have been in the configuration before but not doing anything, and now it is trying to catch up on undelivered messages. Check MMSC.INI for this setting, and if present, remove it. Assuming the problems persist after the downgrade, I would like to see some log files in order to better understand your configuration and the issue you are facing. I would like to see MMSC-yyyymmdd.log and SMSOUT-yyyymmdd.LOG files from both systems so that I can better understand the messaging traffic. I am assuming that there is just MMS traffic that your SMSC considers excessive, but I would like to better understand. IF you want to send me those log files, please ZIP or RAR them and e-mail to nowsms@nowsms.com with Attention: Des in the subject line. Also, post a reply here to let me know you have sent those files via e-mail, in case they get trapped by an e-mail filter and I need to go look for them. -- Des NowSMS Support | |||
| RANDRIAMAHENINA Nantenaina New member Username: Nantenaina Post Number: 1 Registered: 01-2014 |
Hello, We would like to know, what improvement provided this new application for the service? Thank you! Best regards, Nantenaina | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4800 Registered: 08-2008 |
Hi Nantenaina, The following link highlights new features added between 2012 and 2013 releases: http://www.nowsms.com/faq/newsletter The following is our "changes" list which goes back further with brief descriptions of changes and enhancements: http://www.nowsms.com/download/changes.txt -- Des NowSMS Support | |||
| Rambeloson Andry Juvenale New member Username: Andry_juvenale Post Number: 6 Registered: 01-2014 |
Dear Support We finished the downgrade, and as you requested, I will sent the MMSC-yyyymmdd.log SMSOUT-yyyymmdd.log generated with the current application (old version) to nowsms@nowsms.com so that you can better understand the problem. Thank your for your support Best regards Andry Juvenale | |||
