Tom van der Geer wrote:
Hi Maxim,
Thanks for your response. I'm aware of existence of Kannel. I've worked
with it in the past as a HTTP to SMS gateway (maybe it does more than
that). In my setup it received HTTP requests and translated them to the
attached SIM box to send out SMS messages. So this basically was a home
brew HTTP-SMS provider as I described in my first post.
What I'm aiming at now is to be able to send SMS messages from a SIP
client using the MESSAGE method as described in RFC 3428 (if supported
by the SIP client). When a MESSAGE is send from a client to the
(predefined or catch-all) address, the HTTP-SMS module will translate
this request to an HTTP request. A large part of this functionality
already exists in the current SER SMS module, but these requests are
translated to serial communication with a SIM box or mobile phone.
Ultimately incoming SMS messages from the (mobile) network will be
translated back to SIP MESSAGE requests. These will be received as
(callback) HTTP requests from the SMS provider. This will enable the
user to receive SMS messages send from a mobile phone on their SIP
client. But implementing this functionality is phase 2 in my project...
I see. Well, it's possible that Kannel may already be able to handle SMS
receiving/sending protocol offered by that provider, while SER can be
extended to do bridging between SIP and Kannel's own API. The advantage
of such approach is that the resulting solution then would be able to
support any of the many SMS delivery protocols supported by the Kannel,
not only API of that particular provider. It might not be the best
approach in your particular case, but could be something worth
investigating.
Regards,
--
Maksym Sobolyev
Sippy Software, Inc.
Internet Telephony (VoIP) Experts
T/F: +1-646-651-1110
Web: http://www.sippysoft.com
MSN: [email protected]
Skype: SippySoft
_______________________________________________
Serdev mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/serdev
