8300 Voipdb not working 1

[OzzieGeorge]

Hi

I have been asked to help a company who are just installing their first 8300 as they are having problems. Thing is I have only done the administrators course on this and whilst I am very conversant with the IPS the problem they have is in an area new to me. The system runs fine but there is a second stack and we can't get that working because the Vopidb connection in the main stack won't talk to us.In fact if we change the IP address to anything but the default setting, the port shuts down completely. With the default address the port is active but won't talk to us.

The daughter board has been changed but the fault remains and we have defaulted the system and still the fault remains. I personally suspect licensing but whilst I have had a look in Cmd F88 I am unsure if there is a license that covers this port (the company used a configuration tool from NEC to spec the system and licensing) Have any of you experienced this problem before or can someone point us to the necessessary licensing. Then again am I completely off the mark here, could it be a fault or something else?

 

[neax]

Ozzie,

Default, with any/all CP00 or CP02 processors, you are licensed for 108 physical ports, 32 IP station ports and 16 VOIP channel ports. What do you have in Command F88-011-? You need at least 32. so you could use 16 in the main unit and 16 in the next unit.

Also check the following Commands:

0B201-00-? and 0B201-01? (this is the IP address of your PAD cards for unit 01 and unit 02. These are static addresses provided by you network person. EC6 then a system rest is needed after you change this. Then, try to PING the two addresses
0B001-10 should be at least 32. You need at least that to allocate 16 for each PAD card between unit 01 and 02.

 

[belevedere]

If you are connecting a second cabinet to a one stack system then all you need is the BS-00 and BS-01 blades with the provided cables. After that your port licensing comes into play when you attempt to add a blade.
If you are setting up multiple stacks then you need to verify the sense wheel switch settings on the CPU blades. 1 for stack 1, 2 for stack 2 etc. You also need to log into each CPU to set up the IP addresses initially. Obviously they cannot be duplicated, but in the same subnet. All CPU's need to be the same software version. If you have the new IPPAD blade
(IPLC-A)then you need only 2 IP addresses. One for the blade and one for ALL possible DSP's. Licensing determines how many are available. You no longer need 1 address per 16 DSP's.

 

[OzzieGeorge]

Perhaps I should have been more specific. even though we have used the quick setup in PCPro and allocated 16 voip licenses to the main processor and left the Ip addresses at the default setting, without the second stack connected, I cannot ping the Voipdb port on 172.16.1.1 I have 32 licenses by the way. with the voipdb address set to default the port comes live but can't be pinged. If I change the IP address of the Voipdb port, the port shuts down completely (computer reports cable disconnected)

 

[belevedere]

I had an issue like that once. It turned out to be a motherboard. I would try to reseat the VoIP board then try defaulting the system. Verify that you have the latest R7 software. Also, zero out any remaining IP addresses for the DSP's. Leave only the first one in. The new hardware (IPLC-A) requires only one address. Additional ones left in could create a problem.

 

[OzzieGeorge]

Belvedere

You got it! The installing tech had failed to check and upgrade the software prior to programming! It was apparently still on rev1 and in Oz we are up to rev6! I believe all is now ok!