EventReportBCSM

Usage

This operation is used by the gsmSSF to notify the gsmSCF of a call related event for which monitoring was previously requested through a RequestReportBCSMEvent operation.

Expected actions

• While monitoring of multiple events can be requested through a single RequestReportBCSMEvent operation, each monitored event is reported separately through a EventReportBCSM.

Invoke parameters

• eventTypeBCSM – the type of event being reported. Possible values are:
  • collectedInfo
  • routeSelectFailure
  • oCalledPartyBusy
  • oNoAnswer
  • oDisconnect
  • oAbandon
  • termAttemptAuthorized
  • tBusy
  • tNoAnswer
  • tAnswer
  • tDisconnect
  • tAbandon
• eventSpecificInformationBCSM - contains specific call related information:
  • for eventTypeBCSM “routeSelectFailure”, this parameter will contain the “failureCause” if available.
  • for “tBusy”, “busyCause” may be present.
  • for “tNoAnswer”, the parameter may contain the “callForwarded” reason.
  • for “oDisconnect”/”tDisconnect”, the parameter will contain the “releaseCause” if possible.
  • for events “oNoAnswer”, “oAnswer”, “tAnswer”, this parameter will be empty.
• legID – the party of the call for which the event is reported. In this case, the gsmSSF will use the “receivingSideID” option only.
• miscCallInfo – indicates the DP (Detection Point) related information. It contains the following parameter:
  • messageType: can have values “request”/”notification”

• extensions

Result parameters

This operation does not expect a result.

Example

<component remoteCID="1" type="Invoke" operationCode="eventReportBCSM">
     <eventTypeBCSM>tDisconnect</eventTypeBCSM>
     <eventSpecificInformationBCSM>
         <oCalledPartyBusySpecificInfo>
              <busyCause>29 03</busyCause>
         </oCalledPartyBusySpecificInfo>
     </eventSpecificInformationBCSM>
     <legID>
         <receivingSideID>leg2</receivingSideID>
     </legID>
     <miscCallInfo>
         <messageType>notification</messageType>
     </miscCallInfo>
</component>