Fwd: [RestComm] Restcomm SMPP Connector for SMSCGateway (v5.X/v3.X) (#260)

[Amit Bhayani]

Hi,

We want to add SMPP capability in RestComm for it to easily connect to SMSC. Any one up for challenge? 

James,

Since you have been already working on Mobicents SMSC, its same SMPP code that we can port to RestComm. Want to give it a try? I can provide help for same.

Thanks and Regards,

Amit.

---------- Forwarded message ----------
From: jfcvm <notifi...@github.com>
Date: Wed, May 20, 2015 at 11:21 PM
Subject: [RestComm] Restcomm SMPP Connector for SMSCGateway (v5.X/v3.X) (#260)
To: Mobicents/RestComm <Rest...@noreply.github.com>

Currently, only SIP connector exists for Restcomm/SMSC connectivity. SMPP is more ideal for a telecomm infrastructure. Target SMPP versions using Cloudhopper SMPP are v5.x and v3.x.

—
Reply to this email directly or view it on GitHub.

[Ibrahima Gaye]

+1

for volenteering :)

regards,

​

------

Ibrahima GAYE,
Senior Project Management support
mob:

     +223  9  117 1464

     +221 77 564 9358 

My profiles: 

If you received this email in error, please notify us immediately by sending an e-mail or by calling.

 

 

--
You received this message because you are subscribed to the Google Groups "mobicents-public" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mobicents-publ...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[James Carpenter]

Absolutely, we were discussing this in todays meeting. I would love to do my best, but I will have a lot to learn. I was told gvag can assist in getting started. Although, you are right, the code is quite similar.

Please ping me on hangouts if anyone would like to discuss where to begin.

v/r,

James

--

PGP Key Fingerprint:

798F FF6C 0E2F F63A FF70

D18B 378F DF44 EE74 0FDC

PGP Public Encryption Key available via

appropriate PGP Key Server distribution sites

Key ID: 0xEE740FDC

[James Carpenter]

Hi Amit,

Not sure my email response made it, but yes, absolutely. It would be my pleasure and a great starting point for learning. 

So the current smscgateway SMPP connector can be ported to Restcomm? That is, the v3 cloudhopper for now right? 

Can you provide Ibrahim and I advice on where start looking in the current code and where the code will be ported to in Restcomm?

v/r

James

[Ibrahima Gaye]

Hello Amit,
for some mobicents projects we could use mvn mobicents:eclipse to create an eclipse project but that doen't work for Restcomm shall we import it as existing maven project ?

Best regards,

​

------

Ibrahima GAYE,
Senior Project Management support
mob:

     +223  9  117 1464

     +221 77 564 9358 

My profiles: 

If you received this email in error, please notify us immediately by sending an e-mail or by calling.

 

 

[Jean Deruelle]

You can use mvn eclipse:eclipse in the restcomm directory. that works.

Jean

[Ibrahima Gaye]

thank you that works

[James Carpenter]

Good question Ibrahim, I would have never known about it had you not asked :)

Also, I've been skewering through all of the existing ch-smpp client code in smscgateway to get an understanding of how it will intertwine with Restcomm; however, when digging into the Restcomm code, I am a little confused as to how the connector should be embedded as compared with smscgateway.

1. Is is accurate to implement the SMPP connector in a similar manner as the SIP connector?

2. Can anyone recommend an accurate test flow (or simulation tools) for Restcomm when testing the SMPP connector once embededed? i.e. Would it be as simple as connecting to Restcomm and using it in the same manner as the SIP connector from the UE perspective?

Thanks in advance and apologies for the simple questions, I'm hoping to ensure my understanding is clear before altering any code. Any other direction/recommendations/experiences would be welcome as well and appreciated :)

v/r

James

[Ibrahima Gaye]

Hi,

Just to jump on James' email ...

i failed to understand the structure (conceptual wise) of the current code regarding connectors. After using some code analyzers (nwire for java) i cannot find a clear usage of "connectors" as separted down-level-components invoked by upper-level-components in order to copy the logic.

