Hi List, I'm just staring at the emi2 sources to figure out how to best add features we need. Here is our situation: We have an EMI/IP account with a GSM operator here in Germany. To access the SMSC we use a dial-up ISDN line, this means we have to make a long distance call every time we want to send some messages. EMI2 does not handle this situation well: 1. It always keeps the TCP connection open, even if there is no need. (high charges for the long distance call) 2. It does never close the TCP connection. This leads to a second problem unrelated to 1): EMI sessions are bound to the TCP connections. If the ISDN connection breaks down for some reason (e.g. idle timeout) the TCP connection is not terminated properly, so the EMI session stays active until the TCP connection times out on the SMSC side. During this time new connection attempts are refused because we exceed our session limit. Since Kannel treats every refused login request as fatal, no future connection attempts are possible without a bearerbox restart.
What do I want? 1. A configuration option that allows me to specify how long the TCP connection is allowed to be idle. 2. Graceful handling of temporary login failures. I'd like some input on this from the EMI2 hackers here on the list. Regards J�rg
