at needs to be resolved. The rest of the phones that auto
> > provision work that way - Nortel, LG, Linksys, etc.
> >
> >
> >
> > From: sipx-users-boun...@list.sipfoundry.org
> > [mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Alberto
> > Sent
that auto
> provision work that way - Nortel, LG, Linksys, etc.
>
>
>
> From: sipx-users-boun...@list.sipfoundry.org
> [mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Alberto
> Sent: Tuesday, September 27, 2011 10:11 AM
> To: Discussion list for users of sipXec
half Of Alberto
Sent: Tuesday, September 27, 2011 10:11 AM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] SNOM auto-provisioning
Hi Tony,
yes definitely when using a different dhcp server something has to be done
manually. I belive this is the case of Polycom phones too
Hi Tony,
yes definitely when using a different dhcp server something has to be
done manually. I belive this is the case of Polycom phones too.
For a windows server it is perfectly possible to configure snom phones
for auto provisioning. This is what I'm currently using. I don't know if
it's pos
On Tue, 2011-09-27 at 18:41 +0200, Alberto wrote:
> I'm not an expert on dhcpd.conf but seems to me that the code won't
> break anything:
> > class "snom" {
> > match if substring (hardware, 1, 3) = 00:04:13;
> > option tftp-server-name"http://:8090";
> > option bootfile-n
On Tue, Sep 27, 2011 at 12:51 PM, Tony Graziano
wrote:
> I wont break anything. We can even add the same code for 0004f2 (polycom) to
> be specific to a polycom, otherwise it takes the defaults.
Sounds like patch is a go then
> What is unclear
> is how to implement it on anything other than a li
I wont break anything. We can even add the same code for 0004f2 (polycom) to
be specific to a polycom, otherwise it takes the defaults. What is unclear
is how to implement it on anything other than a linux dhcp server.
We can certainly put it in the default dhcpd.conf file, but it becomes part
of
I'm not an expert on dhcpd.conf but seems to me that the code won't
break anything:
class "snom" {
*match if substring (hardware, 1, 3) = 00:04:13;*
option tftp-server-name"http://:8090";
option bootfile-name "/phone/profile/docroot/{mac}.xml";
}
the strin
But I think if we do what you're suggesting we'd break Polycom
provisioning... which is the most used phone on the system...
On Tue, Sep 27, 2011 at 12:28 PM, Alberto wrote:
> Il 27/09/2011 12:47, Michael Picher ha scritto:
> > sipxecs's own dhcp is just dhcpd on the sipxecs server. modify c
Il 27/09/2011 12:47, Michael Picher ha scritto:
> sipxecs's own dhcp is just dhcpd on the sipxecs server. modify config
> in /etc/dhcpd.conf
>
yes I know
> we don't have fine-grained control over dhcp config files in sipXecs.
> If you're afraid of command line stuff you can always install webmi
On Tue, Sep 27, 2011 at 6:52 AM, Tony Graziano
wrote:
> I think he is suggesting that on newer snom firmware auto provisioning with
> sipx will not work unless dhcp.conf is modified. I think he is suggesting an
> improvement to the default dhcpd.conf to get around that.
>
> I see both sides. if yo
I think he is suggesting that on newer snom firmware auto provisioning with
sipx will not work unless dhcp.conf is modified. I think he is suggesting an
improvement to the default dhcpd.conf to get around that.
I see both sides. if you say sipx will not be my dhcp server that code may
not work on
sipxecs's own dhcp is just dhcpd on the sipxecs server. modify config in
/etc/dhcpd.conf
we don't have fine-grained control over dhcp config files in sipXecs. If
you're afraid of command line stuff you can always install webmin on your
server (http://www.webmin.com/rpm.html)
Mike
On Tue, Sep 2
Hi Douglas,
a little feature that was requested in the past is to add by default on
the sipxecs dhcp server the configuration to support snom phones out of
the box. I believe the solution that Domenico suggested is perfect:
class "snom" {
match if substring (hardware, 1, 3) = 00:04:13;
On Tue, Sep 27, 2011 at 2:18 AM, Alberto wrote:
> won't be compatible with html config file anymore. I'm working on a new snom
> plug-in specifically designed for version 8.x.
Excellent. Be sure to note that phone support moved into separate
projects/rpms in the development branch
https://git
Please feel free to update it... that's why we have a wiki. Community
supported documentation.
On Tue, Sep 27, 2011 at 2:18 AM, Alberto wrote:
> Hi Mike,
> the wiki is outdated. Sipxecs supports SNOM firmware 7.x since version 4.0
> and since that time xml is the file format supported. I had
Hi Mike,
the wiki is outdated. Sipxecs supports SNOM firmware 7.x since version
4.0 and since that time xml is the file format supported. I had write
access to the old wiki and I remember I changed it simply adding the xml
extension.
Don't know why the new wiki did not pick-up the change.
For
there's already a note about this in the snom page in the wiki (
http://wiki.sipfoundry.org)
Thanks,
Mike
On Mon, Sep 26, 2011 at 12:07 PM, Domenico Chierico
wrote:
>
>
>
>
> > Be careful that snom 7.x phone will look for a xml file. The path will
> be:
> > http://{HOSTNAME}:8090/phone/profile
> Be careful that snom 7.x phone will look for a xml file. The path will be:
> http://{HOSTNAME}:8090/phone/profile/docroot/{mac}.xml
yes and the better solution i've found for this is an entry into dhcpd config
file like this:
class "snom" {
match if substring (hardware, 1, 3) = 00:
Hi John,
I'm still using version 4.2.1 but I would guess no ... nothing changed
in the path.
Be careful that snom 7.x phone will look for a xml file. The path will be:
http://{HOSTNAME}:8090/phone/profile/docroot/{mac}.xml
To be sure try to access the snom config generated using your browser.
Yo
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: 8bit
Organization: SipXecs Forum
X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <63541>
Message-ID:
I'm trying to download a created snom config file from my
sipxecs 4.4 server at the URL that is mentioned on the
wiki:
http:
21 matches
Mail list logo
