Step 1.
MGCF receives an INVITE request, containing an initial SDP, through one of the origination procedures and via one of the inter-serving procedures.
Step 2.
MGCF initiates a H.248 interaction to pick an outgoing channel and determine media capabilities of the MGW.
Step 3.
MGCF determines the subset of the media flows proposed by the originating endpoint that it supports, and responds with an Offer Response message back to the originator. This response is sent via the S-S procedure.
Step 4.
The originating endpoint sends a Response Confirmation. The Response Confirmation may also contain SDP. This may be the same SDP as in the Offer Response sent in Step 3 or a subset. The originating UE is free to continue to offer new media on this operation or on subsequent exchanges using the Update method.
Step 5.
MGCF initiates a H.248 interaction to modify the connection established in step #2 and instruct MGW to reserve the resources necessary for the media streams.
Step 6.
MGCF responds to the offered media towards the originating party.
Step 7.
GW reserved the resources necessary for the media streams.
Step 8.
When the originating endpoint has completed its resource reservation, it sends the successful Resource Reservation message to MGCF, via the S-S procedures.
Step 9.
MGCF sends an IAM message to the PSTN.
Step 10.
MGCF sends response to the successful resource reservation towards originating end.
Step 11.
The PSTN establishes the path to the destination. It may optionally alert the destination user before completing the session. If so, it responds with an ACM message.
Step 12.
If the PSTN is alerting the destination user, MGCF indicates this to the originating party by a provisional response indicating Ringing. This message is sent via the S-S procedures.
Step 13.
When the destination party answers, the PSTN sends an ANM message to MGCF.
Step 14.
MGCF initiates a H.248 interaction to make the connection in the MGW bi-directional.
Step 15.
MGCF sends a SIP 200-OK final response along the signalling path back to the session originator.
Step 16.
The Originating party acknowledges the final response with a SIP ACK message.