Call Flow

An example call flow between a ARIA endpoint, the OracleSD, and a Gateway/Application Server illustrates a successful call establishment where the call is originated from an ARIA enabled phone and destined to a core network server.

      ARIA phone            Acme SD          Gateway/App Server
 1.       |  INVITE/SDP        |                    |
          | ---------------->  |                    |
                               |  INVITE/SDP        |
          |                    | ---------------->  |
 2.       |  100 TRYING        |                    |
          | <----------------  |                    |
          |                    |  180 RINGING       |
          |                    | <----------------  |
          |  180 RINGING       |                    |
          | <----------------  |                    |
          |                    |  200 OK/SDP        |
          |                    | <----------------  |
 3.       |  200 OK/SDP        |                    |
          | <----------------  |                    |
          |  ACK               |                    |
          | ---------------->  |                    |
          |                    |  ACK               |
          |                    | ---------------->  |
          |                    |                    |
 4.       | <-SRTP/ARIA media->| <- RTPmedia flow ->|

1. The ARIA-enabled phone sends an INVITE request to the SD with the crypto attribute in the SDP specifying the ARIA 192 CM cipher for encryption and HMAC_SHA1_80 for authentication. The crypto attribute also has the master key encoded in base-64 format, as well the mki parameters (optionally). The SD forwards the INVITE to the called party via the gateway according to the media-security-policy on the outbound realm.
2. The SD sends provisional response to INVITE request
3. Assuming that the SD gets successful answer from called party, the SD sends a 200 OK response to the caller, with the crypto attribute in the accompanying SDP specifying the ARIA 192 CM cipher for encryption and HMAC_SHA1_80 for authentication. The crypto attribute also has the master key, as well the mki parameters (optionally).
4. The ARIA-enabled phone acknowledges the reception of 200 OK final response. At this point, encrypted SRTP traffic using the ARIA 192 counter mode cipher flows between the phone and the SD, and unencrypted traffic flows between the SD and the core network.