Event ACRs for SMS

The SBC generates call data event records with information for SMS that differs somewhat from that of calls. You configure the SBC to generate ACRs for SMS using the same procedures you use for calls, which then treats the SMS messages as events, similar to call data during registrations.

End stations send SMS messages using a SIP MESSAGE (content-type=application/vnd.3gpp.sms) with a GSM-SMS body. The SBC complies with 3GPP specifications 23.040 (Technical realization of the Short Message Service (SMS) and 24.011 Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface) with respect to message format. The SBC parses message information for AVP data during message processing and ultimately provides ACRs to the CCF using the Rf interface.

SMS processing that includes ACR generation includes a separate timer, the sms-report-timeout within the sip-config, for SMS accounting. If the SBC does not receive a delivery report /submit report within this timer's value, it discards all accounting for that message. The diagrams below present the start and stop locations of this timer within the context of overall ACR generation.

The call flow diagram below illustrates the SBC, as P-CSCF, gathering data for the SMS report during a message originating scenario. The SBC ultimately issues the ACR after the message delivery is complete.

This call flow illustrates the OCSBC, as P-CSCF, gathering data for the SMS report during a message originating scenario.

The call flow diagram below illustrates the SBC, as P-CSCF, gathering data for the SMS report during a message terminating scenario.

This call flow diagram illustrates the SBC, as P-CSCF, gathering data for the SMS report during a message terminating scenario.