| Limit speed of receiving messages for that account |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through August 22, 2012 ⬆ |
◄ ► |
| Author | Message | |||
| Alex Kaiser Frequent Contributor Username: Alex_k Post Number: 272 Registered: 07-2006 |
Hi Des, We tested that GUI parameter - wireshark showed us that it doesn't work properly. Speed limiting was unstable and below set values (per sec). I guess you should look into. Also please check SMSCSendLimit parameter in multi binds mode (4xTRX), I think there’s some problems too. All actions rises CPU to 100%. Kind regards, Alex K. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3866 Registered: 08-2008 |
Hi Alex, I don't see any CPU related issues. However, I do see that the server-side receive limit setting is applying the limit on a per connection basis. This limit should be applied aggregate for the user account across all connections. This is an oversight and will be fixed in the next update. I would stress that when using this limit setting, you should recommend that clients connect with separate transmitter and receiver connections. If a transceiver connection is used, messages may be limited in both directions (sending and receiving). When separate transmitter and receiver connections are used, the limit will only effect the intended direction. Regarding SMSCSendLimit, that parameter is intended to be applied per connection, not in aggregate across multiple connections. It is working as intended. In my tests of these settings, CPU utilisation was extremely low, so if you are seeing extreme CPU usage, there must be some other contributing factor/setting. -- Des NowSMS Support | |||
