| Throttle Settings For Multi-Session SMSC Connection |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ |
◄ ► |
| Author | Message | |||
| Mathew Mathachan Frequent Contributor Username: Mathewm Post Number: 164 Registered: 04-2011 |
Hello Support team, NowSMS allows for a throttle to be set on a SMSC connection, in the “Connection Restrictions” by enabling and entering a value for the “Limit Message Speed”. We normally set the licensed SMS/sec value. However, at the SMSC end, the operator allows up to six sessions on each SMSC link and they restrict the throttle for each of the several sessions in the link. The aggregate throttle allowed is the sum of the throttle in all the sessions. From the NowSMS documentation it appears that these six sessions can be configured in the “SMPP Advanced Configuration Options” by entering “6” in “# Transmitter Sessions” field. Please confirm if that is the correct way to get the maximum performance of the operator’s SMSC. The operator has a maximum allowed throttle of 20 SMS/sec on each of the sessions. Is there a setting on NowSMS where we can configure a throttle at the session-level to ensure that we stay within the operator guidelines. We see a “# Receiver Sessions” field. Is this for SMS Pull messages? Is it also used for SMS Status messages sent by the SMSC? | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 8490 Registered: 10-2002 |
Hi Mathew, The “Limit Message Speed” throttle is applied at a session level. Each session has this limit, independent of other sessions. Regarding “# Receiver Sessions” … There are 3 types of SMPP connections: 1.) A “sender” connection should only transmit messages (submit_sm). The server should not attempt to deliver any messages to the client (deliver_sm) using this connection. This includes status messages (a.k.a. delivery reports or delivery receipts). (Some SMPP servers will still deliver delivery reports over such a connection. This is against the SMPP specification, but NowSMS will allow this.) 2.) A “receiver”, connection is not allowed to transmit messages over the connection, it can only receive messages (deliver_sm). 3.) A “transceiver” connection is allowed to both send and transmit messages over the same connection. NowSMS has historically defaulted to use separate sender and receiver connections. But most of our customers end up configuring transceiver connections, because SMPP providers prefer to have fewer connections. You might see better performance transmitting over a sender connection than a transceiver connection, especially if most of your messages are requesting delivery reports. However, in most cases, I would not expect to see significant performance differences. Regards, Bryce Norwood NowSMS Support | |||
