Call Pilot 150 Mini?

[Deweyhumbolt]

My partner is working on a Call Pilot 150 Mini attached to an MICS. Apparently this is impossible. All the details are on the Call Pilot thread. I know how good a tech he is, and I'm backing his play 100%.

Has anyone ever seen a Call Pilot 150 Mini hardware,(looks same as Call Pilot 100/150 except has 4 RJ11s) with Norstar software? The word is they only work on Option 11s.

The original problem is he cannot get the RJ45 NIC to work. He knows how to talk to Call Pilots, but no type of cable will get his laptop to even get activity lights.

There is a star awaiting...

Adversity is Opportunity

 

[endlesswinter]

http://www.nortel.com/products/01/c...ral/nn101060-0702.pdf#search='CallPilot MINI'

dosen't look like its gonna work on a MICS.

 

[Crowtalks]

OK, the CP100 has 2 RJ11 jacks and an RJ45 with 2 LEDs for the station ports.

The CP150 has 4 RJ11 jacks and an RJ45 jack with 4 LEDs for the station ports.

I saw the Nortel product PDF on the CP Mini for the Meridian and saw the embedded picture in the PDF.

It looks just like the CP150. If there is a difference, how do you tell?

Deweyhumbolt: Your coworker did statically assign himself/herself an address to connect to the CP, right?

NCSS NCTS NCTE

 

[hawks]

It is the same hardware, it's the software that makes it a Mini or 150. Look at your Call Pilot lable it should say 150/MINI Hardware.

 

[Deweyhumbolt]

Thanks for all your entries. But, doesn't a Call Pilot 100/150 have 2RJ11s. I believe the hardware is different. This Call Pilot 150 Mini has 4 RJ11s, and clearly says Call Pilot 150 Mini inside the cover. Guaranteed working on a MICS. Just need to know if there is any difference in how you interact with its Ethernet port.

crow: yes he gave himself a static IP in the normal range. He's gonna try the serial connection tda.

Adversity is Opportunity

 

[Crowtalks]

As far as the interaction of the ethernet port between the 100 and the 150, they are the same.

Did he try a crossover cable?

Newer laptops will auto detect the cabling and adapt. Older laptops will not and require a crossover cable to communicate with the Call Pilot.

Now back to the difference between CP150 that will work with a MICS and the CP150 for the Meridian...what is the difference as far as looking at the case?

The CP150 I use that hooks to a MICS says CP150/MINI, it has 4 RJ11 jacks, 4 LED indicators, 1 RJ45 jack.

NCSS NCTS NCTE

 

[senk1s]

150/ Mini is the same box - as it says on the label.

150 software is for the norstar only
mini software is for the 11c only

in 100 -> 1 norstar extension per jack for 4 channels
in 150 -> 2 norstar extensions per jack for 8 channels

100/150/mini default IP: 192.168.110.10

___________________________________________________

maybe a bad nic is the case

 

[Crowtalks]

You're right senk1s, my bad. The 150 still has 2 RJ11s with the wh/or enabled.

If I understand you correctly, the same 150 will work with a MICS or a X11?



NCSS NCTS NCTE

 

[RikRodgers]

I'd swear one of the first 150's I installed was on a Norstar, and it was labeled "150mini" on the sw. I ordered the same thing for the next job, but my supplier said it was incompatible. I thought I'd lost my mind. Maybe I haven't.

I haven't had a call back to that site in a loooong time, but I'll double check the next time I'm out.

 

[RikRodgers]

BTW- that site has a CICS 7.1.

 

[hawks]

From the 150 Mini Installer Guide:

CallPilot Mini is supported on Option 11C and Option 11C Mini.

The CallPilot Mini has the following connections:
• one RJ-45 jack for a 10/100 Mbps Ethernet connection to a local network
• one RS-232 port for connecting a terminal which provides alternative access
• two RJ-11 jacks, labeled Port A and Port B, for connections to a Meridian 1 PBX.
Each RJ-11 jack can support two TCM connections. Each TCM connection can support two voice channels. This gives the CallPilot Mini a total of eight voice channels.

 

