Arm oDisconnect and tDisconnect Leg 2 as Interrupted

CCF arms all EDPs as notifyAndContinue by default. For a voice charging service, you can configure CAMEL Gateway to arm oDisconnect and tDisconnect leg 2 EDPs as interrupted instead. Then, when MATRIXX Engine receives o/tDisconnect leg 2 armed as interrupted in a TCAP CONTINUE(EventReportBCSM) operation:

• If an ApplyChargingReport (ACR) operation or a CallInformationReport (CIR) operation is expected, or if CCF is configured to disallow sending TCAP END with components, MATRIXX Engine returns TCAP Continue(ReleaseCall).
• Otherwise, MATRIXX Engine returns TCAP END(ReleaseCall).

You enable CAMEL Gateway advanced options during engine configuration by answering y to the following question:

Do you wish to configure advanced options (y/n)?y

To arm oDisconnect/tDisconnect as interrupted for:

• The mobile originating (MO) voice charging service, answer y to the following configuration question:

  Camel Gateway:VCS voice_mo:Should oDisconnect or tDisconnect be armed as interrupted for the Voice MO calls service (y/n)?

• The mobile terminating (MT) voice charging service, answer y to the following configuration question:

  Camel Gateway:VCS voice_mt:Should oDisconnect or tDisconnect be armed as interrupted for the Voice MT calls service (y/n)?

• An additional voice charging service, answer y to the following configuration question:

  Camel Gateway:VCS voice_service:Should oDisconnect or tDisconnect be armed as interrupted for this service (y/n)?