Anyone can help on this?

Best regards,

​

------

Ibrahima GAYE,
Senior Project Management support
mob:

     +223  9  117 1464

     +221 77 564 9358 

My profiles: 

If you received this email in error, please notify us immediately by sending an e-mail or by calling.

 

 

--

[James Carpenter]

Update here for the SMPP connector:

Have yet to hear from anyone since the meeting and am unsure how to proceed. I could get it to work via SMPP by tying in the sms api (already have, only unbound sessions if hits aggregator), but it is spaghetti code, hacky and won't be accepted anyway. Been attempting to figure out the bootstrap in the sense of restcomm, as I don't know how to *properly* bind the connection on start and spin up the clientOpsThread. But, as I said in the beginning, without direction the project is just over my head; as it relates to *proper* integration with RestComm especially. I did learn how to spin up an SMPP server/client/router in java and c#  :)

Anyway, someone else can take a crack at it, as I am beginning to understand the dynamics between Mobicents and TeleStax. An SMSC without store and forward lol

Lastly, I still haven't heard from TADHack, Bandwidth, Nexmo, or any other entity about developer resource access. Given that this is required for judging, what hopes does the little guy really have? lol rhetorical. Good luck everyone.

[Ivelin Ivanov]

James,
I thought you've been chatting with Amit on SMPP connector design. I will ping George and Amit to help with direction.
What specifically are you missing for your TADHack application? Copy of Restcomm?connectivity to Bandwidth?
Ivelin

--

[James Carpenter]

Hello Ivelin,

No not really, but it is okay. No worries, I understand everyone's busy with life's more important obstacles, we're just volunteers. Besides, wouldn't want the big boss to force volunteer work ;) 

From my understanding, the TADHack is judged by the quotes below, but most of the dev resources listed require accts. How can I access they're APIs or resources for use in the hack? Any of them, preferably  I was looking at the SMS/MMS stuff to play with it and see if I can add features/functionality this week rather than a simple ESME client to server connection :D  Wish I had more time to prepare for something more clever... but I am happy, as I've learned so much in the last couple weeks, so many different components, it's pretty cool.

• "List the sponsor’s resources used in the hack (which sponsors should judge your hack)" - Alan Quayle
• "Compelling use of the Sponsors Technologies and Tools" - Winner Selection / Judging Criteria

List of Resources: Apidaze, Bandwidth, Dialogic, hSenidMobile, Ericsson, forge by Acision, Intel, Matrix, Oracle, Telestax, Tropo, Truphone

v/r

James

[Amit Bhayani]

Hi James,

Sorry, this is coming late than we initially targeted for. 

I have forked the code at https://github.com/abhayani/RestComm and created new branch smpp. 

Initial code is added where SMPP library is already integrated. SMS does arrive in RestComm via SMPP library now. However once it arrives in RestComm, it should be persisted in database using DAO and forwarded to App is still missing. 

Please feel free to sync the code and give it a try.

Thanks and Regards,

Amit.

On Sun, Jun 7, 2015 at 10:10 AM, Ivelin Ivanov <ivelin...@telestax.com> wrote:

I am pretty sure you will get feedback on the Restcomm-SMPP code by Monday.

I will answer the TADHack question on the dedicated thread and copy you.

---

​--​

Ivelin Ivanov 

Co-Founder, Telestax, Inc. 

Founder, Mobicents

+1 (512) 970-3297
@ivelini

http://www.telestax.com/blog/

https://www.youtube.com/c/TeleStax

Lets meet at:

TADHack Global, June 13-14, Lisbon, Buenos Aires, and Raleigh

--
You received this message because you are subscribed to the Google Groups "restcomm" group.
To unsubscribe from this group and stop receiving emails from it, send an email to restcomm+u...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "restcomm" group.
To unsubscribe from this group and stop receiving emails from it, send an email to restcomm+u...@googlegroups.com.