Cisco BTS 10200 Softswitch Long Duration Call Cutoff Feature Module
Revised: July 31, 2008
This document describes the Long Duration Call Cutoff feature for Release 6.0.x of the Cisco BTS 10200 Softswitch. This document includes the following topics:
Understanding the Long Duration Call Cutoff Feature
The Long Duration Call Cutoff feature allows the service provider to disconnect the calls that run for a long period of time.
To enable this feature, the service provider needs to configure a new parameter, LONG-DURATION-CALL-CUTOFF-TMR in the CA-CONFIG table. This parameter (timer) can take values from 0 to 48 (hrs). The timer starts when the subscriber answers the call; and the call is disconnected when the timer expires.
Note This feature can be provisioned only by the service provider.
Provisioning the Long Duration Call Cutoff Feature
The LONG-DURATION-CALL-CUTOFF-TMR parameter has been added to the CA-CONFIG table (see Table 1).
Indicates the timer value for the Long Duration Call Cutoff.
0 indicates that timer is not set and the call is not cut off. Any integer value between 1 and 48 indicates that the call is cut off after the specified number of hours.
A new Service ID with value 85 has been added in the Call Detail Block (CDB) record for the Long Duration Call Cutoff feature. For more information on Service ID and CDB record, refer to the Feature Server-Derived Call Data chapter in Cisco BTS 10200 Softswitch Billing Interface Guide, Release 6.0.x.
Table 2 shows the feature-related data that is placed in the CDB record for the Long Duration Call Cutoff feature.
Table 2 Feature and Associated Call Detail Block Field
Feature Name
Field
Value
Associated CDB Field
LONG-DUR-CUTOFF
Service Id
85
ServiceType1, ServiceType2, or ServiceType3
Service Status
INSTANCE
ServiceStatus1, ServiceStatus2, or ServiceStatus3
Feature Data
—
—
Result
—
ServiceResultCode1, ServiceResultCode2, or ServiceResultCode3
When the LONG-DURATION-CALL-CUTOFF parameter interacts with certain features, the behavior of this parameter changes. Table 3 provides the interaction scenarios of the LONG-DURATION-CALL-CUTOFF parameter with
•Call Transfer (CT)
•Call Forwarding
•Three-Way Calling (TWC)
•Call Hold (CHD)
•Call Park (CPRK)
Table 3 Sample Scenarios
Feature Behavior with...
Scenarios
CT
Scenario 1
Subscriber A has the CT feature.
A calls Subscriber B; when the call is answered, the long duration call cutoff timer (t1) starts.
A hookflashes and calls Subscriber C. When C answers the call, another timer (t2) starts.
A transfers the call; and B and C are in an active call.
When A transfers the call, timer t1 stops; when timer t2 expires, the call between B and C is disconnected.
Scenario 2
Subscriber B has the CT feature.
Subscriber A calls B. Timer t1 is started when the call is answered by B.
B hookflashes and calls Subscriber C. When C answers, timer t2 is started.
B transfers the call, and A and C are in an active call.
When timer t1 expires, the call between A and C is disconnected.
Call Forwarding
Subscriber A calls Subscriber B. B does not answer and the call is forwarded to Subscriber C.
When C answers the call, timer t1 starts for the call between A and C.
This call is disconnected when timer t1 expires.
TWC
Scenario 1
Subscriber A calls Subscriber B. B answers the call and timer t1 starts.
A hookflashes and calls Subscriber C.
C answers the call and timer t2 starts (on A's phone).
A hookflashes again and all three subscribers are in conference. (A is the originator of both calls.)
When timer t1 expires, the call between A and B is disconnected, and when timer t2 expires, the call between A and C is disconnected.
TWC
Scenario 2
Subscriber A calls Subscriber B.
B answers the call and timer t1 starts on A's phone. (B is the terminating party.)
B hookflashes and calls Subscriber C.
C answers the call and timer t2 starts on B's phone. (B is the originating party.)
B hookflashes and all the three subscribers are in conference.
When timer t1 expires, the call from A to B is disconnected; the call from B to C is disconnected only when timer t2 expires.
CHD
Scenario 1
Subscriber A has CHD service.
A calls Subscriber B. B answers the call, and timer t1 starts on A's phone.
A hookflashes, dials the CHD VSC code, and calls Subscriber C.
C answers the call and timer t2 starts on A's phone.
A and C are in an active call.
When timer t1 expires, the call between A and B is disconnected. When timer t2 expires, the call between A and C is disconnected.
Scenario 2
Subscriber A has CHD service.
A calls Subscriber B and B answers the call. Timer t1 is starts on A's phone.
A hookflashes, dials CHD VSC code, and calls Subscriber C.
C answers the call and timer t2 is started on A's phone. A and C are in an active call.
A hookflashes again and dials the CHD VSC code.
Now, A and B are in an active call.
When timer t1 expires, the call between A and B is disconnected. A then hookflashes to get back to C. When timer t2 expires, the call between A and C is disconnected.
Scenario 3
Subscriber B has the CHD service.
Subscriber A calls B.
B answers the call, and timer t1 starts on A's phone. (B is the terminating party.)
B hookflashes, dials the CHD VSC code, and calls Subscriber C.
C answers the call and timer t2 starts on B's phone. (B is the originating party here.)
B and C are in an active call now.
When timer t1 expires, the call between A and B is disconnected. The call between B and C is disconnected, only when timer t2 expires.
CPRK
Scenario 1
Subscriber B has CPRK service, and Subscriber C has CPRK_RET service.
Subscriber A calls B.
B answers the call, and timer t1 is started on A's phone.
B parks the call to another DN.
C retrieves the call, and another timer t2 started.
A and C are in an active call.
When timer t1 expires, the call between A and C is disconnected.
Scenario 2
Subscriber A has CPRK service.
A calls Subscriber B.
B answers the call, and timer t1 is started on A's phone.
A parks the call.
No other subscriber retrieves the call.
When the timer (t1) expires, the call to B is disconnected.
Scenario 3
Subscriber A has CPRK service, and Subscriber C has CPRK_RET service.
A calls Subscriber B.
B answers the call, and timer t1 starts on A's phone.
A parks the call.
C retrieves the call, and timer t2 starts.
B and C are in an active call.
When the timer t1 expires, the call between B and C is disconnected.
CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, Cisco TelePresence, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0807R)
Understanding the Long Duration Call Cutoff Feature
