12.07.2015 Views

IMS to PSTN Call Flow Poster - EventHelix.com

IMS to PSTN Call Flow Poster - EventHelix.com

IMS to PSTN Call Flow Poster - EventHelix.com

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>IMS</strong> Originating <strong>to</strong> <strong>PSTN</strong> ISUP <strong>Call</strong> (<strong>Call</strong>ed <strong>PSTN</strong> Subscriber Initiates Release)<strong>Call</strong>ing UE <strong>IMS</strong> Core Network <strong>PSTN</strong> Interface<strong>Call</strong>er User Visited <strong>IMS</strong> Home <strong>IMS</strong> Signaling MediaEquipment<strong>Call</strong>er Orig P-CSCF Orig S-CSCF BGCF MGCF IM-MGWEventStudio System Designer 624-Feb-13 15:23 (Page 4)This call flow describes the call setup from one <strong>IMS</strong> subscriber <strong>to</strong> ISUP <strong>PSTN</strong> termination. The call is routed via the BGCF (Border Gateway Control Function) <strong>to</strong> the MGCF (Media GatewayControl Function). The MGCF uses one context with two terminations in IM-MGW (Media Gateway). The termination RTP1 is used <strong>to</strong>wards <strong>IMS</strong> Core network subsystem entity and thebearer termination TDM1 is used for bearer <strong>to</strong>wards <strong>PSTN</strong> CS network element.This sequence diagram was generated with EventStudio System Designer (http://www.<strong>EventHelix</strong>.<strong>com</strong>/EventStudio).<strong>IMS</strong> <strong>to</strong> <strong>PSTN</strong>(ISUP) call setupVoiceRTP: VoiceVoiceBidirectional voice path is now through. The IM-MGW convertsRTP <strong>to</strong> voice and vice versa. UE also maps audio <strong>to</strong> RTP andback.ISUP RELThe call release initiated in the <strong>PSTN</strong> network is received byMGCF is ISUP REL message.BYEThe MGCF responds with call release by sending BYE message<strong>to</strong>wards the <strong>Call</strong>er.Release <strong>IMS</strong> TerminationMGCF requests IM-MGW <strong>to</strong> release RTP1 resource.H.248: SUB.reqContext ID = C1,Termination ID = RTP1H.248: SUB.respContext ID = C1,Termination ID = RTP1Release TDM TerminationMGCF requests IM-MGW <strong>to</strong> release TDM1 resource.H.248: SUB.reqContext ID = C1,Termination ID = TDM1H.248: SUB.respContext ID = C1,Termination ID = TDM1ISUP RLCAfter performing RTP1 and TDM1 resource release, MGCF sendsrelease <strong>com</strong>plete message, ISUP RLC <strong>to</strong>wards the <strong>PSTN</strong>network.Drop media PDP context200 OK (BYE) The <strong>Call</strong>er acknowledges the BYE by sending 200 OK <strong>to</strong>wardsMGCF.This sequence diagram was generated with EventStudio System Designer (http://www.<strong>EventHelix</strong>.<strong>com</strong>/EventStudio).

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!