ed PDU session type > QoS rules - Authorized QoS rules > Session-AMBR > PDU address > S-NSSAI > Always-on PDU session indication > Mapped EPS bearer contexts > QoS flow descriptions - Authorized Extended protocol configuration options Element ID: 0x7b Length: 61 [Link direction: Network to MS (1)] = Extension: True .000 = Configuration Protocol: PPP for use with IP PDP type or IP PDN type (0) > Protocol or Container ID: DNS Server IPv6 Address (0x0003) > Protocol or Container ID: DNS Server IPv6 Address (0x0003) > Protocol or Container ID: P-CSCF IPv6 Address (0x0001) > Protocol or Container ID: Network support of Local address in TFT indicator (0x0011) > DNN Figure 7.23 - Packet capture SMF to AMF N1N2 message transfer Figure 7.24 depicts the contents of a successful N1N2 message transfer transaction: SMF->AMF [23] N1N2 Message Transfer success HyperText Transfer Protocol 2 Stream: WINDOW_UPDATE Stream ID: 0, Length 4 Stream: SETTINGS, Stream ID: 0, Length 0 Stream: HEADERS, Stream ID: 3, Length 15, 200 OK Stream: DATA, Stream ID: 3, Length 37 JavaScript Object Notation: application/json Object Member Key: cause String value: N1_N2_TRANSFER_INITIATED Key: cause Figure 7.24 - Packet capture SMF to AMF N1N2 Message Transfer Success Step 23: The AMF acknowledges the request with 200 OK and responds with a cause, N1+N2+TRANSFER INITIATED. Step 24: Resource setup for the uplink tunnel. VoNR call flow Step 25: PDU establishment response to the UE. Step 26: The downlink tunnel of gNB. Step 27: The AMF sends a PDU session update SMC context request to the SMF, which triggers the SMF to (optionally) start establishing N4 to the UPF to retrieve GTP tunnel identifiers, or retrieve them from an already established N4 tunnel if established asynchronously. Step 28: The SMF sends the tunnel information to the UPF for setting up the downlink data path. Steps 29 and 30: The Sx modification response will contain the status of the transaction - whether it has passed or failed. If it was successful, it will convey the same to the A