nguyenbahuong / smslib

Automatically exported from code.google.com/p/smslib
0 stars 0 forks source link

SMPP support #130

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
 Any plan to support direct SMSC connections, mainly via SMPP, and maybe 
other protocols too (UCP, CIMD etc). There are several open java libraries 
for SMPP, but smslib's point would be to provide common API layer for 
them; it would be then something like Kannel or Nowsmsc.

Original issue reported on code.google.com by jaak.lai...@gmail.com on 29 Sep 2008 at 9:54

GoogleCodeExporter commented 9 years ago
Hi,

Indeed, there are various open source SMPP libs out there which could be added 
in 
SMSLib. I have thought several times about adding such a library, but...

Read this: http://groups.google.com/group/SMSLib/msg/f19e4c5602c21e2a

My problem is that I cannot find an SMPP provider which would give me SMPP 
access 
for a reasonable fee.

On the other hand, I could add such a library and work with an emulator, but at 
the 
end I could not really support it. Emulators are nice but I should have real 
access 
in order to support something I have developed / integrated.

Any feedback on this issue will be much appreciated :)

Original comment by ad...@smslib.org on 29 Sep 2008 at 10:56

GoogleCodeExporter commented 9 years ago

Original comment by ad...@smslib.org on 30 Sep 2008 at 6:05

GoogleCodeExporter commented 9 years ago
Hi. I gave a little thought to this issue.
SMSLib project is big enough to be separated into components - not only in
issue-tracking system, but physically (SMSServer is sophisticated app by itself 
to
become something independent; and adding Jetty dependency already). Maybe it 
worth
separating SMSLib into, well, SMSLib itself, SMSServer and incubating 
components.
SMPP gateway is first candidate to make it into incubator. After SMPP gateway 
starts
working reliably with emulator - it can be made publicly available for testing 
and
further adaptation. And after 2-3 successful integrations it can be committed to
SMSLib or into, for example, 'adapters'/'gateways' project to be maintained by 
those
who use them.

I think it is far better choice for those who need SMPP integration, but can't 
find
something working to start from.

Our managers are constantly asking me about SMPP support, but don't want to 
start
project to be developed from ground (far better to sell something already made 
by
someone else. Much higher profit, you see :) ) I doubt our project managers will
resist temptation to start project from 'testing' phase directly ;)

Original comment by allat...@gmail.com on 13 Oct 2008 at 8:56

GoogleCodeExporter commented 9 years ago

Original comment by T.Delenikas on 17 Oct 2008 at 7:30

GoogleCodeExporter commented 9 years ago

Original comment by ad...@smslib.org on 31 Oct 2008 at 8:47

GoogleCodeExporter commented 9 years ago
Separating SMSServer and SMSLib is a great idea. It would be even greater if 
SMSLib
could expose a generic interface to program against, shielding all the details 
of
underlying gateways/interfaces. SMSServer in itself would then be a client of 
SMSLib
and add relaying capabilities. 

Original comment by all...@gmail.com on 10 Nov 2008 at 10:44

GoogleCodeExporter commented 9 years ago
Hello Alleey,

Can you please elaborate on the "generic interface" issue?
Why do you think that the existing methods are not good enough?

Original comment by ad...@smslib.org on 10 Nov 2008 at 11:04

GoogleCodeExporter commented 9 years ago

Original comment by T.Delenikas on 24 Nov 2008 at 2:58

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
Good day.

It seems that I finally got "all-go" for implementing SMPP support. I looked 
through
several free-open-source implementations, but all of them are quite old and 
stuck on
phase "SMPP v5.0 in mid 2008". However, widely used v3.4 is supported by most of
them. OpenSMPP hosted on sourceforge [1] seems good place to start, but it is
licensed under LGPL. Won't there be any licensing issues in using it in SMSLib? 
I
think I'll have to modify it a little (if at all) to fit into SMSLib's gateway
interface...

Maybe you have any proposals about another SMPP projects worth looking at? I'll 
be
gratefull!

[1] http://smstools.wiki.sourceforge.net/

Edited:
I'll have SMPP connection available really soon, so I can assist you in 
testing, if
that is all that stops you now (according to comment 1) :)

Original comment by allat...@gmail.com on 21 Jan 2009 at 9:24

GoogleCodeExporter commented 9 years ago
Hi,

I am not very sure that LPGL and Apache go well together... I think they 
should(?).

I know this project: http://code.google.com/p/jsmpp/ Its Apache licensed, so 
from (at
least) this point, its perfect. Never tried it though... It has its own PDU 
library,
we have our own. I don't know how easy would be to "strip" jsmpp and use Jeff's 
PDU
library instead...

Original comment by T.Delenikas on 22 Jan 2009 at 7:31

GoogleCodeExporter commented 9 years ago
SMPP and GSM3040 PDU headers structure and coding methods are very different. 
At the
first glance, I don't think PDU from this two specs have much in common, but 
I'll
look further.

Original comment by allat...@gmail.com on 22 Jan 2009 at 9:05

GoogleCodeExporter commented 9 years ago
Hmm... I thought that the PDU block encoding is the same(?)
Headers are certainly different.

Original comment by T.Delenikas on 22 Jan 2009 at 9:55

GoogleCodeExporter commented 9 years ago
I thought you was talking about completely replacing JSMPP PDU creation code 
with
SMSLib one. User data encoding can be reused, I think.

Original comment by allat...@gmail.com on 22 Jan 2009 at 11:04

GoogleCodeExporter commented 9 years ago
Hi,

Is there any progress on the SMPP issue?
I am planning on spending some time integrating the jsmpp library and test with 
the 
emulator. If you are spending time on this, I can hold back :)

Original comment by T.Delenikas on 5 Feb 2009 at 11:14

GoogleCodeExporter commented 9 years ago
Hi.

No, currently I don't have time on this. But I think it will be my next 
assignment. I
was busy fixing MC35i support (this device pisses me off), tuning SMSLib 
threads and
working on another project. So I'm literaly 1-2 weeks away from starting work 
on SMPP.

Original comment by allat...@gmail.com on 5 Feb 2009 at 10:31

GoogleCodeExporter commented 9 years ago

Original comment by T.Delenikas on 18 Feb 2009 at 7:50

GoogleCodeExporter commented 9 years ago

Original comment by ad...@smslib.org on 4 Apr 2009 at 1:00

GoogleCodeExporter commented 9 years ago

Original comment by T.Delenikas on 21 Apr 2009 at 9:08

GoogleCodeExporter commented 9 years ago
Almost an year. Is any one is working on SMPP integration??
Any progress ...

Original comment by pratyush...@gmail.com on 16 Feb 2010 at 10:22

GoogleCodeExporter commented 9 years ago

Original comment by ad...@smslib.org on 16 Mar 2010 at 8:51

GoogleCodeExporter commented 9 years ago

Original comment by T.Delenikas on 31 Mar 2010 at 6:46

GoogleCodeExporter commented 9 years ago
First attempt for SMPP support. SMSLib uses the jsmpp library 
(http://code.google.com/p/jsmpp/) for SMPP support.

http://smslib.googlecode.com/svn/smslib/branches/smpp/

Original comment by T.Delenikas on 17 Apr 2010 at 7:18

GoogleCodeExporter commented 9 years ago

Original comment by T.Delenikas on 17 Apr 2010 at 7:18

GoogleCodeExporter commented 9 years ago
SMPP support added in SMSLib v3.4.6

Original comment by T.Delenikas on 27 Apr 2010 at 6:45

GoogleCodeExporter commented 9 years ago

Original comment by T.Delenikas on 29 Apr 2010 at 8:27