TB30s SIP Administrator Guide v1.3 Page 175 of 259
Ad-Hoc Conf (RFC 4579)
The TB30 is now a "conference-aware" user agent which supports SIP
conferencing call control conventions defined in the RFC-4579 (Call Control -
Conferencing for User Agents) as a conference participant.
TB30 as a conference-aware UA, is able to process SIP redirections such as
described in Section 8.1.3.4 of RFC 3261. Can recognize the 'isfocus' feature
parameter, can support REFER and SIP events. But as many of the servers
which already support this feature as “focus UA” and “Conference factory”
(like Netcentrex/Comverse, Broadsoft or Sylantro servers) don‟t support so
far the subscriptions to conference package (RFC 4575 "Event Package for
Conference State"), this subscribe mechanism is not implemented in the
TB30.
MMI description on initiator side:
1. A and B are in a call.
2. A press “Conf” soft key (-> B is put on hold), then enters C phone’s number.
3. C replies, A and C are in a 2nd call.
4. A press “Conf” again, to switch in conference mode (-> C is put on hold).
5. A creates a conference by sending an INVITE to the Conference_Factory_URI (as described in the
section “5.4. INVITE: Creating a Conference Using Ad-Hoc SIP Methods” of the rfc-4579).
Then it will :
6. Retrieve the "conference ID" either in the 200 OK or in the 302 Moved response (in case the
phone receives a 302 Moved response, it will send another INVITE to the new URI in order to
really initiate the conference).
7. send REFER to B to move to conference ID (as described in section 5.6 of the rfc-4579)
8. send REFER to C to move to conference ID (as described in section 5.6 of the rfc-4579)
The expected behavior here is the Server takes care of capturing the Refers,
then re-INVITE participants to the new call, and deletes old dialogs with
initiator.
TB30 as Initiator is ready to receive early Byes to its Refers, with or without
received Notify (200)·
Here you can find an example Call-Flow of Centralized Conference:
To Next Page
Loading...
Need help?
General