Hi Lonnie, many thanks for that. We are definitely on the same page.
Feeling similarly after writing you yesterday, I began to setup a vanilla
instance of Asterisk for the very purpose of going through the excersise of
getting acquainted with the configuration files just as you suggested. :-)

So now I have the phones calling eachother and I am working through
configuring the outbound/inbound calls.

Best regards!

Nate

On Wed, Jul 19, 2017 at 12:47 AM, Lonnie Abelbeck <li...@lonnie.abelbeck.com
> wrote:

> Hi Nate,
>
> I found the UniFi VoIP provisioning info ...
>
> UniFi VoIP - DHCP Option 66 Auto Provisioning Guide(Post 4.7)
> https://help.ubnt.com/hc/en-us/articles/213546207-UniFi-
> VoIP-DHCP-Option-66-Auto-Provisioning-Guide-Post-4-7-
>
> Taking a step back, it occurs to me you may want to just play with these
> phones and AstLinux and not necessarily auto-provisioning at this point.
>
> AstLinux requires you to understand how to configure Asterisk via text
> .conf files.  While this has a learning curve, you have full control of the
> resulting PBX, down to the finest detail.
>
> So many times reported here, "I tried the XYZ GUI, it was nice at first,
> but eventually I had to configure raw Asterisk conf files to get it the way
> I wanted".
>
> So, learn Asterisk if you have not already.  Start with configuring your
> UniFi VoIP phones via their GUI and manually add the matching SIP
> credentials in AstLinux's Asterisk.  Create a simple dialplan
> (extensions.conf) to send and receive calls.  This is a good skill to have.
>
> After you are comfortable with Asterisk, only then you may consider
> auto-provisioning the UniFi VoIP phones per the docs above.
>
> Lonnie
>
>
> On Jul 17, 2017, at 10:14 PM, Nate <nathan.p...@gmail.com> wrote:
>
> > Hi Lonnie, thanks for the response.
> >
> > The phones seem alright. I've only just begun to test them so I don't
> have very much experience with them yet. I have been through configuring
> them to work with FusionPBX and a couple different SIP providers and the
> call quality seemed decent enough; But again I'm not sure how much the
> quality reflected the phone or the SIP provider. They are Android based
> with a touch screen which makes the interface for configuring them fairly
> pleasant. They look/feel nice enough to use FWIW...
> >
> > Regarding the templates, your comments are most welcome as I had run
> diff against some of the files to see if I could get an idea of where they
> were similar and different. I'll revisit the yealink.conf to for another
> look.
> >
> > Ubiquiti has a Quick Start Provisioning Guide (PDF) online here with
> references to Asterisk and a handful of other PBX's.
> >
> > Many thanks again. I'm enjoying the introduction to this technology.
> >
> > Nate
> >
> > On Tue, Jul 18, 2017 at 2:33 PM, Lonnie Abelbeck <
> li...@lonnie.abelbeck.com> wrote:
> > Hi Nate,
> >
> > First, how do you like those phones ?
> >
> > As for the phone provisioning template file, keep in mind that only the
> [phoneprov] section is unique to the phone and possibly a few lines in the
> [general] section, take a look at templates/yealink.conf .
> >
> > Do you have any reference how the UniFi UVP phones are provisioned ?
> XML via HTTP/HTTPS ?  Naming convention for the downloaded XML files ?
> >
> > Lonnie
> >
> >
> >
> > On Jul 17, 2017, at 7:29 PM, Nate <nathan.p...@gmail.com> wrote:
> >
> > > Good day everyone,
> > >
> > > I'm a system admin just getting started with SIP/PBX/VoIP technology.
> > >
> > > I have the SIP trunk setup and am now just trying to get a couple of
> UniFi UVP phones configured to test with.
> > >
> > > I've read the docs on IP Phone Provisioning Getting Started, and IP
> Phone Mass Deployment but neither is clear on what to do if there the
> phones you have are not included with the default templates and looking at
> the templates it appeared they all had specific settings for their
> respective phones. I also didn't see a generic template to use as a
> boilerplate either.
> > >
> > > Can anyone please help clarify what I should do to create a template
> for these phones?
> > >
> > > Many many thanks in advance,
> > >
> > > Nate.
> >
> >
> >
> >
> > ------------------------------------------------------------
> ------------------
> > Check out the vibrant tech community on one of the world's most
> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> > _______________________________________________
> > Astlinux-users mailing list
> > Astlinux-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/astlinux-users
> >
> > Donations to support AstLinux are graciously accepted via PayPal to
> pay...@krisk.org.
> >
> > ------------------------------------------------------------
> ------------------
> > Check out the vibrant tech community on one of the world's most
> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot______
> _________________________________________
> > Astlinux-users mailing list
> > Astlinux-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/astlinux-users
> >
> > Donations to support AstLinux are graciously accepted via PayPal to
> pay...@krisk.org.
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Astlinux-users mailing list
> Astlinux-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to
> pay...@krisk.org.
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Astlinux-users mailing list
Astlinux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to 
pay...@krisk.org.

Reply via email to