Problems with CallPilot 150

[PTerrell]

I've got a CallPilot 150 hooked up to a MICS 6.1 that is "being cranky".

Users complained that they were getting "Inactive Feature" when they tried to get into VM. The CallPilot had all four port lights on. I tried to browse and ping the IP address and got nothing.

I tried unplugging and replugging several times, but LEDs briefly flashed at first, then nothing.

Took it over to the local vendor and the sales rep plugged it into his test bench and it came up fine: all features and mailboxes available. Diagnosis: bad power supply.

With new power supply, unit now powers on, and is pingable. But cannot get in through F*8 or browser. After the LEDs go through the boot cycle, no lights...

Could this be bad ports on the KSU?

 

[lugerlover]

swap ports then

 

[DigitelD]

If it's being cranky, put it in the corner for some time-out.

SHK Certified (School of Hard Knocks)

 

[cook1082]

Try feature xf test and remove the feature codes from the system . Then reboot the CP.

 

[bwtc]

Make sure that there is no residual wire stuck in the punch-down block, from a previous connection. This can cause a loose/poor connection. I've noticed that the CallPilots are not as forgiving as the Nortel phones if there is a loose connection -- they generally need to be rebooted if connection is even briefly lost.

 

[PTerrell]

Thanks all for the help. Lugerlover was correct. I swapped the ports and the VM came on after a reboot.

Sigh...those simple things that leave you scratching your head...

 

[PTerrell]

And I feel bad for my typo...I meant F9**...

 

[gforce9]

What version of CP do you have? There were several s/w issues on boot cycles with the CP's.....especially early on. If it was a 1.5.32.01, for example, your 'fix' may only be temporary.