[asterisk-dev] Channel support for GSM devices
odi at odicha.net
Thu Oct 8 09:04:56 CDT 2009
Tzafrir Cohen escribió:
> Sounds interesting,
> On Thu, Oct 08, 2009 at 10:00:54AM +0100, Odicha wrote:
>> Firstly apologies for my English
>> I have a project idea. The aim is to provide a single asterisk channel
>> services to all GSM hardware that can connect to the system
>> Needs to be met.
>> 1) It will provide voice capabilities
>> 2) It will bring instant messaging services
> What do you mean?
> I suppose that you basically want something similar to what we have in
> SIP and XMPP. Routing messages between different channels is a bit more
>> 3) It will provide a layer signaling over states of the GSM network and
>> the hardware itself
>> Hardware capable of being used.
>> Any device with GSM capabilities. We can distinguish 3 main groups:
>> 1) GSM Modems. Usually USB or PCMCIA PCEXPRESS.
>> 2) MultiModem Devices (eg. Junghanns Openvox quadGSM or OpenVox G400P)
> Junghanns wrote libgsmat that was intended to integrae that one into
> chan_zap, using his ztgsm driver.
But if I take a look at ztgsm code and I want to use some portions,
we'll be in same status that with zaphfc...
Perhaps it would be better start from scratch... because I think forking
dahdi is not a good solution at all (no more "bristuffs" please...)
Or perhaps, one thing I have though sometiemes is that perhaps asterisk
could have a "third parties addons branch"... A svn for all those things
that due to code policy can't be into asterisk trunk but they can be
useful (as zaphfc, for example), so we won't have no more lose or
redundant works (as chan_sebi // chan_datacard issue... two different
people doing the same)
>> 3) External FXS Gateways (Nokia Premicell type, Xacom Celline, etc) with
>> a serial or usb port usually we can use for receive and send sms
> Hmm... in this case you don't need a separate channel driver.
>> ** Supported buetooth devices be left out but are covered by another
>> module that has a different philosophy to that proposed here, they could
>> be ported without much complexity in the future
>> If we look we see first of all we have to divide, first between devices
>> with voice and data devices that operate alone, and secondly, between
>> devices that must be added hardware management (as multiport cards) and
>> those with maintain contact with only AT (like any traditional modem)
>> My proposal goes through using a model similar to chan_dahdi with a
>> common interface towards Asterisk and connect with specific modules for
>> each class of hardware device, simplifying management tasks. For
>> example, to send an sms through any supported device to follow the
>> protocol to asterisk would face exactly the same.
> How about a slightly different task: I got an SMS message on one such
> modem. How do I pass it to my SIP phone?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the asterisk-dev