Feb
14
2010
6

How to setup automatic Polycom provisioning for the Asterisk 2.0 GUI

Recently we covered the installation of Asterisk 1.6 + Asterisk GUI 2.0.  In this article we will talk about the details necessary to enable Polycom provisioning from the ‘Users’ tab of the Asterisk 2.0 GUI.  By default auto-provisioning will not work out of the box.  You would think when the GUI is installed that it would be setup as well, considering that you have the option to enter a MAC address in the user extension creation process.

Nor are their docs related to configuring this in the source packages(that I could find).  Online forums and tutorials were of no help either.  There are many post online claiming that you need to set up DHCP, ‘option 66’ for Polycom provisioning to work.  This is true of TFTP provisioning from AA50 appliance, but not from the Asterisk 2.0 GUI that relies solely on HTTP.  At least as far as I can tell.

I think Digium is being vague on purpose about this because they do not want to undermine their Asterisk Appliance product.  While I understand this line of thinking, it’s not consistent with the Open Source business models that have succeeded.

Open Source depends on reaching vast amounts of people due to the low cost.  When my customers have to choose between a Avaya system(running Linux) that cost $45,000 /w phones or a Asterisk system w/ Polycom phones for $19,000; it makes the lesser known Asterisk product attractive.  Over time the base builds up and Digium collects on hardware and support fee’s.

So from my perspective, any Asterisk installation helps Digium’s bottom line eventually.  Even if Digium doesn’t see money from every Asterisk user, simply the presence of those users makes Asterisk a more credible product.  Bringing more and more Enterprise and Government contracts to everyone, thus more money and investment into Digium.

Alright my tirade is over, back to business!  This post assumes you have installed a recent version of Linux, Asterisk 1.6 and the Asterisk 2.0 GUI installed.  If you do not, read my post:How to setup the Asterisk 2.0 GUI with Asterisk 1.6.

The Goals of this Post:

-configure phoneprov for Asterisk 2.0 GUI

(more…)

Dec
21
2009
0

How to setup auto-provisioning for Polycom SoundPoint IP phones using the Asterisk Appliance

The Digium Asterisk Appliance has built-in features for handling Polycom SIP handsets.  It’s very easy to do and will save you the trouble of individually configuring the settings of each phone.  I have a Digium AA50 configured with a standard dial plan and a Polycom Soundpoint IP 501.

Goals of this Post:

– Configure AA50 Polycom Provisioning
– Configure Polycom SoundPoint IP 501 phone

(more…)

Jun
28
2009
1

Polycom 501 XML configuration file Example

This file is named by the MAC address of your Polycom SoundPoint IP SIP phone followed by, ‘-phone.cfg’.  In your FTP folder you would have a file for each phone – I have a single phone.  It’s MAC is ‘0004F202734B’; so my phones configuration file would be named, ‘0004f202734b-phone.cfg’.  I believe there are other conventions for naming this file as well.

The example below was used to connect my phone with a VoiceIP Solutions Asterisk PBX.  This example shows just a fraction of the many possible features in this line.  For my purposes, I defined the Asterisk server IP address, and it’s SIP credentials.  I also added the NTP server.  The ‘mwi’ tag refers to ‘message waiting information’, here I set the mailbox(s) I’m subscribing to and the extension to check voicemail.   My Asterisk voicemail menu is extension ‘299’.

0004f202734b-phone.cfg:

<?xml version=”1.0″ encoding=”UTF-8″ standalone=”yes”?>
<!– Example Per-phone Configuration File –>
<!– $RCSfile: phone1.cfg,v $  $Revision: 1.104.2.2 $ –>
<phone1>
<reg
reg.1.displayName=”5555″
reg.1.address=”5555″
reg.1.auth.userId=”5555″
reg.1.auth.password=”2005″
reg.1.server.1.address=”192.168.1.254″
tcpIpApp.sntp.address=”pool.ntp.org”
tcpIpApp.sntp.gmtOffset=”-33600″
>
<mwi
msg.mwi.1.subscribe=”5555″
msg.mwi.1.callBackMode=”contact”
msg.mwi.1.callBack=”299″
>
</phone1>

Apr
02
2009
5

How to configure a Polycom SoundPoint IP phone for Asterisk on Fedora 10

In my opinion the best IP business phones on the market are made by Polycom. Anyone that knows anything about the VoIP Industry knows that!  High quality Polycom desk phones combined with Asterisk are a great combination of quality/price. So to that end we’re doing this lab.

Polycom employs several methods of provisioning the SIP phones.  For general configuration Sound Point IP have an excellent built web GUI,  but for multiple phones Polycom has an XML based system as well.  Every Sound Point IP can be provisioned based on MAC address.  Polycom’s provisioning method makes use of TFTP, FTP, or HTTP to deliver firmware updates and individual phone settings.

The goals of this post:

– Configure FTP server for Polycom firmware and configuration

– Configure Asterisk SIP extension

– deploy firmware and XML configuration files to Polycom SoundPoint IP 501 SIP phone

(more…)

Feb
26
2009
20

Using Multiple interfaces with KVM and Xen

I’ve been meaning to write a post on ethernet bridges and how they can easily be used to accommodate virtual machines with their “own” physical NIC(Network Interface Card).  I see a ton of post online about people struggling to get multiple ethernet cards to work in Xen and other hypervisors like KVM.  A common complaint is that when both NIC cards are plugged into the LAN they lose connectivity from all machines including the host.

Many sites make an attempt to explain the problem of multiple interfaces on the same network by walking you through a Xen custom configuration.  However they fail to identify the concept of bridges, layer 2 loops and why Spanning Tree Protocol is your friend!  So many virtualization nuts(like myself) spend hours trying to find a problem with Xen, Vmware, KVM, whatever… when the problem may just be how the interfaces are configured.

The goals of this post:

* define ethernet bridging

* explain ethernet loops

* discuss how this relates to VM’s and the hypervisor

* LAB: set up two ethernet cards for guest VM and my Fedora 10 KVM Server

(more…)