[Spce-user] Provisioning

Skyler skchopperguy at gmail.com
Fri Apr 5 22:42:17 EDT 2013


Oh, hehe. Asterisk, right. Thanks Jeremie. ;)

On 4/5/2013 6:26 PM, Jeremie Chism wrote:
> PIAF is PBX in a flash which is an offshoot of freepbx. It uses endpoint manager which was developed by the guy that did provisioner.
>
> Sent from my iPhone
>
> On Apr 5, 2013, at 7:32 PM, Skyler <skchopperguy at gmail.com> wrote:
>
>> Hi Mike,
>>
>> Thanks for keeping this to the list first, before going off-line.
>>
>> Not sure what PIAF means, this project is more of an in-development scenario with focus on spce. If you are comfortable with provisioning end-point devices in general I'm sure you are welcome to join in to offer your experience and suggestions on how to make this great.
>>
>> Drop me an email off-list.
>>
>> Skyler
>>
>> On 4/5/2013 4:33 PM, sipwise at ics-il.net wrote:
>>> I am looking to start testing SIPWise soon and would miss the provisioning in PIAF, so I'd love to give my feedback on it.
>>>
>>>
>>>
>>> -----
>>> Mike Hammett
>>> Intelligent Computing Solutions
>>> http://www.ics-il.com
>>>
>>> ----- Original Message -----
>>> From: "Skyler" <skchopperguy at gmail.com>
>>> To: "Oren Yehezkely" <orenyny at gmail.com>
>>> Cc: spce-user at lists.sipwise.com
>>> Sent: Friday, April 5, 2013 4:52:07 PM
>>> Subject: Re: [Spce-user] Provisioning
>>>
>>> Hi Oren,
>>>
>>>    Ya I briefly looked at that a while after seeing Jeremie's post.
>>>
>>>    It looks great, though I'm hoping to guide into a solution that can
>>> fully integrate with spce. Maybe fork? Not sure yet, going to play
>>> around with some ideas.
>>>
>>>    If you'd like to participate, drop an email and I'll get you into our
>>> thread on this.
>>>
>>> Skyler
>>>
>>> On 4/2/2013 2:08 AM, Oren Yehezkely wrote:
>>>> Skyler,
>>>>
>>>> Did you check provisioner.net <http://provisioner.net>?
>>>>
>>>> I am looking into implementing it as well.
>>>>
>>>> Oren
>>>>
>>>>
>>>> On Mon, Apr 1, 2013 at 8:51 PM, Skyler <skchopperguy at gmail.com
>>>> <mailto:skchopperguy at gmail.com>> wrote:
>>>>
>>>>      Communication is needed for sure, to get us on the same track. Email
>>>>      is my preferred choice but I guess we could start with a call if you
>>>>      need that. Sure.
>>>>
>>>>        I'll await the contact off-list to trade info.
>>>>
>>>>      Skyler
>>>>
>>>>
>>>>      On 4/1/2013 5:31 PM, Kevin Masse wrote:
>>>>
>>>>          I agree with all of your comments, I should have a mix of Yealink,
>>>>          Aastra, Grandstream, Linksys by Cisco brands.
>>>>
>>>>          I will not normally have a lot of ATA's on hand but the process
>>>>          will be
>>>>          the same.
>>>>
>>>>          Additionally I wouldn't mind putting a call together with you and
>>>>          Jeremie.  I just PM'd Jeremie outside the list to offer the same
>>>>          as you
>>>>          just suggested.  Once he gets back to me we can set up a call to
>>>>          collaborate and update the list on our successes.
>>>>
>>>>          Kevin
>>>>
>>>>
>>>>
>>>>
>>>>          -----Original Message-----
>>>>          From: Skyler [mailto:skchopperguy at gmail.com
>>>>          <mailto:skchopperguy at gmail.com>__]
>>>>          Sent: Monday, April 01, 2013 8:25 PM
>>>>          To: Kevin Masse
>>>>          Cc: Jeremie Chism; spce-user at lists.sipwise.com
>>>>          <mailto:spce-user at lists.sipwise.com>
>>>>          Subject: Re: [Spce-user] Provisioning
>>>>
>>>>          Hi Kevin,
>>>>
>>>>          On 4/1/2013 5:11 PM, Kevin Masse wrote:
>>>>
>>>>              Greetings, one way one might consider auto provisioning
>>>>              would be to
>>>>              use a tftp server.
>>>>
>>>>              This can reside on any stand alone server.
>>>>
>>>>
>>>>              Hrm, would this be secure if we are talking about a server
>>>>          which is
>>>>          exposed to the net from a datacenter? I do tftp locally but behind
>>>>          firewall.
>>>>
>>>>              If you are using provisioning via SOAP or XML into Sipwise
>>>>              you could
>>>>              add another process that places a tftp configuration of the
>>>>              device you
>>>>
>>>>
>>>>              want to register into that server as another routine.
>>>>
>>>>
>>>>              I think to start, might be better to forget about the
>>>>          SOAP/XMLRPC and
>>>>          look more towards the basic concept. Like, add device provision
>>>>          controls
>>>>          into Admin area which then stores to DB and then from there,
>>>>          anything
>>>>          can happen.
>>>>
>>>>              Send out your ATA's or IP telephones with only the configuration
>>>>              server address in the settings.  They will then pull their
>>>>              configuration from the tftp server and the settings will
>>>>              tell it to
>>>>
>>>>          register to Sipwise.
>>>>
>>>>
>>>>
>>>>              That makes sense, though exposing tftp to the world is
>>>>          dangerous.
>>>>          Wouldn't http/s be better here?
>>>>
>>>>              Now, if you are not automating this, simply build the
>>>>              provisioning
>>>>              file and place it on the tftp server manually and it should
>>>>              all still
>>>>
>>>>          work.
>>>>
>>>>
>>>>
>>>>              Ya, I'm thinking automated for sure. Dynamically though.
>>>>
>>>>              Essentially all it is doing is providing information for
>>>>              your Sipwise
>>>>              server.  Most provisioning would be in a file mac-address.cfg
>>>>
>>>>              Download the template for your device from the manufacturer
>>>>              of the
>>>>              device or program one and export the xml from it to use as a
>>>>              template
>>>>              for provisioning.
>>>>
>>>>              I hope this helps.
>>>>
>>>>              Kevin
>>>>
>>>>
>>>>
>>>>              Feel free to join Jeremie and I, what target device(s) do
>>>>          you have
>>>>          on-hand there for testing?
>>>>
>>>>          Skyler
>>>>
>>>>
>>>>
>>>>              -----Original Message-----
>>>>              From: spce-user-bounces at lists.__sipwise.com
>>>>              <mailto:spce-user-bounces at lists.sipwise.com>
>>>>              [mailto:spce-user-bounces at __lists.sipwise.com
>>>>              <mailto:spce-user-bounces at lists.sipwise.com>] On Behalf Of
>>>>              Jeremie
>>>>              Chism
>>>>              Sent: Monday, April 01, 2013 8:04 PM
>>>>              To: Skyler
>>>>              Cc: spce-user at lists.sipwise.com
>>>>              <mailto:spce-user at lists.sipwise.com>
>>>>              Subject: Re: [Spce-user] Provisioning
>>>>
>>>>              Absolutely.
>>>>
>>>>              Sent from my iPhone
>>>>
>>>>              On Apr 1, 2013, at 6:36 PM, Skyler <skchopperguy at gmail.com
>>>>              <mailto:skchopperguy at gmail.com>> wrote:
>>>>
>>>>                  Jeremie,
>>>>
>>>>                  Since you started the thread on this a month or so ago;
>>>>                  Where are you
>>>>
>>>>              at with evaluations? I have some time this coming 3.5 weeks
>>>>              (slowing
>>>>              down) and I'm looking for a small collaborated project.
>>>>              Interested in
>>>>              bringing a solid/tested example to future releases?
>>>>
>>>>
>>>>                  Skyler
>>>>
>>>>                  On 3/30/2013 12:58 PM, Jeremie Chism wrote:
>>>>
>>>>                      Ata provisioning is not built into sipwise. You
>>>>                      would need to
>>>>                      develop
>>>>
>>>>
>>>>                      your own system. We are looking at several options
>>>>                      but have not
>>>>                      settled on one.
>>>>
>>>>                      Sent from my iPhone
>>>>
>>>>                      On Mar 30, 2013, at 2:35 PM, sipwise at ics-il.net
>>>>                      <mailto:sipwise at ics-il.net>
>>>>                      <mailto:sipwise at ics-il.net
>>>>                      <mailto:sipwise at ics-il.net>> wrote:
>>>>
>>>>                          The only references I saw in Google about
>>>>                          provisioning in SIPWise
>>>>                          were to the raw information the end-user could
>>>>                          provision their
>>>>
>>>>              device with.
>>>>
>>>>
>>>>                          Is there any provisioning system built-in?
>>>>
>>>>                          If not, what are people using for this?
>>>>
>>>>                          What I'm talking about is the end-user ATA
>>>>                          fetches a config from
>>>>                          the
>>>>
>>>>
>>>>                          server that is propagated with
>>>>                          username\password, server address,
>>>>
>>>>              etc.
>>>>
>>>>
>>>>
>>>>
>>>>                          -----
>>>>                          Mike Hammett
>>>>                          Intelligent Computing Solutions
>>>>                          http://www.ics-il.com
>>>>
>>>>                          _________________________________________________
>>>>                          Spce-user mailing list
>>>>                          Spce-user at lists.sipwise.com
>>>>                          <mailto:Spce-user at lists.sipwise.com>
>>>>                          <mailto:Spce-user at lists.__sipwise.com
>>>>                          <mailto:Spce-user at lists.sipwise.com>>
>>>>                          http://lists.sipwise.com/__listinfo/spce-user
>>>>                          <http://lists.sipwise.com/listinfo/spce-user>
>>>>
>>>>
>>>>
>>>>                      _________________________________________________
>>>>                      Spce-user mailing list
>>>>                      Spce-user at lists.sipwise.com
>>>>                      <mailto:Spce-user at lists.sipwise.com>
>>>>                      http://lists.sipwise.com/__listinfo/spce-user
>>>>                      <http://lists.sipwise.com/listinfo/spce-user>
>>>>
>>>>
>>>>                  _________________________________________________
>>>>                  Spce-user mailing list
>>>>                  Spce-user at lists.sipwise.com
>>>>                  <mailto:Spce-user at lists.sipwise.com>
>>>>                  http://lists.sipwise.com/__listinfo/spce-user
>>>>                  <http://lists.sipwise.com/listinfo/spce-user>
>>>>
>>>>
>>>>              _________________________________________________
>>>>              Spce-user mailing list
>>>>              Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com>
>>>>              http://lists.sipwise.com/__listinfo/spce-user
>>>>              <http://lists.sipwise.com/listinfo/spce-user>
>>>>
>>>>
>>>>      _________________________________________________
>>>>      Spce-user mailing list
>>>>      Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com>
>>>>      http://lists.sipwise.com/__listinfo/spce-user
>>>>      <http://lists.sipwise.com/listinfo/spce-user>
>>>
>>> _______________________________________________
>>> Spce-user mailing list
>>> Spce-user at lists.sipwise.com
>>> http://lists.sipwise.com/listinfo/spce-user
>>>
>>> _______________________________________________
>>> Spce-user mailing list
>>> Spce-user at lists.sipwise.com
>>> http://lists.sipwise.com/listinfo/spce-user
>>
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> http://lists.sipwise.com/listinfo/spce-user




More information about the Spce-user mailing list