[Spce-user] Using API for subscriber control

Pedro Guillem pedro.guillem at gmail.com
Mon Nov 24 16:16:26 EST 2014


Indeed i will. The password algorithm is the apache2 standard.

... by any chance, does anybody knows of a PHP example to call this
functions over XML-RPC ?

I haven´t used xml-rpc since i was 21 hahaha.. (i´m 31 now, so 10 years). I
might be a little rusted.

Pedro

On Mon, Nov 24, 2014 at 4:04 PM, Kevin Masse <kmasse at questblue.com> wrote:

> Pedro, that sounds correct.
>
> Make sure you have created your credentials in order to login in the
> config.yml
>
>
>
> Thanks
>
> Kevin
>
>
>
>
>
> *From:* Pedro Guillem [mailto:pedro.guillem at gmail.com]
> *Sent:* Monday, November 24, 2014 4:04 PM
>
> *To:* Kevin Masse
> *Cc:* spce-user
> *Subject:* Re: [Spce-user] Using API for subscriber control
>
>
>
> I read the handbook of version 3.1 (ossbss section) and it points to the
> SOAP interface and how to use it.
>
> Inside the WSDL site itself is the documentation for each function. It´s
> packed along with the server.
>
>
>
> Page 87 of 101 states:
>
> Access https://<ip>:2443/SOAP/Provisioning.wsdl and login with your new
> credentials
>
>
>
> I´ll report further questions, if any.
>
> I hope this is the right interface.
>
>
>
> Thanks a lot!
>
> Pedro
>
>
>
> On Mon, Nov 24, 2014 at 3:29 PM, Kevin Masse <kmasse at questblue.com> wrote:
>
> Hello Pedro, I do not have the link for version 3.1
>
>
>
> We need to send this back to the group.  I have a 2.8 but you need to be
> sure the API is the same so let’s let the group answer that 3.1 part.
>
>
>
> Kevin
>
>
>
>
>
> *From:* Pedro Guillem [mailto:pedro.guillem at gmail.com]
> *Sent:* Monday, November 24, 2014 3:28 PM
> *To:* Kevin Masse
> *Cc:* spce-user
> *Subject:* Re: [Spce-user] Using API for subscriber control
>
>
>
> Thanks for the quick reply Kevin.
>
> I imagined this would be a feature long taken care of.
>
>
>
> I haven´t checked the API, could you please post a link for version 3.1 ?
>
>
>
> Cheers
>
> Pedro
>
>
>
> On Mon, Nov 24, 2014 at 2:56 PM, Kevin Masse <kmasse at questblue.com> wrote:
>
> Good afternoon Pedro, you would want to use the SOAP / API Provisioning to
> do this.
>
> It is a simple command that will have different lock options (Global)
> (Outbound) etc.
>
>
>
> Have you reviewed the API for your package version?
>
>
>
> Kevin
>
>
>
>
>
> *From:* Spce-user [mailto:spce-user-bounces at lists.sipwise.com] *On Behalf
> Of *Pedro Guillem
> *Sent:* Monday, November 24, 2014 2:55 PM
> *To:* spce-user
> *Subject:* [Spce-user] Using API for suscriber control
>
>
>
> Hello guys
>
>
>
> I was wondering if there is a "single liner" or ngcp-* script to
> temporally enable or disable a suscriber?. I mean specifically to restrict
> outgoing calls.
>
>
>
> I do know there are some perl scripts for creating a new suscriber and
> even for "terminating" it, but not for temporally disabling a suscriber.
>
>
>
> If its easier to modify a table row to perform this, it's also a solution.
>
>
>
> Any ideas
>
> Pedro Guillem
>
>
>
>
>
>
>
>
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20141124/8c5395c0/attachment-0001.html>


More information about the Spce-user mailing list