In this scenario the two end users are User A and User B.
Call conference call flow in sip. And participant are of different kinds which are Conference aware participants and Conference unaware participants. The call between Lori and Mike goes on hold. The call between Lori and Kevin goes on hold.
3 The conference call is setup and the RTP data begins flowing between the conference initiating UE and the MRFP. The IETF Session Initiation Protocol Call Control Transfer describes methods by which SIP UAs can provide call transfer services using such SIP extensions as REFER RFC 3515 Replaces RFC 3891 Referred-By RFC 3892and sipfrag RFC 3420. The major design goal is that the same SIP conferencing primitives would be used by user agents having different conferencing capabilities and implementing.
The new users establish a call to the conference URI passed in the refer message. The call flow is as. User B is located at a Cisco SIP IP phone.
SIP Call Flow for Inbound Call The SIP call flow diagram for inbound calls is shown in Figure 3. Ad Choose A Fully Licensed And Compliant Provider To Enjoy Stable Long-Term Service. The following image shows the basic call flow of a SIP session.
Conference Call -flow part 1 When the CONF service is invoked conference resources are allocated to the served user UE-1. The call flow will be A calls C then B calls A followed by A confere. Logically this is the entire call flow.
Ad Choose A Fully Licensed And Compliant Provider To Enjoy Stable Long-Term Service. Conference Caller leaving the Conference BYE Request URI. An INVITE request that is sent to a proxy server is responsible for initiating a session.