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 IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

4000 V5 TCP-IP question

Status
Not open for further replies.

rick517

IS-IT--Management
Nov 6, 2004
2
US
Trying to set this up from scratch, how do I set all of the IP addresses required?? Thanks
 
What exactly is the goal? Administrative access? HiPath Manager? IP Phones? IP Trunking? IP Shelves? Need more specifics before anyone can provide a satisfactory response.
 
The goal is
1 Put the pbx on our in house network
2 Configure Ip Phones
3 do all admin required tasks

Does this help
I hope so, I am confused
 
Much better. My advice would be to attend training. These tasks are not all that difficult, but there are many things to do, and it sounds as if you have no clue where to begin. Someone with plenty of spare time will need to assist you. The service & administrative documentation appears to be designed to assist previously-trained engineers, so it will most likely not be of much help.
Good luck!
 
If you have a login and password for the system that allows you access to the configuration.

Set up the "Customer LAN" with an IP from your network, default gateway, and appropriate netmask for your network. This will be the IP you use for Administration.

Set up your STMI4 card(s) with a different IP from your network, default gateway, and netmask. This will be your gateway IP for the IP phones. If you have the ability, the STMI4 card has 2 ethernet jacks - both of them will have the SAME IP address. You can connect each one to a different switch in your network, and in the event one switch/port/connection fails the board will failover to the second port/switch with the same configuration parameters, giving you some redundancy. There is other redundancy stuff as well, but this will get you going. The other configuration task you're going to want to do in your STMI4 card(s) before you create ANY phones on them is to decide how many ports you want to reserve for SIP and how many you want for regular IP phones. Each board can do 120 phones, and it can be partitioned any way you want between SIP and IP but it is a major PITA to change it after the fact because you first have to delete all the phones, then change it, and then recreate all the phones.

I believe those are the only 2 IPs you need from your LAN for the switch (unless you have multiple STMI4 cards - in which case you can build your phones on whatever card you choose, but for the phone's gateway you must set the IP of the card that the phone was built on).

Any other stuff probably gets configured on the Atlantic LAN, which is used for internal communications of the system and is not part of your network. Your vendor should have set up anything necessary there at install time.

HOW you set up the customer LAN and the IP of the STMI4 card I'm not going to go into for lack of space, but the system has pretty good help topics built-in.

Like Iamnothere said - there is a lot of stuff there that gets pretty deep, and I would also advise you seek out some training, or at least do what I did and pay the tech for 4 hours of time to go through the system with you and take lots of notes. In my case I have been administering systems with very similar programming functions for 15 years, and I just had to have him give me a rundown on how to set up all the IP stuff and the differences in the command language between the 9006 version of the AMOs I am used to and the "new" version changes of some of their names because they left a LOT of it in German and command names that made sense before have been renamed to make very little sense now! (like DEST for call forwarding and other destination programming is now called ZIEL, and etc.... )

Also keep in mind that it's quite a different thing to play on a system you don't understand in the classroom or before it goes into service - you can screw up and it's no big deal, just a learning experience - vs a live system that is in production. If you make a serious mistake in a live system and don't know how to fix it you take your site down until you can get a service tech in there to fix it! That could be a "career limiting move", as a former CEO of my company used to call it...




 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top