SMS are now stored in SQL table

Hi all! Today I've just committed some code that stores incoming SMS in the SQL table as soon as they are received. There is also more error handling right now, i.e. if the SMS is sent to an unknown extension, it is rejected right away. What's still missing is the code to actually deliver the SMS from the SQL table to the destination phone. For this, we need to * decouple paging from voice calls * correctly construct TPDU and RP/CP header from actual SMS payload * trigger SMS delivery of pending messages at LOCATION UPDATING / IMSI ATT * trigger SMS delivery once the MS tells us it has memory (SMMA) * regularly iterate over undelivered SMS and try to send them * decide how to handle SMS while a voice call is ongoing If anyone has a good idea what to do about UCS2 encoded messages, I'm more than happy to hear about it. My plan so far is to translate it to UTF-8 and store it as UTF-8 in the SQL database. This way we have something that most linux systems (and other tools) can deal with. Disadvantage is that we'd end up translating a message back and forth... Also, if somebody is more familiar with the 'regular' SMSC architecture in real GSM networks, it would probably be good to think of a way how we can integrate external SMS delivery both incoming and outgoing. SMS is much easier since it is basically data/signalling only and there's no need to actually route unstructured voice data like it is the case for regular phone calls. -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)