[Deweyhumbolt]

This just gets more convoluted each day. I like your life expierence post Rik, seems like what my partner is facing. Everything about it says Call Pilot 150 Mini, and that it's not compatible, but it's working on an MICS.

Now the bigger issue is this Vmail has 4 RJ11s, not 2. You don't wire blues and oranges like I'm use to on a Call Pilot 150. The link supplied by endless on page 2, clearly shows this.

Anyway, until my partner runs the boot up on serial connection, I really don't have any more to report.

Adversity is Opportunity

 

[hawks]

Dewey, Where on page 2 are you looking because I don't see anything. Page 3 shows what looks like to me 3 as ports just like the 150.

 

[Deweyhumbolt]

Correct again, hawks. I took my partner's word. I now looked at it, and it's small on my monitor, but clear 3 connections. Nevertheless, my partner swears it has 4 RJ11s and 1 RJ45. He will provide pictures.

Thanks for keeping me honest.

Adversity is Opportunity

 

[ChicagoTech5555]

the software level is different for a 100/150 for a meridian system. I just put one in last month and the software level was 1.7 for a meridian system and the last 100/150 I put in a few months ago for a norstar was 3.1.

you must change your ip address to 192.168.110.11 or 12 etc..
and you must use a crossover cable to talk through the nic

 

[Deweyhumbolt]

Here's the bootup text file. No activity lights, laptop will not connect. We're guessing bad NIC. Any feedback appreciated. Does anyone know the passwords it wants at the end?
************************************************************

CallPilot 150 Boot Loader V1.5.19
(C) 2001 Nortel Networks

--------------------------------------------------------------------------
NETWORK INTERFACE PARAMETERS:
IP address on LAN is 192.168.110.10
HARDWARE PARAMETERS:
Serial channels will use a baud rate of 9600
This board's ethernet address is 0:14:3:BC:1E
CALLPILOT BOOTLOADER PARAMETERS:
Execution Mode: Load CallPilot
Source File System Parameters:
Device: ATA Disk
Source File List Name: filelst.lst
Destination File System Parameters:
Device: ATA Disk
File List Name: filelst.lst
Format Target Device: Y
Boot File Name: CallPilot.bin
After board is reset, start-up code will wait 2 seconds
--------------------------------------------------------------------------
To change any of this, press any key within 2 seconds


Automatic Update Mode Enabled!
To Change Update Mode to Manual, press any key within 10 seconds

Dialog Boot Sequence Enabled!
Using Dialog Parameters

Initializing ATA Disk... Done.
Initializing PCMCIA Stack ...SSInit: CS_Sockets - 2,Num_PWindows - 8
Card services Init complete found 2 sockets.
Done.
Initializing PCMCIA ATA Disk Drives ...SanDisk SDP 5/3 0.6
AtaInit: completed
Done.
Detecting ATA Cards...
Device found in Slot A:
Model: SanDisk SDCFB-256
Serial: 012123H1305M4353
Rev.: HDX 2.25
Mounted 10.256
Loading 10.256/CallPilot.bin... Done.
Unmounting 10.256
Transferring control to the downloaded code

I-Cache ON, D-Cache ON
Downloaded OS and application executing from RAM
Memory Test Completed Successfully
Starting root(RAM)
Initializing D-channel driver
Initialized for 8 channels
Disk volume 3.0.0, initialized...
Initializing ATA Disk... Done.
Initializing PCMCIA Stack ...Card services Init complete found 2 sockets.
Done.
Initializing PCMCIA ATA Disk Drives ...SanDisk SDP 5/3 0.6
AtaInit: completed
Done.
Detecting ATA Cards... Card(s) detected
Verifying 7.0
PPP: Using hardcoded ip address 192.168.0.2
PPP: Username is CallPilot
PPP: Password is administrator
PPP: Adding PPP NI...

Standard output device initialized...
7.1\safe not found
Pseudo device initialized...
TFTP device initialized...

