Nikos, Yes it works fine with sim-buffering set to false. I don't really want to change modems as the one I have works with this simple fix and it took quite a while to work out the kinks. (i.e. the ^PORTSEL cmd).
I realize that the gateway is supposed to be on at all times, but occasionally servers do have to be rebooted, updated, etc. I just wanted to have all my bases covered. If I run with CNMI notifications, sim-buffering=true, and my simple change to smsc_at.c, then I think I'm all set. I get message notifications via CNMI, and I get held messages on restart. Also, I came across someone else who I think had the same problem on a e220. http://kerneltrap.org/node/17017 There were other postings on various forums asking about the Invalid memory index error log, but no answers, so this may apply to other modems as well. If I had the time, I'd like to add some config option to kannel to tell it what the first memory slot is (0 or 1), but unfortunately I don't. Though my guess is that for someone on this list, that's a 5 minute change. Thanks, -Chris 2010/4/22 Nikos Balkanas <[email protected]>: > Hi, > > Seems a lot of trouble for a single modem. Ever considering changing it? > Does it work OK without sim-buffering? > Kannel gateway is supposed to be on at all times. > > BR, > Nikos >> 2010-04-22 09:13:32 [12167] [7] ERROR: AT2[huawei]: CMS ERROR: +CMS ERROR: >> 321 >> 2010-04-22 09:13:32 [12167] [7] ERROR: AT2[huawei]: CMS ERROR: Invalid >> memory index -> don't worry, just memory fragmentation. (321)
