Thirdlane PBX Manager 6.1.1.7 is available

I loaded the latest ST ISO (Not Beta) and upgraded PBX manager to 6.1.1.7 but still don't see the options for specifying provisioning directory so the provisioning files are not being generated. Did I miss something? Should I use the Beta ISO instead.

For me, it looks like the specific patch to fix the provisioning directory option did not fix my installation. I also see this same issue on another system we are putting in production this comming Friday. This is a Law Office and I don't what to upset them. Please help or point me in the right direction.

Thanks. Any help would be apreaciated.

Denis

Denis,

For the installations that used ISO 2.0 you no longer need to specify provisioning directory since regardless of the provisioning method (http, ftp or tftp) the same directory (/home/PlcmSpIp) is used for provisioning. While it is Polycom specific name (to make it easier to install Polycom firmware) it works the same for all the phones.

I am brand new to Thirdlane so try to be nice. Fortunately I have been working with asterisk and polycom's for 3 years so I have a little background.

Here is my issue:

I just downloaded and installed the Multi-Tenant 2.0 ISO version (PBX Manager 6.1.1.6) and loaded it into a VM with an internal IP address of 192.168.1.70. The System Settings-> Provisioning Settings is set to "192.168.1.70". But now I am stuck at attempting to set up the first Polycom 550.

I have configured an extension and set up a MAC Address for a 550 for auto-provisioning. I have confirmed that there are polycom config files in /home/PlcmSpIp.

But now I am making some rabid assumptions that there is nothing else I need to do other than to log into the Polycom phone and set the Polycom Server type to "HTTP" and set the address "192.168.1.170".

Assumptions being what they are, it isn't working. The Polycom can't contact the boot server to get it's configuration (it is on the same internal lan segment).

What am I missing? Are there other things I need to configure , download, or manually edit on the Thirdlane server in order get the polycom to boot? Or does the server address need a specific directory on it?

Thanks,
Karl Kacerek

for starters theres a few problems with this statement

I just downloaded and installed the Multi-Tenant 2.0 ISO version (PBX Manager 6.1.1.6) and loaded it into a VM with an internal IP address of 192.168.1.70.

one being NAT, another using a VM.

I am just testing so I'm not too concerened with voice quality. I am assuming I'll have issues with RTP streams through the VM but I just wanted to deploy Thirdlane in a VM environment first to test basic functionality like install, creating extensions, and provisioning phones.

Thirlane installs beautifully and runs great. I provisioned a SNOM 300 manually to an extension and it works fine.

I am very aware of NAT problems. I've worked with Asterisk/Sip and NAT for 3 years and have 40 customers and 100s of extensions running double NAT. Pain in the butt but it can work.

That all said, the VM is operational on my internal network and the SNOM is provisioned. I'm just trying to figure out what the polycom HTTP address should be set to and if there is anything else I need to do to set up the auto-provisioning server to serve up Polycom HTTP.

if you are provisioning polycom phones you want to use ftp provisioning. HTTP provisioning is a matter of knowing the full URL to provision, but you're missing out on some of the biggest polycom advantages if you dont use FTP provisioning.

Thanks. I am very familiar with Polycom FTP.

Am I correct to assume I need to manually configure the FTP server in my Thirdlane CentOS deployment to point to /home/plcmspip and to manually add users that can access it?

Also, am I correct to assume I need to manually download my preferred Polycom Bootrom and SIP.LD files from Polycom and place them into /home/plcmspip?

its already done in the ISO, the user/pass is PlcmSpIp (polycom default) .. the directory structure is designed in a way that even knowing the password (no bigger risk than TFTP or HTTP since they require no passwords) does not allow indexing, therefore you have to know the filename in order to retrieve it.

if you know how to make full use of DHCP options, you literally wont have to make any changes to the phones when you take them out of the box.

Thanks Erik, FTP works like a charm.

(Well, after I figured out I was getting blocked by fail2ban because I had blown the password a couple of times. Newbie mistake but I learned something new - fail2ban - cool tool)

But there are no Polycom files on my ISO distribution.

I've done a "find -name 'bootroom.ld'" and it was'nt found anywhere.

Is this a problem with the ISO or is Thirdlane not providing the Polycom boot and SIP files on the ISO?

I'll go ahead and download the Polycom distribution from http://downloads.polycom.com/voice/voip/sp_ss_sip/spip_ssip_vvx_3_2_3_r… and unzip them to /home/PlcmSpIp

no, the files are rather huge, the sip.ld package is 98M now (and seems to grow exponentially every version) and the bootrom is pretty large as well. It makes more sense for clients to load the firmware for the specific devices they want to support.

We are staying out of distributing firmware - size, versioning, distribution rights, etc, and leaving this to resellers/customers.

I would also like to add that one should look at the templates we are distributing as "sample templates" - our goal is to provide the basic templates that can be further customized as needed. Just remember to put your templates and your version of models.txt file in the user_provisioning directory so they don't get overwritten during software updates.

Hi,

We are taking a stab at the latest ast 1.8 and applied an unlicensed TL MTE on it. We've noticed that it isn't possible to *not* select a queue in tl-queue-member-pause-base

/Ole