3G Call flow (Voice Call) 1. The mobile equipment, (ME), (i.e.

User Equipment, UE) requests the network to set up a connection to a B-party in another network (in our case the PSTN/ISDN network). The message sent over the air interface to RNC is the SETUP message. 2. The RNC sends the SETUP message to the MSC server with all necessary information to complete the call set up. The called party number and the type of the call are submitted. After the analysis the MSC finds that the call is a speech call to another network. 3. In order to complete the call the MSC must seize all required resources in its own control area. The MSC then contacts the appropriate Media Gateway (MGW) at the edge of the connectivity network. A SEIZE RESOURCE message is sent to the selected MGW in order to seize resources to complete the connection. 4. The MGW confirms that necessary resources are reserved. An ACKNOWLEDGEMENT (ACK) message is sent to the MSC server. 5. The MSC server informs the RNC that the call set up is proceeding with a CALL PROCEEDING message that contains a progress indicator. 6. The MSC server now requests from the RNC to set up a switched virtual connection (SVC) towards the selected MGW with an ASSIGNMENT message. 7. RNC signals across the ATM network to the selected MGW and sets up an AAL2 connection (ERQ, Establishment Requested message). 8-9. The MGW confirms the AAL2 connection set up towards the RNC by sending an ECF (Establishment Confirmed) message. Both RNC and MGW have activated the AAL2 resources. A virtual ATM connection exists now from RAN to the edge MGW. 10. The RNC informs the MSC server that this switched virtual connection is now set up with an ASSIGNMENT COMPLETE message. 11. The MSC server proceeds in the call set up phase by contacting the appropriate transit server. The transit server is responsible for the signaling interconnect towards the external circuit switched network. This is done by sending the Initial Address Message (IAM), which contains complete routing information, including the address to the previously selected MGW. 12. The transit server contacts the MGW and reserves necessary outgoing resources towards the PSTN/ISDN network by sending the SEIZE RESOURCE message. 13. The MGW answers the seizure request by informing the GMSC that necessary resources are reserved. An ACKNOWLEDGEMENT message is sent to the GMSC server.

14. The GMSC transit server proceeds by contacting the external network in order to terminate the call towards the B-party. The IAM message is forwarded to the PSTN/ISDN network. 15. The external network acknowledges that the received address is understood and the call set up is proceeding by sending the Address Complete Message (ACM). 16. The transit server informs the MSC server that call set up towards B-party is proceeding by 17. MSC server orders the MGW to through-connect reserved resources backwards (towards A- party). The codecs and other resources are reserved all the way out to the A-party. 18. MSC server informs the RNC that B-party is alerted. The user equipment will be informed by the ALERT message and produces proper alerting echo tone. 19. When the B-party answers the call, the external network signals this to the GMSC transit server by sending the Answer Message (ANM). 20. The transit server sends the same message, the ANM, towards the MSC server, i.e. B-party has answered the call. The MSC server will now start the procedure to connect even the A-party. 21. MSC server orders both way through connection from the MGW, that is a speech path establishment on the connectivity layer. The MGW resources are already seized as a result of previous seizure messages. 22. With the CONNECT message MSC server orders the RNC to connect the call to the user equipment on the traffic channel. This message reaches the A-party's mobile equipment. This message indicates to the call control entity of the calling mobile station that a connection has been established through the network. 23. RNC acknowledges the connection. 24. The call set up is complete. The user equipment is communicating with the Bparty across RAN, the Core Network and the external network.