| View previous topic :: View next topic |
| Author |
Message |
rob at hillis.dyndns.org
Guest
|
 Posted: Fri Mar 28, 2008 12:54 am Post subject: [asterisk-users] Newbie Polycom: DHCP/boot server supporting |
 |
|
All Polycom phones use the same firmware and bootroms - one reason why
the sip.ld is so damn large for them.
Lee, John (Sydney) wrote:
| Quote: | I have a question about DHCP and boot server supporting more than 1
model of Polycom phones.
According to Polycom "standards", Polycom phone boots up to get a DHCP
address and at the same time getting a boot server string (with username
and password) to logon to boot server to download SIP, bootROM and etc.
That is okay if there is only one type of phone (that requires a
specific SIP and bootROM release).
What about if the environment has to support two or more models of
Polycom phones?
On the boot server side, I can define another home directory like
/home/polycom1 and /home/polycom2 to store different SIP and bootROM
releases. However, the issue is how different polycom phone model can
get a different user account and password to log on to different home
directories.
I understand the issue here is DHCP and not the boot server but I am a
bit of a newbie here.
Can anyone help please?
_______________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
|
|
|
| Back to top |
|
 |
pdhales at optusnet.co...
Guest
|
| Posted: Fri Mar 28, 2008 1:05 am Post subject: [asterisk-users] Newbie Polycom: DHCP/boot server supporting |
|
|
Can't you just use the same bootrom for all your polycom phones?
PaulH
On Fri, 2008-03-28 at 15:38 +1100, Lee, John (Sydney) wrote:
| Quote: | I have a question about DHCP and boot server supporting more than 1
model of Polycom phones.
According to Polycom "standards", Polycom phone boots up to get a DHCP
address and at the same time getting a boot server string (with username
and password) to logon to boot server to download SIP, bootROM and etc.
That is okay if there is only one type of phone (that requires a
specific SIP and bootROM release).
What about if the environment has to support two or more models of
Polycom phones?
On the boot server side, I can define another home directory like
/home/polycom1 and /home/polycom2 to store different SIP and bootROM
releases. However, the issue is how different polycom phone model can
get a different user account and password to log on to different home
directories.
I understand the issue here is DHCP and not the boot server but I am a
bit of a newbie here.
Can anyone help please?
_______________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users |
|
|
| Back to top |
|
|
Guest
|
| Posted: Fri Mar 28, 2008 1:05 am Post subject: [asterisk-users] Newbie Polycom: DHCP/boot server supporting |
|
|
| Quote: | All Polycom phones use the same firmware and bootroms - one reason why
the sip.ld is so damn large for them.
|
Thanks Rob.
Alleluia! Rob, I will take your word for it - it solves all my worries
in deploying different models to the same environment like IP5XX and
IP6XX. |
|
| Back to top |
|
|
splante at insightsys.com
Guest
|
| Posted: Fri Mar 28, 2008 1:58 pm Post subject: [asterisk-users] Newbie Polycom: DHCP/boot server supporting |
|
|
Paul Hales wrote:
| Quote: | Can't you just use the same bootrom for all your polycom phones?
|
To elaborate in case it isn't obvious from above: Even if you needed
different config files or even SIP applications by phone, you don't have
to go to separate DHCP entries by phone. The MACADDESS.cfg file points
to everything *except* the bootrom, so as long as you can share the same
bootrom for all your phones, you can set one particular phone to use the
new latest-and-greatest SIP application and related config files by just
changing it's particular MAC.cfg file. |
|
| Back to top |
|
|
|
Search
