Restore CallPilot ELAN

BEWARE! This procedure is superseded. If there's a Signalling Server, it is not recommended to disable the Call Servers ELAN!

If the ELAN goes down, CallPilot will too! This includes both VoiceMail and Auto-attendant functions. CallPilot "Blue Call Router" service not starting, or similar errors, (after re-booting) also indicate an ELAN problem. Check the CallPilot ELAN cabling and connections!

To reset the ELAN, and hopefully restore CallPilot, follow the procedure below.

Note: this must be performed from a serial TTY, and will affect call processing on 4.5 systems and later (systems equipped with Signalling Servers). Proceed only if you understand the ramifications of disabling a systems ELAN.

1 Shut down CallPilot. Check for acquired CDN's:

LD 23

REQ: PRT
TYPE: CDN

2 If there are any CDN's acquired, they must first be released:

LD 48	-	STAT ELAN	- to find the <ELAN#>
LD 48	-	DACR ALL <ELAN#>

3 Then disable the link:

LD 48	-	DIS ELAN	- Optional Step. See Note above!
LD 137	-	DIS ELNK

4 Re-insert (or boot) CallPilot, and re-enable the link:

LD 137	-	ENL ELNK
LD 48	-	ENL ELAN	- Optional Step. See Note above!

5 CallPilot should boot-up and you will see CDN Acquired messages on the terminal.
Make a test call to voicemail (usually to extension 5555) and check CallPilot answers.

STAT ELAN in LD 48:

.stat elan

SERVER TASK:  ENABLED
ELAN #: 016  DES: CALLPILOT
   APPL_IP_ID: 192 .168 .2 .10 LYR7: ACTIVE  EMPTY   APPL ACTIVE     ⇐ Good!

If the CDN doesn't acquire, make sure you can PING the CallPilot server from the Call Server in LD 117:

.stat elan

SERVER TASK:  ENABLED
ELAN #: 016  DES: CALLPILOT
   APPL_IP_ID: 192 .168 .2 .10 LYR7: DOWN DSBL                       ⇐ Bad!

.****ld 117

=> ping 192.168.2.10

PING 192.168.2.10 FAILED                                             ⇐ Check ELAN connections