Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
How to Config Remote IP Phone in a Second Office
- Thread starter edsuk1
- Start date
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.
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.
- Thread starter
- #3
Thanks for coming back so quick, Gibsonic, just a couple of points:
1. "external avaya power brick or a standard PoE switch", excuse my ignorance, what is a "power brick" and is it located at the remote site?
2. We can do static ip's not a problem.
3. We do not currently have any IP phone or boxes that would allow IP, is it connected via standard IP ports?
4. Any idea which particular phone would suffice?
5. Where does the VCM module sit?
Thanks.
1. "external avaya power brick or a standard PoE switch", excuse my ignorance, what is a "power brick" and is it located at the remote site?
2. We can do static ip's not a problem.
3. We do not currently have any IP phone or boxes that would allow IP, is it connected via standard IP ports?
4. Any idea which particular phone would suffice?
5. Where does the VCM module sit?
Thanks.
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.
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.
- Thread starter
- #5
Got it, we have some standard analogue phones that are power by a seperate PSU, so this would be the same, albeit an IP phone.
Will review the 4621BL phones - thanks for that.
Opened monitor, cant see where the Vcomp value would be, any ideas? Also shows TFTP xxx copy of dump below, again any ideas?
********** SysMonitor v5.1 (65) **********
********** contact made with 192.168.16.40 at 16:39:19 6/7/2007 **********
********** System (192.168.16.40) has been up and running for 12days, 8hrs, 1min and 39secs(1065699863mS) **********
********** Warning: TEXT File Logging selected **********
********** Warning: TEXT Logging to File STARTED on 6/7/2007 16:39:19 **********
0mS PRN: Monitor Started IP=192.168.16.22 IP 406 3.1(48) EDS
0mS PRN: LAW=A PRI=1, BRI=0, ALOG=0, ADSL=0 VCOMP=0, MDM=0, WAN=0, MODU=3 LANM=0 CkSRC=5 VMAIL=1(VER=2 TYP=1) CALLS=0(TOT=4099)
447mS RES: Fri 6/7/2007 16:39:13 FreeMem=3550356(33) CMMsg=6 (6) Buff=100 657 500 1357 3 Links=7103 Elements=0
11963mS PRN: TFTPServer::RRQ(from 192.168.16.25) nasystem/call_info/0.9299.0
12447mS RES: Fri 6/7/2007 16:39:25 FreeMem=3547848(31) CMMsg=6 (6) Buff=100 657 500 1357 3 Links=7098 Elements=0
14945mS ISDNL3Evt: v=5 stacknum=5 State, new=Initiated, old=NullState id=9300
14948mS PRN: TFTPServer::RRQ(from 192.168.16.25) nasystem/call_info/0.9299.0
15090mS ISDNL3Evt: v=5 stacknum=5 State, new=OverlapSend, old=Initiated id=9300
15097mS PRN: TFTPServer::RRQ(from 192.168.16.25) nasystem/call_info/0.9299.0
21339mS ISDNL3Evt: v=5 stacknum=5 State, new=Proceeding, old=OverlapSend id=9300
21346mS PRN: TFTPServer::RRQ(from 192.168.16.25) nasystem/call_info/0.9299.0
24414mS ISDNL3Evt: v=5 stacknum=5 State, new=Delivered, old=Proceeding id=9300
24423mS PRN: TFTPServer::RRQ(from 192.168.16.25) nasystem/call_info/0.9299.0
24910mS ISDNL3Evt: v=5 stacknum=5 State, new=Active, old=Delivered id=9300
24926mS PRN: ConfMap 0 0.32 (B=1,R=0)
24926mS PRN: ConfMap 0 2.7 (B=1,R=0)
24927mS PRN: ConfMap 0 11.6 (B=1,R=0)
24929mS PRN: TFTPServer::RRQ(from 192.168.16.25) nasystem/call_info/0.9299.0
24943mS PRN: CLAIM called on call which is not ACD A=0.9301.0 B=0.9302.0
24947mS RES: Fri 6/7/2007 16:39:37 FreeMem=3543740(28) CMMsg=6 (6) Buff=100 657 498 1353 3 Links=7089 Elements=0
24978mS PRN: TFTPServer::RRQ(from 192.168.16.25) nasystem/call_info/0.9299.0
24989mS PRN: TFTPServer::RRQ(from 192.168.16.25) nasystem/call_info/0.9299.0
56881mS PRN: ConfUnMap 0 11.6 (B=1,R=0)
56881mS PRN: ConfUnMap 0 0.32 (B=1,R=0)
56882mS PRN: ConfUnMap 0 2.7 (B=1,R=0)
56889mS ISDNL3Evt: v=5 stacknum=5 State, new=DiscReq, old=Active id=9300
56947mS RES: Fri 6/7/2007 16:40:10 FreeMem=3550288(32) CMMsg=6 (6) Buff=100 657 500 1357 3 Links=7102 Elements=0
57150mS ISDNL3Evt: v=5 stacknum=5 State, new=NullState, old=DiscReq id=9300
95457mS PRN: TFTPServer::RRQ(from 192.168.16.25) nasystem/call_info/0.9303.0
95947mS RES: Fri 6/7/2007 16:40:49 FreeMem=3547848(31) CMMsg=6 (6) Buff=100 657 500 1357 3 Links=7098 Elements=0
97824mS ISDNL3Evt: v=5 stacknum=5 State, new=Initiated, old=NullState id=9304
97827mS PRN: TFTPServer::RRQ(from 192.168.16.25) nasystem/call_info/0.9303.0
97926mS ISDNL3Evt: v=5 stacknum=5 State, new=OverlapSend, old=Initiated id=9304
97933mS PRN: TFTPServer::RRQ(from 192.168.16.25) nasystem/call_info/0.9303.0
101947mS RES: Fri 6/7/2007 16:40:55 FreeMem=3547996(32) CMMsg=6 (6) Buff=100 657 500 1357 3 Links=7095 Elements=0
103081mS ISDNL3Evt: v=5 stacknum=5 State, new=Proceeding, old=OverlapSend id=9304
103087mS PRN: TFTPServer::RRQ(from 192.168.16.25) nasystem/call_info/0.9303.0
107692mS ISDNL3Evt: v=5 stacknum=5 State, new=Delivered, old=Proceeding id=9304
107701mS PRN: TFTPServer::RRQ(from 192.168.16.25) nasystem/call_info/0.9303.0
138061mS ISDNL3Evt: v=5 stacknum=5 State, new=DiscInd, old=Delivered id=9304
138067mS PRN: TFTPServer::RRQ(from 192.168.16.25) nasystem/call_info/0.9303.0
138947mS RES: Fri 6/7/2007 16:41:32 FreeMem=3548084(33) CMMsg=6 (6) Buff=100 657 500 1357 3 Links=7095 Elements=0
Will review the 4621BL phones - thanks for that.
Opened monitor, cant see where the Vcomp value would be, any ideas? Also shows TFTP xxx copy of dump below, again any ideas?
********** SysMonitor v5.1 (65) **********
********** contact made with 192.168.16.40 at 16:39:19 6/7/2007 **********
********** System (192.168.16.40) has been up and running for 12days, 8hrs, 1min and 39secs(1065699863mS) **********
********** Warning: TEXT File Logging selected **********
********** Warning: TEXT Logging to File STARTED on 6/7/2007 16:39:19 **********
0mS PRN: Monitor Started IP=192.168.16.22 IP 406 3.1(48) EDS
0mS PRN: LAW=A PRI=1, BRI=0, ALOG=0, ADSL=0 VCOMP=0, MDM=0, WAN=0, MODU=3 LANM=0 CkSRC=5 VMAIL=1(VER=2 TYP=1) CALLS=0(TOT=4099)
447mS RES: Fri 6/7/2007 16:39:13 FreeMem=3550356(33) CMMsg=6 (6) Buff=100 657 500 1357 3 Links=7103 Elements=0
11963mS PRN: TFTPServer::RRQ(from 192.168.16.25) nasystem/call_info/0.9299.0
12447mS RES: Fri 6/7/2007 16:39:25 FreeMem=3547848(31) CMMsg=6 (6) Buff=100 657 500 1357 3 Links=7098 Elements=0
14945mS ISDNL3Evt: v=5 stacknum=5 State, new=Initiated, old=NullState id=9300
14948mS PRN: TFTPServer::RRQ(from 192.168.16.25) nasystem/call_info/0.9299.0
15090mS ISDNL3Evt: v=5 stacknum=5 State, new=OverlapSend, old=Initiated id=9300
15097mS PRN: TFTPServer::RRQ(from 192.168.16.25) nasystem/call_info/0.9299.0
21339mS ISDNL3Evt: v=5 stacknum=5 State, new=Proceeding, old=OverlapSend id=9300
21346mS PRN: TFTPServer::RRQ(from 192.168.16.25) nasystem/call_info/0.9299.0
24414mS ISDNL3Evt: v=5 stacknum=5 State, new=Delivered, old=Proceeding id=9300
24423mS PRN: TFTPServer::RRQ(from 192.168.16.25) nasystem/call_info/0.9299.0
24910mS ISDNL3Evt: v=5 stacknum=5 State, new=Active, old=Delivered id=9300
24926mS PRN: ConfMap 0 0.32 (B=1,R=0)
24926mS PRN: ConfMap 0 2.7 (B=1,R=0)
24927mS PRN: ConfMap 0 11.6 (B=1,R=0)
24929mS PRN: TFTPServer::RRQ(from 192.168.16.25) nasystem/call_info/0.9299.0
24943mS PRN: CLAIM called on call which is not ACD A=0.9301.0 B=0.9302.0
24947mS RES: Fri 6/7/2007 16:39:37 FreeMem=3543740(28) CMMsg=6 (6) Buff=100 657 498 1353 3 Links=7089 Elements=0
24978mS PRN: TFTPServer::RRQ(from 192.168.16.25) nasystem/call_info/0.9299.0
24989mS PRN: TFTPServer::RRQ(from 192.168.16.25) nasystem/call_info/0.9299.0
56881mS PRN: ConfUnMap 0 11.6 (B=1,R=0)
56881mS PRN: ConfUnMap 0 0.32 (B=1,R=0)
56882mS PRN: ConfUnMap 0 2.7 (B=1,R=0)
56889mS ISDNL3Evt: v=5 stacknum=5 State, new=DiscReq, old=Active id=9300
56947mS RES: Fri 6/7/2007 16:40:10 FreeMem=3550288(32) CMMsg=6 (6) Buff=100 657 500 1357 3 Links=7102 Elements=0
57150mS ISDNL3Evt: v=5 stacknum=5 State, new=NullState, old=DiscReq id=9300
95457mS PRN: TFTPServer::RRQ(from 192.168.16.25) nasystem/call_info/0.9303.0
95947mS RES: Fri 6/7/2007 16:40:49 FreeMem=3547848(31) CMMsg=6 (6) Buff=100 657 500 1357 3 Links=7098 Elements=0
97824mS ISDNL3Evt: v=5 stacknum=5 State, new=Initiated, old=NullState id=9304
97827mS PRN: TFTPServer::RRQ(from 192.168.16.25) nasystem/call_info/0.9303.0
97926mS ISDNL3Evt: v=5 stacknum=5 State, new=OverlapSend, old=Initiated id=9304
97933mS PRN: TFTPServer::RRQ(from 192.168.16.25) nasystem/call_info/0.9303.0
101947mS RES: Fri 6/7/2007 16:40:55 FreeMem=3547996(32) CMMsg=6 (6) Buff=100 657 500 1357 3 Links=7095 Elements=0
103081mS ISDNL3Evt: v=5 stacknum=5 State, new=Proceeding, old=OverlapSend id=9304
103087mS PRN: TFTPServer::RRQ(from 192.168.16.25) nasystem/call_info/0.9303.0
107692mS ISDNL3Evt: v=5 stacknum=5 State, new=Delivered, old=Proceeding id=9304
107701mS PRN: TFTPServer::RRQ(from 192.168.16.25) nasystem/call_info/0.9303.0
138061mS ISDNL3Evt: v=5 stacknum=5 State, new=DiscInd, old=Delivered id=9304
138067mS PRN: TFTPServer::RRQ(from 192.168.16.25) nasystem/call_info/0.9303.0
138947mS RES: Fri 6/7/2007 16:41:32 FreeMem=3548084(33) CMMsg=6 (6) Buff=100 657 500 1357 3 Links=7095 Elements=0
the VCOMP value is in what you just posted... VCOMP=0
********** Warning: TEXT Logging to File STARTED on 6/7/2007 16:39:19 **********
0mS PRN: Monitor Started IP=192.168.16.22 IP 406 3.1(48) EDS
0mS PRN: LAW=A PRI=1, BRI=0, ALOG=0, ADSL=0 VCOMP=0, MDM=0, WAN=0, MODU=3 LANM=0 CkSRC=5
********** Warning: TEXT Logging to File STARTED on 6/7/2007 16:39:19 **********
0mS PRN: Monitor Started IP=192.168.16.22 IP 406 3.1(48) EDS
0mS PRN: LAW=A PRI=1, BRI=0, ALOG=0, ADSL=0 VCOMP=0, MDM=0, WAN=0, MODU=3 LANM=0 CkSRC=5
- Thread starter
- #7
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
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?
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?
- Thread starter
- #9
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.
Yes, network admin.
Cheers.
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.
Yes, network admin.
Cheers.
- Thread starter
- #11
- Thread starter
- #12
One other thing I have noticed with the system manger under BootP it shows the following:
1 x entry
enabled - not ticked
Mac 000000000003
Ip address 192.168.16.40
file name nas0-16.bin
time ofset 0
There is a seperate entry for the live box with the correct mac and ip address etc
Is the first entry required or should i delete it?
1 x entry
enabled - not ticked
Mac 000000000003
Ip address 192.168.16.40
file name nas0-16.bin
time ofset 0
There is a seperate entry for the live box with the correct mac and ip address etc
Is the first entry required or should i delete it?
- Status
Similar threads
