If you have integrated CallPilot and Symposium (that is, you are using Give IVR and/or ACCESS to give recordings to callers in queue via CallPilot), then Symposium needs to be booted first. Let it come all the way up, especially the MLSM service. CallPilot needs to come up then. The reason is that CallPilot needs to register with the Symposium, and it cannot do that until Symposium has all its services functional. You could go into CallPilot and set a boot delay of, say, 300 seconds. Then you could boot both at the same time and CallPilot would still come up last.
sandy nailed that one, the boot delay was added to allow sympoiuun to boot 1st, very handy when the power does the reboot for you.. in the earlier rls's i did a ip address change on both due to a network change, and almost never found the boot sequence problem that was killing me.. the cp was acquiring the cdn's before the symposium was, even though the ast was set right.. if you have a problem, check that, after i got cp up i had a nortel symposium super tech on the line and it still took most of the night. i hated to reboot the cp and the switch again because the 1st time, the elnk wouldn't ping out.. i had to change a param, edd and cold start.. plus i had the most nervous cust in the world in the switchroom, and i wasn't their usual tech, we had never met, and tommy was the only tech that they trusted.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.