![](https://pdfstore-manualsonline.prod.a.ki/pdfasset/f/cc/fcca7184-1660-4620-9680-bdb9cfd0a74e/fcca7184-1660-4620-9680-bdb9cfd0a74e-bg46.png)
4-8
Cisco BTS 10200 Softswitch Operations and Maintenance Guide, Release 6.0.x
OL-16000-07
Chapter 4 Operating the BTS
Using Status and Control Commands
Changing states of
component pairs
(EMS, BDMS, CA,
and FS)
control call-agent id=CA146; target-state=FORCED-STANDBY-ACTIVE;
Possible states:
• ACTIVE_STANDBY
• STANDBY_ACTIVE
• NORMAL—Primary is active and secondary is standby.
• FORCED-ACTIVE-STANDBY—Primary has been forced to active and
secondary is standby.
• FORCED-STANDBY-ACTIVE—Primary has been forced to standby and
secondary is active.
Viewing component
application states
status application id=CA146;
Changing
component
applications states
(in-service or OOS)
control application id=CA146; action=star;node=prica06
Caution This negatively impacts the performance of the BTS host.
Activating media
gateways
Ensure the MG exists, then enter:
control mgw id=<mgw-id>; target-state=ins; mode=forced;
where
• mgw id—the voice port on the subscriber’s MTA (the voice port’s MAC
address without hyphens)
• target-state—ins to show in service for all activations
• mode—forced for all activations
Setting subsystem
groups/OPC in or
OOS
control subsystem_grp id=CNAM; mode=forced; target_state=UOS;
This sets the state of the individual subsystems within the subsystem group as
well. If a subsystem/OPC combination is taken OOS individually, the state of
the subsystem group may be in service while some members of the group are
out of service.
Viewing subsystem
groups/OPC status
status subsystem_grp id=CNAM
Table 4-3 Using Status and Control Commands (continued)
Task Sample Command