CP Shutdown impact on Symposium

[kd99]

Our environment has Symposium 5.0 with Call Pilot 2.02 providing access link messaging. We have shutdown SCCS several times without having to touch the CP and the access link is unaffected. Just wondering if the reverse is true. If Call Pilot is shut down will the Symposium need to be restarted to reactivate the access link?

 

[pbxn]

If you reboot both at the same time, then yes. I think you have to bring CP up first before Symp. I did an IP change awhile ago and couldn't get mail back up to take calls. Symp was brought up first and tried to take the mail cdn for itself.

 

[lretrievers]

Both servers should be brought down, first bring Symposium completely up (all services up), and then bring up the Call Pilot. You should be fine. Shutting down one, or an INI of the switch, or any interruption of service on any 3 of these components can cause the systems to get out of sync with each other.

I am not sure why Symposium would try to grab the CDN of the Call Pilot, unless you have it configured as a CDN in the Symposium (it shouldn't be there, only the ACD - DN of the Access Ports should be in the Symposium.

 

[pbxn]

I'm not sure either lretievers, but I have seen it happen. When I did IP changes on my telecom stuff, I could not get CP to take calls. Boggled the crap out of me, I ended up calling my vendor, they toyed with it for a awhile as well, and thats when we found out the Symposium, I would guess, assumes that CDN's belong to it, such a possesive little thing, lol.

 

[yyrkroon]

When setting up the VAS, if you don't have SECU set to YES, you will run into problems like this.

When CP and SECC/SCCS are both installed, the SECU on the VAS (for both elan) MUST be set to YES.

 

[ss341]

FYI
I have found that when Symposium is booted up it will attempt to take the lowest numbered link available.
If all links are up and in use you can boot til the cows come home with no problems. That goes for CallPilot as well. But if everything is down (i.e. power failure) and you have the CallPilot say on Elan 16\Vas 16 and the Symposium on Elan 17\Vas 17, be sure to boot the CallPilot first other wise the Symposium will grab 16 if it comes up first. (and it won't work)

 

[lretrievers]

Keep in mind that Symposium has to acquire the Access Ports first, not Call Pilot.

 

[croat1]

Had a problem recently with SCCS grabbing CP CDN's
SECU was set to YES.

We had to do PBX INI in order to resolve the things.

And yes, SCCS should always come up first as it needs to grab lower VAS ID

 

[Milesprower]

When call pilot is booting up, it must see the Meridian Link Service from SCCS. This is how Call Pilot keeps track of the voice port start/stop status.

If Call Pilot does not see Meridian Link when it is initializing, then access messaging will not work. For this reason Nortel directs that the SCCS be brought up first, then Call Pilot.

Once the systems are up and in sync, you should be able to reboot SCCS and still have functional access messaging.

Because SCCS needs to come up first it is normally assigned ELAN 16 and Call Pilot ELAN 17.