Difference between revisions of "RequestReportBCSMEvent"

Latest revision as of 18:16, 27 August 2013

[edit] Capability: Camel

[edit] Usage

This operation is used to request by the gsmSCF that the gsmSSF should monitor for a call event (e.g., busy or no answer), then send a notification back to the gsmSCF when the event is detected.

[edit] Expected actions

• The requested events are monitored until the monitoring is ended, until the end of the call, until the requested events are detected or the corresponding call leg is released.

[edit] Invoke parameters

• bcsmEvents – list of parameters which specify the event/events for which a report is requested. An event is specified by the following parameters:
  • eventTypeBCSM – type of event for which a report is requested. Values “collectedInfo” and “termAttemptAuthorize” aren't valid for this operation.
  • monitorMode – indicates how the event is to be reported. If its value is “interrupted”, the event is reported as a request, if its value is “notifyAndContinue”, the event is reported as a notification, if its value is “transparent”, the event is not reported.
  • legID – the party of the call for which the event is to be reported. The gsmSCF uses only the “sendingSideID” only.
    • sendingSideID
  • dPSpecificCriteria – specific information specific to the DP to be armed
    • applicationTimer
• extensions

[edit] Result parameters

This operation does not expect a result.

[edit] Example

<component localCID="1" type="Invoke" operationCode="requestReportBCSMEvent">
    <bcsmEvents>
        <bcsmEvent>
             <eventTypeBCSM>tAnswer</eventTypeBCSM>
             <monitorMode>transparent</monitorMode>
             <legID>
                 <receivingSideID>leg2</receivingSideID>
             </legID>
             <dPSpecificCriteria>
                 <applicationTimer>25</applicationTimer>
             </dPSpecificCriteria>
        </bcsmEvent>
    </bcsmEvents>
</component>