PBX setup
-
savagezaing!
PBX setup
I am working for a hardware design company. And have been tasked to set up our PBX’s.
I need to do the following
Run VOIP handsets on OXE, OXO, 4400
As well as update the firmware on the OXO
The configurations are as follows
OXE :
MG, CS, and UA-16 card all working as expected admin done via telnet or HyperTerminal. All dect handsets work as expected. Have an IPPhone registered on the system, It gets the time and is aware of what numbers are available. But when trying to establish a call an error message is displayed: Network congestion. When trying to add more sets in the same wat the original was created we get:
Processing Failure
OBJECT -1: ATTRIBUTE 0: Lock 173/174/175/176/177(Users): Protection Error
OXO
OMC 510 1.1d software. CPU, UA-16 card as well as a CoCPU-2 card (not seen by software) When trying to make use of the OMC-Software upgrade function an error message is displayed :
Statusfile KO : State LOGIN, status KO, reason : Download forbidden in failsafe Check HD!
The PBX also functions correctly for normal DECT handsets as well as UA sets.
4400
CPU5 Card and DECT8 as well as an INT/IP card. But we do not know how to set up the card correctly. Expect it to be done in same way as OXE. But the cable connections elude us.
If there is anybody who would be able to help or point me in the correct direction I would be greatly appreciated.
Thank you in advance
Leon
I need to do the following
Run VOIP handsets on OXE, OXO, 4400
As well as update the firmware on the OXO
The configurations are as follows
OXE :
MG, CS, and UA-16 card all working as expected admin done via telnet or HyperTerminal. All dect handsets work as expected. Have an IPPhone registered on the system, It gets the time and is aware of what numbers are available. But when trying to establish a call an error message is displayed: Network congestion. When trying to add more sets in the same wat the original was created we get:
Processing Failure
OBJECT -1: ATTRIBUTE 0: Lock 173/174/175/176/177(Users): Protection Error
OXO
OMC 510 1.1d software. CPU, UA-16 card as well as a CoCPU-2 card (not seen by software) When trying to make use of the OMC-Software upgrade function an error message is displayed :
Statusfile KO : State LOGIN, status KO, reason : Download forbidden in failsafe Check HD!
The PBX also functions correctly for normal DECT handsets as well as UA sets.
4400
CPU5 Card and DECT8 as well as an INT/IP card. But we do not know how to set up the card correctly. Expect it to be done in same way as OXE. But the cable connections elude us.
If there is anybody who would be able to help or point me in the correct direction I would be greatly appreciated.
Thank you in advance
Leon
-
cavagnaro
Hi. welcome to alcatel world.
First lesson to learn when using Alcatel: LICENSES :p
The first error you are getting means you doesn't have the OPS (licenses) to make that function to work. The locks means what licenses are affected.
Run a spadmin, go to option 2 and see what numbers are in those locks.
OMC? What is that? Do you mean LOLA? That is the software used to do software upgrades in the OXO. There are a lot of prerequisites before doing that, and becarefull with what you are doing, load of software must be done by some certificated personal.
4400: What card you need to configure? The INIT/IP? Use your cable to connect to the card (as in the GD for OXE) and configure it.
First lesson to learn when using Alcatel: LICENSES :p
The first error you are getting means you doesn't have the OPS (licenses) to make that function to work. The locks means what licenses are affected.
Run a spadmin, go to option 2 and see what numbers are in those locks.
OMC? What is that? Do you mean LOLA? That is the software used to do software upgrades in the OXO. There are a lot of prerequisites before doing that, and becarefull with what you are doing, load of software must be done by some certificated personal.
4400: What card you need to configure? The INIT/IP? Use your cable to connect to the card (as in the GD for OXE) and configure it.
-
savagezaing!
Thank you!
LOLA? I have a windows bases application OmniPCX Office management Console for the OXO. And it has an OMC Software download function. That gives the above mentioned error.
My 4400 doesn’t look in any way like the OXE/OXE, it has WINDI connectors that has to be wired in a specific way. But I have documentation for wiring the Base stations, so they work – hehe. However the wiring from the intIP to the CPU eludes me, as well as how do you administrate the CPU? "netadmin -m" and "mgconfig" was the ones I used to admin the OXE, but it was done by using the HyperTerminal and moving the serial connection for the CS to the GD.
I’ll look into the Licensing issue.
Thankyou once again
Leon
My 4400 doesn’t look in any way like the OXE/OXE, it has WINDI connectors that has to be wired in a specific way. But I have documentation for wiring the Base stations, so they work – hehe. However the wiring from the intIP to the CPU eludes me, as well as how do you administrate the CPU? "netadmin -m" and "mgconfig" was the ones I used to admin the OXE, but it was done by using the HyperTerminal and moving the serial connection for the CS to the GD.
I’ll look into the Licensing issue.
Thankyou once again
Leon
-
ALCATELMEX
To administer the CPU in the 4400, you can do it by Telnet or by hyperterminal, and with the command "netadmin" will be able to configurate its addressing IP. Now to configure the addressing IP of the card INTIP, that you do it in the CPU with the tool "mgr", in the area of “Shelf/Board/Ethernet Parameters" on the slot where the INTIP is found, subsequently should assure you that both cards can be seen for IP. The card INTIP utilizes a connector 10/100 BaseT that permits to integrate it to the LAN, on this point you can connect the cable of network...
Salu2...
Salu2...
-
cavagnaro
Re: Thank you!
I believe you have then version 5 of OXO, let me ask to my OXO partners and will try to reply ASAPsavagezaing! wrote:LOLA? I have a windows bases application OmniPCX Office management Console for the OXO. And it has an OMC Software download function. That gives the above mentioned error.
-
mozi
For the OXO Problem, it seams that the Hard Disk is mal function.
If this has happend you got an Hardware Error Message 239. In case ofhard disk crash, the system works with reduced services, using NAND Flash memory.
Only one software version is stored in NAND Flash; it is not possible to download a new
version using OMC.
Make a Backup with OMC replace the Hard Disk and install the Software using LOLA
Is there enough memory on the CoCPU?
I upgraded an old OXO from R2.1 to 5.0 and the CoCPU doesn't start. Tracing during start of the CoCpu on the v24 Port shows that there was to less memory. After increasing it, it works.
If this has happend you got an Hardware Error Message 239. In case ofhard disk crash, the system works with reduced services, using NAND Flash memory.
Only one software version is stored in NAND Flash; it is not possible to download a new
version using OMC.
Make a Backup with OMC replace the Hard Disk and install the Software using LOLA
Is there enough memory on the CoCPU?
I upgraded an old OXO from R2.1 to 5.0 and the CoCPU doesn't start. Tracing during start of the CoCpu on the v24 Port shows that there was to less memory. After increasing it, it works.
-
savagezaing!
Thank you
I replaced the Hard Disk and it fixed the problem, on the OXO. Got the latest software from the Alcatel PBWS site and uploaded it. And the functionality I was looking fir is now working
am still experiencing problems getting the Co-CPU to work? In the system configuration view of the main cabinet Slot 5 is always empty. And it I create a configuration that defines that it should be there, it produces and error. I suspect that the card itself if malfunctioning. But maybe someone could shed some light on other reasons that may cause this.
Thank you once again
am still experiencing problems getting the Co-CPU to work? In the system configuration view of the main cabinet Slot 5 is always empty. And it I create a configuration that defines that it should be there, it produces and error. I suspect that the card itself if malfunctioning. But maybe someone could shed some light on other reasons that may cause this.
Thank you once again
-
savagezaing!
Software upgrade
Sorry for being such a noob.
I also got the Alcatel OmniPCX Enterprise Release 7.1 software from the alcatel BPWS site and was wondering what i need to do to install it onto my OXE? If anybody could point me in the right direction it would be great..
Or is is as simple as unzipping the file into any directory after uploading it onto the HD using for instance the TFTP connection. and then running the appropriate bat files?
Thank you in advance
I also got the Alcatel OmniPCX Enterprise Release 7.1 software from the alcatel BPWS site and was wondering what i need to do to install it onto my OXE? If anybody could point me in the right direction it would be great..
Or is is as simple as unzipping the file into any directory after uploading it onto the HD using for instance the TFTP connection. and then running the appropriate bat files?
Thank you in advance
-
cavagnaro
Licenses. 
If you have an older version you will need to acquire licenses for 7.1 and make sure you have all your current features and configurations activated.
Once you have the license you need the PC Installer. I'll highly recommend that this operation be done by someone who can give correct support as many things can happen if you don't know what are you exactly doing.
Also some versions without correct patches ends being a real nightmare.
Also, sa i see you are going to have a hard time giving support to your users, would be good if you take a basic training on OXE and OXO.
Regards
If you have an older version you will need to acquire licenses for 7.1 and make sure you have all your current features and configurations activated.
Once you have the license you need the PC Installer. I'll highly recommend that this operation be done by someone who can give correct support as many things can happen if you don't know what are you exactly doing.
Also some versions without correct patches ends being a real nightmare.
Also, sa i see you are going to have a hard time giving support to your users, would be good if you take a basic training on OXE and OXO.
Regards
