Call Pilot rls 2.5 keeps going down and has to be rebooted. when it goes down or during reboot scrolls error : MAS NOTIFICATION Failure. after a while it will come up . I have already moved to Dongal and HD to another CP hardware but still seems to have problems. What is the MAS Notification failure telling us
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Call Pilot keeps going down
- Thread starter trclubb
- Start date
Firebird Scrambler
Systems Engineer
I've found these old records below
MAS EMCI service fails to start on a call pilot 201i server
call pilot 1.07, 201i platform
After re-loading a faulty 201i server the call pilot 'mas emci' service would not come back into service. By disconnecting the mouse, keyboard & Monitor cables and re booting the call pilot server everything came up correctly. The mouse monitor & keyboard could then be connected after.
##########################################################################
This problem may occur if the MAS Link Handler service does not start after a reboot. The service requires a manual intervention for it to start. The service is set to automatic but still does not start on its own.
Problem Resolution
Ensure all Dependency services of MAS LinkHandler Port #2 service are set to start up automatically. In Windows services, check that the Event Log, Remote Procedure Call (RPC) and Remote Procedure Call (RPC) Locator services are all set to automatic by right-clicking on each service and selecting properties. The startup type should be set to automatic. If it is not, select automatic from the drop down box and click apply.
Right-click on properties of MAS LinkHandler Port #2 service. Click on the recovery tab. Change the computer response for the service failing to 'Restart the Service' for the First failure, Second failure, and Subsequent failures options. Then apply the changes.
The service should now start on its own after a reboot.
####################################################################
If MAS LINK handler server restarts on CCMS, *usually* the call pilot will auto recover and voice prompt integration will come back into service without intervention.
IF this fails however, you would normally shut down Call Pilot and CCMS, restart CCSM then ONCE UP AND RUNNING restart Call Pilot...
If this still does not work, the full proceedure as recomended by AvayaNET is as follows:
1. Restart VSM
2. If step works then the procedure is complete. If it fails then continue
3. Shutdown the Callpilot(CP) server
4. Deacquire the CP resoruces.
>ld 48
>stat elan (to check the elans configured)
>dacr agt <access or ivr port TN> ...repeat for all applicable IVR or access channels
>ld 23
req: dacr
type: <cdn or acd>
cust: <cust no>
acd: <acd dn or cdn>
Use overlays 10,11,20,21 or 23 ro confirm actions
5. Reboot CCMS server
6. Wait until CCMS server is fully recovered. Ensure the VSM, MAS link handler Port #2 & CCMS MLSM _service is running.
7. Power up Callpilot.
To assist with root cause we would need the following traces for the next occurrence:
CCMS:
Windows event logs in text format.
Server utility event logs (all logs levels)
Search for *.hdmp, *.mdmp, drwtsn32.log, user.dmp incl hidden folders.
AML
MLS
Access protocol, access protocol debug, access link and elh traces,
TSM session trace.
VSM session traces .
VSM thread traces level 7.
MAS Link Handler traces
netstat -oan > ccms_netstat.txt
tasklist /svc > ccms_tasklist.txt
Call pilot:
Windows event logs in text format.
Callpilot manager events
SLEE traces.
netstat -oan > cp_netstat.txt
tasklist /svc > cp_tasklist.txt
From CS1K
CS1K-AHST-27-09-2009.txt
CS1K-RDTAIL.txt
Wireshark traces running on a suitable server, not CCMS or Callpilot (not an absolute requirement but preferable).
Firebird Scrambler
Nortel Meridian 1 / Succession and BCM / Norstar Programmer in the UK
Advance knowledge on BCM support
MAS EMCI service fails to start on a call pilot 201i server
call pilot 1.07, 201i platform
After re-loading a faulty 201i server the call pilot 'mas emci' service would not come back into service. By disconnecting the mouse, keyboard & Monitor cables and re booting the call pilot server everything came up correctly. The mouse monitor & keyboard could then be connected after.
##########################################################################
This problem may occur if the MAS Link Handler service does not start after a reboot. The service requires a manual intervention for it to start. The service is set to automatic but still does not start on its own.
Problem Resolution
Ensure all Dependency services of MAS LinkHandler Port #2 service are set to start up automatically. In Windows services, check that the Event Log, Remote Procedure Call (RPC) and Remote Procedure Call (RPC) Locator services are all set to automatic by right-clicking on each service and selecting properties. The startup type should be set to automatic. If it is not, select automatic from the drop down box and click apply.
Right-click on properties of MAS LinkHandler Port #2 service. Click on the recovery tab. Change the computer response for the service failing to 'Restart the Service' for the First failure, Second failure, and Subsequent failures options. Then apply the changes.
The service should now start on its own after a reboot.
####################################################################
If MAS LINK handler server restarts on CCMS, *usually* the call pilot will auto recover and voice prompt integration will come back into service without intervention.
IF this fails however, you would normally shut down Call Pilot and CCMS, restart CCSM then ONCE UP AND RUNNING restart Call Pilot...
If this still does not work, the full proceedure as recomended by AvayaNET is as follows:
1. Restart VSM
2. If step works then the procedure is complete. If it fails then continue
3. Shutdown the Callpilot(CP) server
4. Deacquire the CP resoruces.
>ld 48
>stat elan (to check the elans configured)
>dacr agt <access or ivr port TN> ...repeat for all applicable IVR or access channels
>ld 23
req: dacr
type: <cdn or acd>
cust: <cust no>
acd: <acd dn or cdn>
Use overlays 10,11,20,21 or 23 ro confirm actions
5. Reboot CCMS server
6. Wait until CCMS server is fully recovered. Ensure the VSM, MAS link handler Port #2 & CCMS MLSM _service is running.
7. Power up Callpilot.
To assist with root cause we would need the following traces for the next occurrence:
CCMS:
Windows event logs in text format.
Server utility event logs (all logs levels)
Search for *.hdmp, *.mdmp, drwtsn32.log, user.dmp incl hidden folders.
AML
MLS
Access protocol, access protocol debug, access link and elh traces,
TSM session trace.
VSM session traces .
VSM thread traces level 7.
MAS Link Handler traces
netstat -oan > ccms_netstat.txt
tasklist /svc > ccms_tasklist.txt
Call pilot:
Windows event logs in text format.
Callpilot manager events
SLEE traces.
netstat -oan > cp_netstat.txt
tasklist /svc > cp_tasklist.txt
From CS1K
CS1K-AHST-27-09-2009.txt
CS1K-RDTAIL.txt
Wireshark traces running on a suitable server, not CCMS or Callpilot (not an absolute requirement but preferable).
Firebird Scrambler
Nortel Meridian 1 / Succession and BCM / Norstar Programmer in the UK
Advance knowledge on BCM support
- Status
Similar threads
- Locked
- Question