I’m new at this and had very little training way back. Have not worked in PBX for years, I am attending training soon but not before working on several things.
Can someone help explain some questions regarding this configuration…?
Main site with CS on appliance server, redundant CS at remote location and 5 sites with GD2 and PCS at each site connected via company WAN.
Questions:
1) Is the entire configuration done in main CS? Meaning does all the information broadcast to all remote PCS? Or do you program each PCS individually? How is this done?
2) Does a PCS have mtcl/mgr access for configuration? In other words is a PCS same as CPU/CS?
3) When creating users, how does it know which node it belongs to if creating in main CS?
4) Is there a recommended numbering plan? I.e. node 1 has extension 2100 and node 2 has 2200, etc...?
5) To call each node are IP trunk groups created?
6) When calling from node 1 to node 2, how does the system know to call over IP network? Where in the configuration is this done?
In know this is all very basic questions and it would help me understand the OXE network. Thanks very much.
basic OXE Network questions from beginner?
-
cavagnaro
Re: basic OXE Network questions from beginner?
Hi and welcome to the forum.
PCS is a survive facility which complements CPU redundancy, what this feature will do is if on your remote shelfs you loose connection to main CPU then the "local" CPU will activate and mantain functionality of that shelf as a standalone PBX. Once connection is restored it will reboot and beging to work as a remote shelf. Each shelf has a number (under command line on main CPU write "config all" to see all your shelfs. I guess the one who did the implementation left a document with shelf 1 = location A, shelf 2 = location B, and so on.
Hope this helps in something
PCS is a survive facility which complements CPU redundancy, what this feature will do is if on your remote shelfs you loose connection to main CPU then the "local" CPU will activate and mantain functionality of that shelf as a standalone PBX. Once connection is restored it will reboot and beging to work as a remote shelf. Each shelf has a number (under command line on main CPU write "config all" to see all your shelfs. I guess the one who did the implementation left a document with shelf 1 = location A, shelf 2 = location B, and so on.
Yes it is done on the main CPU and will broadcast the configuration once the configuration is done, first time each PCS needs some parametes as IP addres and such stuff, but as yours is already working then no need to do it, unless you loose such configuration, you know, shit happens. The propagation is done using a command which will do is copy main CPU DB to the PCS db.liegraves wrote:
1) Is the entire configuration done in main CS? Meaning does all the information broadcast to all remote PCS? Or do you program each PCS individually? How is this done?
Yes, but any configuration you do here as standalone CPU will be loose once connection to main CPU is restored.2) Does a PCS have mtcl/mgr access for configuration? In other words is a PCS same as CPU/CS?
Because in the user you declare shelf (location), which board on that shelf and the port.3) When creating users, how does it know which node it belongs to if creating in main CS?
It is up to you really, customer will need to define it with you even determine how many digits, but remember never overlap.4) Is there a recommended numbering plan? I.e. node 1 has extension 2100 and node 2 has 2200, etc...?
Nop, the remote shelfs will act as IP devices, so you need only to make sure both CPU and PCS and remote GD has IP connectivity.5) To call each node are IP trunk groups created?
Node 1 to node 2? Then each site has its own CPU? That is different configuration as PCS becasue in Nodes configuration you have an active CPU on each site, while on PCS the CPU is down until connection to main CPU is down.6) When calling from node 1 to node 2, how does the system know to call over IP network? Where in the configuration is this done?
Hope this helps in something
-
liegraves
Re: basic OXE Network questions from beginner?
thank you very much cavagnaro that does help. I didn't know the remote sites are to be shelves off the main node.
I read that each PCS needs to be in its own IP domain, is that the case? Where does this get accomplished?
So at each PCS I have to setup netadmin and then do I do a create empty database afterwards?
So as far as users, if I have an IP phone I point it to the main CS IP address or the PCS IP address to get information?
This has not been implemented yet. I will be assisting in the deployment later in the year or early next year.
thanks for your input.
I read that each PCS needs to be in its own IP domain, is that the case? Where does this get accomplished?
So at each PCS I have to setup netadmin and then do I do a create empty database afterwards?
So as far as users, if I have an IP phone I point it to the main CS IP address or the PCS IP address to get information?
This has not been implemented yet. I will be assisting in the deployment later in the year or early next year.
thanks for your input.
-
d-mgr
Re: basic OXE Network questions from beginner?
Yes IP domains are setup under mgr/IPliegraves wrote:thank you very much cavagnaro that does help. I didn't know the remote sites are to be shelves off the main node.
I read that each PCS needs to be in its own IP domain, is that the case? Where does this get accomplished?
Yes that is best idealiegraves wrote:So at each PCS I have to setup netadmin and then do I do a create empty database afterwards?
Use CS DHCP and nothing has to be done at user level. Setup ranges for each IP Domainliegraves wrote:So as far as users, if I have an IP phone I point it to the main CS IP address or the PCS IP address to get information?
Good Luckliegraves wrote:This has not been implemented yet. I will be assisting in the deployment later in the year or early next year.
thanks for your input.
