1. We have a second office with a fixed range of external IP addresses, I am looking to install a phone and use as part of the main office system, by calling either way using the extension number, any ideas?
outside of the data networking concerns about bandwidth, QoS, etc. the setup is pretty simple.
each phone needs power via external avaya power brick or a standard PoE switch.
you can do DHCP, but i would recommend static assignments in this scenario. you'll need to read up on how to add option 176 to your dhcp server at your remote site if you want to do dhcp.
boot the phone, give it an ip address for the local network, give it the gateway, subnet mask, etc. When it ask for the call server give it the IP address of your IPO office.
you will want to pre-create the IP extensions and users on the IPO for best results.
after it gets all it's network info it should ask for the extension and password.
that's really all their is to it outside of the data networking concerns.
definatley need to make sure your IPO has ip routes to the remote subnet...
oh and you have to have a VCM module with enough resources.
there are some things to play with concerning which codec to use but you should be able to get basic functionality with automatic.
by avaya power brick, i am referring to the 1151B1 Power Supply (or 1151B2 Power Supply with Battery Backup) that is an external black box device that receives ac power from the wall and then injects power to the IP phone in lieu of the phone receiving power from a standard PoE (802.11af compliant)
your IP phones will connect to your regular data network directly or through the above mentioned power device.
ideally your data network would use VLAN's to segment the voice traffic, QoS to prioritize traffic, and have tons of available bandwidth over your WAN connection. What type of WAN connection do you have between the sites? VPN, Frame Relay? Point to Point T1?
The phone choice is going to be one based on business need and personal preference. I personally like the 4621BL since the BL stands for Back-Lit...looks much nicer than the non-BL. Of course it's a lil more $ than smaller phones with less features.
The VCM module is installed internally to your IPO control unit. You can use the monitor tool that comes with the ip office admin software to connect to your system. once connected it will show a VCOMP=? value where the ? is the number of VCM channels you have. If it says 0 you don't have any...duh. They now come in 4, 8, 16 and 30 port flavors. You will need to size the VCM based on how many IP phones you will be installing and how many simultaneous connections you anticipate needing to be able to support.
To be honest, if you are not familiar with some of what i've already described you are probably best served by contacting a local Avaya Business partner to help you out.
Its been a long day, thanks for pointing out the obvious.....I really should read before sending.
Any ideas on what the TftpServer logging means, if I click on the Tft log from manager it shows the following:
Fri 6/7/2007 10:08:03 : Received BOOTP request for 000fb5fdbbbc 192.168.16.25 , unable to process
Fri 6/7/2007 10:08:06 : Received BOOTP request for 000fb5fdbbbc 192.168.16.25 , unable to process
Fri 6/7/2007 10:08:10 : Received BOOTP request for 0020ed41f6bb 192.168.16.30 , unable to process
Fri 6/7/2007 10:08:13 : Received BOOTP request for 0020ed41f6bb 192.168.16.30 , unable to process
Fri 6/7/2007 10:29:00 : Received BOOTP request for 000000000000 192.168.16.2 , unable to process
Fri 6/7/2007 10:29:00 : Received BOOTP request for 000000000000 192.168.16.2 , unable to process
Fri 6/7/2007 10:29:00 : Received BOOTP request for 000000000000 192.168.16.2 , unable to process
Fri 6/7/2007 10:29:00 : Received BOOTP request for 000000000000 192.168.16.2 , unable to process
Fri 6/7/2007 10:35:47 : Received BOOTP request for 000fb5fdbba8 192.168.16.13 , unable to process
Fri 6/7/2007 10:35:51 : Received BOOTP request for 000fb5fdbba8 192.168.16.13 , unable to process
Fri 6/7/2007 10:51:38 : Received BOOTP request for 000fb5fbd113 192.168.16.24 , unable to process
Fri 6/7/2007 10:51:42 : Received BOOTP request for 000fb5fbd113 192.168.16.24 , unable to process
Fri 6/7/2007 10:54:28 : Received BOOTP request for 000fb5fdbbad 192.168.16.21 , unable to process
Fri 6/7/2007 10:54:31 : Received BOOTP request for 000fb5fdbbad 192.168.16.21 , unable to process
Fri 6/7/2007 11:10:10 : Received BOOTP request for 000423dc6a41 192.168.16.16 , unable to process
Fri 6/7/2007 11:13:10 : Received BOOTP request for 0015586f4840 192.168.16.17 , unable to process
Fri 6/7/2007 11:13:14 : Received BOOTP request for 0015586f4840 192.168.16.17 , unable to process
Fri 6/7/2007 11:14:15 : Received BOOTP request for 000fb5fdbbac 192.168.16.23 , unable to process
well you obviously have several different devices trying to access your tftp server.
do you have any IP phones on your network already? btw...in order to send the updated firmware to the ip phones you should set your ip preference in manager to 255.255.255.255
are you the network admin? what are those ip addresses assigned to from your list there?
The IP address are for standard winxp machines with phone manager loaded (clients).
No IP phones whatsoever, 1 x 406, 1 x ISDN box (used only for occasional ISDN kit that is plugged in from time to time), 2 x 16 port analog pots, with a seperate PC running the manager software.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.