Operations and Maintenance Guide
Chapter 4 Operating the BTS
Download this chapter
Chapter 4 Operating the BTSChapter 4 Operating the BTS
Download the complete book
Operations and Maintenance GuideOperations and Maintenance Guide (PDF - 2 MB)
give_us_feedback

Table Of Contents

Operating the BTS

Introduction

Managing Subscribers

Viewing Calls

Using Status and Control Commands

Using Show and Change Commmands

Viewing and Deleting Transactions

Scheduling Commands


Operating the BTS

Revised: September 25, 2009, OL-12797-09

Introduction

This chapter tells you how to operate the BTS. This chapter assumes the following are true:

•Connecting components have been correctly installed.

•Connecting components have been successfully started.

•You are a system administrator with past BTS experience.

Managing Subscribers

Table 4-1 Managing Subscribers 

Task
Sample Command

Activating added subscribers 

control subscriber-termination id=<subscriber id>; target-state=INS; mode=FORCED;

Deactivating subscribers

Force the subscriber OOS: 

control subscriber-termination target-state=oos; mode=forced; id=<subscriber id>;

Force the subscriber's MTA OOS: 

control mgw id=<mgw-id>; target-state=oos; mode=forced;

Disassociate the subscriber from VoIP service: 

delete subscriber-service-profile sub-id=<subscriber id>; service-id=1;

Remove the subscriber from the BTS database: 

delete subscriber id=<subscriber-id>;

Remove VoIP service from the subscriber's MTA: 

delete termination prefix=aaln/; port-start=1; port-end=2; mgw_id=<mgw-id>;

Remove the subscriber's MTA from the BTS: 

delete mgw id=<mgw-id>;

Bypassing LNP queries for ported-in numbers

After activating a ported-in number, update the BTS so calls to this number from MTAs on the BTS directly route to the MTA associated with the ported-in number: 

change dn2subscriber office-code-index= 
	<office-code-index of ported TN's NPA-NXX>; 
dn=<XXXX of the ported TN>; lnp-trigger=N;

Ensuring LNP queries for ported-out numbers

Update the BTS so calls to this number perform an LNP query: 

change dn2subscriber office-code-index= 
	<office-code-index of ported TN's NPA-NXX>; 
dn=<XXXX of the ported TN>; lnp-trigger=y;

Assigning a DN ported-out status

Note Wait for the CLEC to confirm the transfer before changing the DN status on the BTS. Initially, calls to the DN may have to route to the porting-out subscriber's MTA using LNP. 

change dn2subscriber office-code-index= 
	<office-code-index of porting TN's NPA-NXX>;  
dn=<XXXX of the porting TN>; status=ported-out; sub-id=null;

Disconnecting service to ported subscribers

1. Assign time and date to disconnect service.

2. Send service disconnection notice to NPAC SMS.

3. NPAC SMS broadcasts this to all service providers.

4. NPAC SMS removes the ported number from its database.

5. All service providers remove the number from their LNP databases.

6. Calls to the number route as if it was non-ported.

Viewing subscribers voice mail indicator (VMI) status 

status subscriber ID=278-222-1917

Note For MGCP subscribers only.

Resetting subscribers voice mail waiting indicator (VMWI) 

control subscriber ID=278-222-1917; mwi=on

or 

control subscriber ID=278-222-1917; mwi=off

Changing subscribers ring and call waiting tone 

change dn2subscriber DN=4692553010; RING_TYPE=4; CWT_TYPE=4;

Note The CWT_TYPE has no effect on SIP subscribers. Their IP phones control how they receive call waiting tones.

Deleting subscribers secondary DNs

Delete one secondary DN for a subscriber: 

delete dn2subscriber FDN=4692553010;

Delete all secondary DNs for a subscriber: 

delete dn2subscriber SUB_ID=SUBSCRIBER_1; VIRTUAL_DN=Y;

Changing subscribers announcements

Delete the changed-number entry. 

delete changed-number old-DN=<old-DN>;

Change the status of the old DN to DISC in the dn2subscriber table. 

change dn2subscriber DN=<old-DN>; status=DISC;

Changing subscribers DNs

Change the subscriber DN to the new DN. 

change sub id=<id>; dn1=<new-DN>; CN-REFERRAL=Y;

Example: 

change sub id=sub1; dn1=206-222-1841; CN-REFERRAL=Y;

The CN-REFERRAL token adds an entry in the changed-number table for the changed subscriber DN. By default, the CN-REFERRAL token is set to Y. If the CN-REFERRAL token is set to N, the changed-number table is not updated with the changed number information.

Use the show subscriber command to verify the new DN. 

show sub id=<id>

Example: 

show sub id=sub1; 

Dn1 indicates 206-222-1841

Verify that the changed number (old DN) of the subscriber is being tracked in the changed-number table. 

show changed-number old-dn=<old-dn>

Example: 

show changed-number OLD-DN=206-222-2345

Use the dn2subscriber table to verify that the old DN is in CN state and new DN is in assigned state. Check if the status of the old DN is CN. 

show dn2subscriber FDN=<old-DN>;

Example: 

show dn2subscriber FDN=206-222-2345;

Check if the status of the new DN is assigned. 

