MikeL has asked for the wisdom of the Perl Monks concerning the following question:

I have manually built a Plivo interface for sending txt msgs as Plivo does not provide Perl support. I've used it for years. Recently I've decided to try changing my app over to use Twilio for txt msging. I learned of the SMS:Send cpan module to do this already-made, yay!

Since I already have the code, and maybe someone else might want to use Plivo, I've taken the trouble to implement it in SMS:Send by copying the existing Twilio modules and tweaking the code for Plivo.

I've done some searching, and I've only found how to create/submit a brand-new cpan module. I just need to add a couple of source files to an existing module. Perhaps there's some tests I should add as well?

Could anyone guide me to how to download the existing bundle, so I can add my changes and upload? Also, is there a review mechanism so that I can be assured I'm not messing something up?

P.S. I have created a PAUSE account, I'm in pending status.

Replies are listed 'Best First'.
Re: adding to existing cpan module
by LanX (Saint) on Apr 11, 2023 at 00:23 UTC
Re: adding to existing cpan module
by eyepopslikeamosquito (Archbishop) on Apr 11, 2023 at 00:37 UTC
Re: adding to existing cpan module
by MikeL (Acolyte) on May 06, 2023 at 02:51 UTC
    Hi all - just thought I'd follow up.

    Plivo STILL hasn't approved my 10DLC registration, and they're still blocking my outgoing txts, and they're still charging me, etc. It's been weeks -- so F*** them.

    So I've started over with Twilio, it's nice using the pre-built SMS:Send::Twilio!

    I have taken the trouble to modularize my SMS::Send::Plivo and required WWW::Plivo:API and uploaded them to cpan via PAUSE. I wouldn't be surprised if there's problems; if there are issues I'll try to address them, but as I'm now telling Plivo to go jump in the lake, it's unlikely I'll be able to test further.

    Thanks to all you folks who pointed the way for me.

Re: adding to existing cpan module
by NERDVANA (Priest) on Apr 11, 2023 at 18:02 UTC
    I've also been using Plivo for years. Any reason for the switch? (just curious)
      Reason for switch is that Plivo keeps shutting me off!

      My txt sending app simply notifies subscribers of weather events from their own weather station - it is not marketing. Their weather station regularly uploads data to my server, which hourly analyzes their data and sends them any notifications they've opted in for, e.g. temp below 36F.

      I originally built the app for myself, on my winery&vineyard website, then over time it grew to encompass other subscribers.

      Now, with 10DLC, you must register every app with your upstream provider.

      At first they refused me due to the fact that it's on the website of an alcohol producer. Fine, at significant pain to my customers, I've moved the website to my generic webhosting URL so as to disassociate from alcohol.

      But they still just can't grasp the fact that a subscriber has to login to the website, and go to a Preferences page in order to en/dis-able their txt msging.

      I've spent many hours in moving the website and working with customers to re-configure their weather stations. I've already spent about as much money on failed attempts to get 10DLC approval as I spend on an entire year of sending txt msgs, and I'm still not approved. I'm hoping Twilio will be able to handle this better.

        Sounds like a fun project!

        I also went through the 10DLC registration on Plivo and they approved the company profile easy enough (satisfaction surveys delivered to renters on behalf of landlords), but got hung up on associating a number with a campaign. AT&T approved but T-Mobile failed it, no reason given. I removed the association and tried again, and it went through after a few days.

        Did you create the controller for "STOP" and "HELP" verbs? I'm not sure if they tested that, but I implemented those before I tried registering just to make sure I was complying with their rules.

        A different way to handle the alcohol-association problem might have been to set up a second website (can be on the same server) that only handles the Plivo SMS endpoint, and could just say stuff about weather. That way none of your users would need to reconfigure anything.