[Spce-user] Using API for subscriber control
Kevin Masse
kmasse at questblue.com
Mon Nov 24 15:29:55 EST 2014
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/ff487469/attachment-0001.html>
More information about the Spce-user
mailing list