Login:

Type "test" to stop auto boot

Starting Access/2 and Voicemail
SysConfig file does not exist. Use default!!!
Opening DSP Msg logfile
DSP[0]: 1.50.51.A7 July 12, 2004
DSP[1]: 1.50.51.A7 July 12, 2004
DSP Abstraction Layer Binding to port 5001
DSP Abstraction Layer Accepting...
Language Debug: Reading '7.1\access2\runtime\alarm0.dat'.
Read language file '7.1\access2\runtime\alarm0.dat'.
Loaded 1 of 1 language file(s). Default language: 0 (hex).
Curr File Pool Path='7.0\access2\FILEPOOL\0\*.*'
Curr File Pool Path='7.1\access2\FILEPOOL\0\*.*'
TCM 1: Channel 0: UP
dcd: CH0 is opened.
TCM 2: Channel 2: UP
dcd: CH2 is opened.
TCM 3: Channel 4: UP
dcd: CH4 is opened.
TCM 4: Channel 6: UP
dcd: CH6 is opened.
DCHCNTRL - DCH0 Reader created
DCHCNTRL - DCH1 Reader created
DCHCNTRL - DCH2 Reader created
DCHCNTRL - DCH3 Reader created
DCHCNTRL - Number of D-channels trying :4
dchMon: Initialized FumpSTM of Dchannel No : 1
dchMon: Initialized FumpSTM of Dchannel No : 3
dchMon: Initialized FumpSTM of Dchannel No : 2
dchMon: Initialized FumpSTM of Dchannel No : 4
DCHCNTRL - Active channel = 4 D Channel State = 255

dch: channel 4 Msg Len 99 Update Board to Access

dch: channel 4 Msg Len 99 Update Board to Access

dch: channel 4 Msg Len 99 Update Board to Access

dch: channel 4 Msg Len 99 Update Board to Access
D-channel No. 4 is working
D-channel No. 3 is working
D-channel No. 1 is working
D-channel No. 2 is working
dcd 0:receive unknown msg 1e
dcd 2:receive unknown msg b
dcd 2:receive unknown msg 3
Got KSU Version from functerm: ----30DEC04I„
***>>>TelInit telNumITInfoElemBytes 5

******************
* *
* ! R E A D Y ! *
* _ *
******************
Loaded 1 of 1 language file(s). Default language: 0 (hex).
Access up in 54 seconds
Starting voicemail
Country: NORTH AMERICA
Alternate QZ Mapping: 0
AMIS Address Start Key: #
Application SName: VM
Default Language {enum from country.c}: 0
Enable TT Gate: 0
Group List Lead Digit: 9
Key Language Toggle: 9
Key Operator Revert: 0

Maximum Network DN Length: 16
Maximum Packet Network DN Length: 16
National Number Length: 10
SC Maximum Lines 10 20: 334
Voicemail CORE Ready...


Password:
Invalid name.

Login: CallPilot

Password:
Invalid name.

Login:

FAR END INFO EVENT: Device Id 1 Call Id 8 Device Type 5e DN L3



FAR END INFO EVENT: Device Id 1 Call Id 12 Device Typ

Adversity is Opportunity

 

[SupportDude]

I reviewed my docs from the CP introduction back in 2002.
No mention of any cabinet with 4 RJ11 ports.
There was one picture and it had 2 RJ11 and one RJ45.
This could have been one of the very first CP's released, pre 1.5.

Why not just load up the latest CP s/w on the PCMCIA card and that'll be that as far as making sure you have the correct version.
I can second the fact that the cabinets are identical and its just the s/w that changes the interop.
You can upgrade the PCMCIA in a laptop with a card reader.

As for the passwords at the serial port, you don't need those. It only provides access to the OS. You can't really do much from there.

You might want to stop the boot when given the choice right at the beginning and verify the gateway is in the same subnet as the CP IP address. I remember that causing some strange problems in the early days.


-SD-

http://www.mysupportguy.net