| Can I change SMSC callTimeout ? |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through September 15, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| Paul |
Hi, in smsout*.log there are items, containing error "Retry Pending - Timeout waiting for response from server or lost connection". As seen on timestamps, this timeout is equal to 30 sec and freezes all data exchage on this time (you're using only ONE connection to SMSC server one time, isnt it?). Can I decrease this timeout? I'm using UCP SMSC. Sorry for bad English, it's not my native language WBR, Paul | |||
| Bryce Norwood - NowSMS Support (Bryce) |
Hi Paul, Unfortunately, this timeout is not configurable. We could look at changing this, as that would not be very difficult. But I would be concerned that too low of a timeout would result in false errors. I did some checking, and in the UCP/EMI interface, we are actually using a timeout of 120 seconds, not 30 seconds. So it sounds like what is happening is that the SMSC is dropping the connection, and that is what we are detecting. I find this very unusual that the SMSC would be dropping connections like this. Perhaps you need to set a value for "keep alive" packets to be sent every so many seconds so that the SMSC does not drop the connection. BTW ... if you want to use multiple connections to the same SMSC, there is a trick to being able to do this. NowSMS will only allow you to configure one connection to a particular host name and port address. However, you can create a HOSTS file entry in the WINNT\SYSTEM32\DRIVERS\ETC directory where you have multiple alias names for the SMSC. Then you can configure NowSMS to connect to the different alias names that are defined in the HOSTS file. NowSMS sees each alias as a separate SMSC, and it will maintain multiple connections to the same SMSC in this manner. -bn | |||
| Paul |
Bryce, thank you for your irrefragable answer WBR, Paul | |||