show dn2subscriber FDN=<new-DN>;

Example: 

show dn2subscriber FDN=206-222-1841;

Place an incoming call to the new DN and verify the call is setup successfully.

Place an incoming call to the old DN and verify that the announcement played is "<old DN> has been changed to <new DN>."

If an announcement is not played, do the following:

Verify if the release cause id maps to annc-id=118. 

show release-cause id=22;

Verify if the announcement id maps to announcement-number 301. 

show annc id=118;

Note If there is no referral number (that is, when CN-REFERRAL is set to N where the new number is private), the BTS 10200 plays a generic announcement indicating that the number has changed. No further information is provided on the new number.


Viewing Calls

These tasks allows you to view information related to call forwarding features.

If A calls B and the call is forwarded to C:

•Querying A shows A is connected to C and provide C's information.

•Querying C shows C is connected to A and provide A's information.

•Querying B shows A is calling C and the call is forwarded through B.

•Even when the call is forwarded through B, B can originate another call. B can also forward multiple calls.

When viewing Three-Way Call and Call Waiting calls remember the output shows both calls.

Table 4-2 Viewing Calls 

Task
Sample Command

Viewing active calls 

query call-trace subscriberDN/FQDN/NPA-NXX-****/aaln/*@*

Viewing call trace summaries, started when subscriber presses *57 

report call-trace-summary

Note The report appears on the screen andit does not generate in HTML.


Using Status and Control Commands

Table 4-3 Using Status and Control Commands 

Task
Sample Command

Viewing BTS system status 

status system;

Viewing component states

status element-manager id=EM01;

Possible states:

•STARTUP—During platform startup, the two sides are communicating to determine which side will come up active.

–INIT-NORMAL—primary will be active, secondary will be standby; switchover allowed.

–INIT-FORCED—primary will be forced to active or standby, secondary will be forced to standby or active; no switchover allowed.

•ACTIVE-NORMAL—primary is active, secondary is standby; switchover allowed.

•ACTIVE-FORCED—primary or secondary has been forced to active; no switchover allowed.

•STANDBY-NORMAL—primary should be active, secondary should be standby; switchover allowed.

•STANDBY-FORCED—primary or secondary has been forced to standby; no switchover allowed.

•TRANSITION-TO-ACTIVE-NORMAL—primary is going to active, secondary is going to standby; switchover allowed.

•TRANSITION-TO-ACTIVE-FORCED—primary has been forced to active or standby; secondary has been forced to standby or active; no switchover allowed.

•TRANSITION-TO-STANDBY-NORMAL—primary is going to standby, secondary is going to standby; switchover allowed.

•TRANSITION-TO-STANDBY-FORCED—primary has been forced to active or standby; secondary has been forced to standby or active; no switchover allowed. 

Tip Use status application for more detailed information.

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

Using Show and Change Commmands

Table 4-4 Using Show and Change Commands 

Task
Sample Command

Viewing subscriber-related batch data: subscribers, terminations, subscriber service profiles 

show subscriber limit=1000; start_row=<next page 
value>;display=id,sub_service_profile; order=id;

Where

•limit—Page size for the maximum number of rows (or lines) to display

•start_row—Which page to display first

•display=id—Sorts data by id column

•order=id—Provides a key for ordering or sorting the data

Viewing database usage statistics 

show db-usage table-name=dial_plan;

Note Do not use hyphens in table names; instead use underscores.

Changing database usage statistics 

change db-usage table-name=dial-plan; 
minor-threshold=70;major-threshold=80; critical-threshold=95;

Viewing and Deleting Transactions

The Transaction Queue tracks updates to EMS database, and the shared memory of the CAs and FSs. Entries should remain in the transaction queue for a few seconds, unless an EMS, CA, or FS in an error state. In case of an error state, the transaction queue to stores entries for later updates.

Table 4-5 Viewing and Deleting Transactions 

Task
Sample Command

Viewing transaction queue entries 

show transaction-queue target=CA146

Following is an example of the system response to this command.

TRANSACTION_ID=3910358747849163606
SEQUENCE_NUM=0
TARGET=CA146
STATEMENT=INSERT INTO CARRIER (ID) VALUES ("3434")
TIMESTAMP=2007-10-24 16:13:05
ACTIVE_TARGET=Y
USERNAME=btsadmin
TERMINAL=CMD-1!USR6!priems121
STATUS=PENDING

Deleting transaction queue entries 

delete transaction-queue target=CA146
Caution This command causes a database inconsistency. Call TAC before using it.

Scheduling Commands

Schedule a command to execute daily, weekly, or monthly at a specific time. You can remove the command at any time. If the command is scheduled to recur and is currently executing it completes in a normal fashion and is removed from the list going forward. Using start-time and recurrence command tokens, schedule commands at any time and frequency.

Table 4-6 Scheduling Commands 

Task
Sample Command

Viewing scheduled commands 

show scheduled-command id=1234;

Adding scheduled commands 

add scheduled-command start-time=2001-10-01 12:22:22; 
noun=database; verb=audit;

Changing scheduled commands 

change scheduled-command id=1234; start-time=2001-10-02 20:00:00;

Deleting scheduled commands 

delete scheduled-command id=1234;