IMS PSTN Interworking Call Flows, IMSPresence Sequence Diagrams and more
EventHelix Update 23
April 20, 2008
This call flow covers the handling of a CS networkoriginated call with ISUP. In the diagram the MGCFrequests seizure of the IM CN subsystem sidetermination and CS network side bearer termination.When the MGCF receives an answer indication, itrequests the IM-MGW to both-way through-connect theterminations. Originating and terminating end initiatedcall releases are also covered.IMS to PSTN Call(ISUP interworking, H.248 andBGCF routing)
This call flow describes the call setup from an IMSsubscriber to ISUP PSTN termination. The call is routedvia the BGCF (Border Gateway Control Function) to theMGCF (Media Gateway Control Function). The MGCFuses one context with two terminations in IM-MGW(Media Gateway). The termination RTP1 is usedtowards IMS Core network subsystem entity and thebearer termination TDM1 is used for bearer towardsPSTN CS netwrok element.
The latest EventStudio patch improves compatibilitywith Windows Vista. The scenario project templates andsample documents are now installed in the
IP Multimedia Subsystem (IMS) provides a frameworkand building blocks for building advanced telecomservices. One such service is network wide publicationand subscription of presence information. Users cansubscribe to presence information for their contacts. Ifthe contact accepts their request, the subscriber will beregistered for presence notification. Whenever thefriend publishes presence information, the IMSpresence framework will notify the subscribed users.
IMS presence information communication can put a lotof load on the network. One way to reduce this load isto predefine the list of friends and family. When yousubscribe to the "friends and family" list, a ResourceList Server (RLS) in the IMS subscribes to the individualsubscribers (presentities) on your behalf. Once the RLScompletes the registrations, it collates the individualpresence status into a single NOTIFY message.