
|
| Call Processor Maintenance | 63 | |
| Table 29 Call Processor State Tab (continued) |
|
| |
|
|
|
|
|
| Attribute | Description | Settings |
|
|
|
|
|
|
| Software status | The current operational state of the entity. If |
| |
|
| AdminStatus is down, then OperStatus should |
|
|
|
| be down. If AdminStatus is changed to up, |
|
|
|
| through the entity command interface, then |
|
|
|
| OperStatus should change to up if the entity |
|
|
|
| is operational; it should remain in the down |
|
|
|
| state if and only if there is a fault that |
|
|
|
| prevents it from going to the up state; it |
|
|
|
| should remain in the notPresent state if the |
|
|
|
| entity has missing components. If the entity is |
|
|
|
| operational, but not responding to queries, |
|
|
|
| the state is notResponding. |
|
|
|
|
|
|
|
| Usage State | Indicates how busy the resource is. |
| |
|
| |||
|
|
|
|
|
Call Processor | This section provides maintenance tasks that are specific to just the call | |||
Maintenance | processor. |
|
|
|
Restarting the Call To restart the Call Processor:
Processor1From the EMS explorer tree, navigate to the 3Com Sip Call Processor.
2
Stopping the Call To stop the Call Processor:
Processor
1From the EMS explorer tree, navigate to the 3Com Sip Call Processor.
2