CallPilot Blue Call Router 4

[aspencommtech]

Hooking up new system, supposedly been working together before a system wipe.

I have built everything, but Call Pilot is not answering.

I have CP 201i in slot 10 on main cabinet. Built 14 2008 sets for number of licenses, and built CDN in LD 23. Getting error messages on reboot. What might I have done wrong? This is not going into their network, so I don't know about ELAN needs, even though I built port 16.

Please help.

 

[tball1]

You will need to but phone system and callpilot on elan together and use a small dumb switch if you have one so they can talk on each other. Also if the 201i is being used in a cabinet you are not to use slot 10 as leading card slot use something like 8 and 9 or 11 or 12.

 

[KCFLHRC]

Card slot 10 will work fine, not recommended by Nortel but will work fine. Definitely make sure you have the Elan from the PBX connected to the Elan of the Cal Pilot either through a hub, switch or crossover cable. Monitor the PBX after these connections are made and see of the Elan comes up. You also have to build a VASID if you haven't done so.

 

[aspencommtech]

First off I don't know where to connect ELAN to PBX. Is there a connector I might be missing?
I don't see an RJ-45 on the card. Should there be some adapter to the AMP cable port?

VISD is another issue too. Anyone willing to walk me through the steps?

Thanks.

 

[KCFLHRC]

There will be an amphenol looking connector in the bottom of the cabinet labeled P1. You will need to plug in a Nortel cable there Part # NTDK27AA, then you will plug in a transceiver into that for your ELAN connection. The VASID is built in LD 17 and is associated with the ELAN, so VASID 16 is associated with ELAN 16. So in Ld 17 you would do a new VAS, VSID 16, ELAN 16. Hope this helps

 

[aspencommtech]

I am geting errors trying to do a new vas, but chg works, then I get stuck.

 

[KCFLHRC]

Req = chg
Type = vas
vsid = 16
elan =16

If in fact 16 is your Elan this is how you build the vas

 

[janaya]

Blue Call Router is the ELAN connection not communicating between the PBX and the Call Pilot. Make sure in the Config Wizard you have the right IP addresses in the right place (ELAN/CLAN). I have transposed octets and got this. My typo so my fault. I would check there first.

 

[aspencommtech]

I guess I am missing a part, so it is on its way. Default came up as 1.1.1.1 and 2.2.2.2? Sound right?

 

[KCFLHRC]

By default the PBX is 137.135.128.253 with a mask of 255.255.254.0 You will need to put the Call Pilot ELAN in that same SubNet. Don't worry about the CLAN

 

[aspencommtech]

What should the gateway be?

 

[KCFLHRC]

You can just make the gateway .1

 

[janaya]

If you need your information from the pbx

login to the system

ld 117
=> prt host
look for the primary 137.135.128.253 (default - your's could be different
=>prt mask
255.255.255.0 (again default info here

Like KCF stated for the gateway you can enter .1

CLAN information would be your network information.

 

[aspencommtech]

If I have no network, I am just supposed to connect this into a dummy hub, I am told, still waiting on a part to do so, but this will allow my pbx to talk to the callpilot
/?

 

[telebub]

Or crossover cable between CallPilot ELAN cable and PBX transceiver.

 

[aspencommtech]

I'm now getting IP address conflict.

Used 137.135.128.253 for ELAN

used 137.135.128.254 for CLAN

 

[KCFLHRC]

The PBX is 253, make the Call Pilot 250 and make the CLAN 249 or what ever you want

 

[aspencommtech]

Hey, I think it is all working. Anybody know the default passwords on the CP? Says it should be between 6 & 16 digits when I manually change it.

 

[KCFLHRC]

What release is the call pilot? probably is bvw250

 

[aspencommtech]

I found it, was 12+DN for the mail box.