<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>LaForge's home page (Posts about sms)</title><link>https://laforge.gnumonks.org/</link><description></description><atom:link href="https://laforge.gnumonks.org/blog/tags/sms.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><lastBuildDate>Thu, 24 Oct 2024 20:08:49 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Anyone interested in supporting SMPP interworking at 32C3?</title><link>https://laforge.gnumonks.org/blog/20151206-32c3-smpp/</link><dc:creator>Harald Welte</dc:creator><description>&lt;p&gt;Sylvain brought this up yesterday:  Wouldn't it be nice to have some
degree of SMS interfacing from OpenBSC/OsmoNITB to the real world at
32C3?  It is something that we've never tried so far, and thus
definitely worthy of testing.&lt;/p&gt;
&lt;p&gt;Of course, full interworking is not possible without assigning public
MSISDN to all internal subscribers / 'extensions' how we call them.&lt;/p&gt;
&lt;p&gt;But what would most certainly work is to have at least outbound SMS
working by means of an external SMPP interface.&lt;/p&gt;
&lt;p&gt;The OsmoNITB-internal SMSC speaks SMPP already (in the SMSC role), so we
would need to implement some small amount of glue logic that behaves as
ESME (external SMS entity) towards both OsmoNITB as well as some
public SMS operator/reseller that speaks SMPP again.&lt;/p&gt;
&lt;p&gt;Now of course, sending SMS to public operators doesn't come for free.
So in case anyone reading this has access to SMPP at public operators,
resellers, SMS hubs, it would be interesting to see if there is a chance
for some funding/sponsoring of that experiment.&lt;/p&gt;
&lt;p&gt;Feel free to contact me if you see a way to make this happen.&lt;/p&gt;</description><category>ccc</category><category>gsm</category><category>openbsc</category><category>osmocom</category><category>sms</category><guid>https://laforge.gnumonks.org/blog/20151206-32c3-smpp/</guid><pubDate>Sat, 05 Dec 2015 16:00:00 GMT</pubDate></item><item><title>python-libsmpp works great with OsmoNITB</title><link>https://laforge.gnumonks.org/blog/20151205-python-libsmpp/</link><dc:creator>Harald Welte</dc:creator><description>&lt;p&gt;Since 2012 we have support for SMPP in OsmoNITB (the network-in-the-box
version of OpenBSC).  So far I've only used it from C and Erlang code.&lt;/p&gt;
&lt;p&gt;Yesterday I gave python-smpplib from
&lt;a class="reference external" href="https://github.com/podshumok/python-smpplib"&gt;https://github.com/podshumok/python-smpplib&lt;/a&gt; a try and it worked like a
charm.  Of course one has to get the details right (like numbering plan
indication).&lt;/p&gt;
&lt;p&gt;In case anyone is interested in interfacing OsmoNITB SMPP from python,
I've put a working example to send SMS at &lt;a class="reference external" href="http://cgit.osmocom.org/mncc-python/tree/smpp_test.py"&gt;http://cgit.osmocom.org/mncc-python/tree/smpp_test.py&lt;/a&gt;&lt;/p&gt;</description><category>gsm</category><category>osmocom</category><category>smpp</category><category>sms</category><guid>https://laforge.gnumonks.org/blog/20151205-python-libsmpp/</guid><pubDate>Fri, 04 Dec 2015 16:00:00 GMT</pubDate></item></channel></rss>