Wildfire connection to Asterisk

1. Focus XCON Focus DCON We suppose Xcon is working MeetMe Asterisk When the SPACE component starts, 3 main events happen: Wildfire connection to Asterisk • Connection to the Asterisk • Manager interface Gateway Update • Connection to the Gateway • interface Sip Client Manager 3) Request for initialization information XMPP Client • Now the focus cloud involves also the • Wildfire server and SPACE • component which has in charge: • Dicovery of other foci • Managing of DCON information and BFCP packets. QueryUpdate Updating… Memory Dispatcher Presence Manager S2S manager SPACE

2. DCON Focus A DCON Focus B Asterisk MeetMe Asterisk MeetMe Discovery of active Foci Gateway Gateway Manager Manager User A_1 User B_1 User B_1 Memory Dispatcher Dispatcher Memory Presence Manager S2S manager S2S manager Presence Manager SPACE SPACE We suppose that the roster of user A_1 (belonging to focus A) contains user B_1 (belonging to focus B) and viceversa . Once an user (we suppose B_1) joins the focus, the Presence Manager enforces the S2S Manger to try to contact all the foci in the B_1’s roster. Two cases are possible…

3. DCON Focus A DCON Focus B Asterisk MeetMe Asterisk MeetMe Discovery of active Foci Case 1: A_1 not yet online Gateway Gateway Manager Manager B prefix A prefix User A_1 User A_1 User B_1 User B_1 Memory Dispatcher Updating… Dispatcher Memory Updating… A prefix B prefix s2s established XMPP update Presence Manager S2S manager S2S manager Presence Manager SPACE XMPP update SPACE If A_1 (the user in B_1 roster) is not yet online the focus A will appear “not active” until A_1 will join it. Once A_1 joins the focus, in fact, the Presence Manager enforces the S2S Manager to try to contact B. In such a way the s2s connection is complete and the foci can exchange their conference information by means of an XMPP encapsulated “update message” and add the prefix of the remote focus to the local Asterisk Dialplan.

4. DCON Focus A DCON Focus B Asterisk MeetMe Asterisk MeetMe Discovery of active Foci Case 2: A_1 is already online Gateway Gateway Manager Manager B prefix A prefix User A_1 User A_1 User B_1 User B_1 Memory Dispatcher Updating… Dispatcher Memory Updating… A prefix B prefix s2s established XMPP update Presence Manager S2S manager S2S manager Presence Manager SPACE XMPP update SPACE If A_1 (the user in B_1 roster) is already online the focus A will appear “active” So the s2s connection is complete and the foci can exchange their conference information by means of an XMPP encapsulated “update message” and add the prefix of the remote focus to the Asterisk Dialplan.

5. DCON Focus A DCON Focus B Asterisk MeetMe Activate Asterisk MeetMe 867100 Spreading of Conference Events Gateway Gateway Manager Manager B = 857 A = 867 User A_1 User A_1 User B_1 User B_1 Memory Dispatcher Updating… Dispatcher Memory Updating… s2s established 867100 867100 Presence Manager S2S manager S2S manager Presence Manager XMPP Activate SPACE SPACE When the s2s connection has been established and the prefixes have been exchanged an user can join a conference active on the remote focus. We soppose A_1 joins the local conference 867100: an “ActivateEvent” will be sent to SPACE by means of the Manager Interface. SPACE will then spread it to all the active foci which will update their information.

6. DCON Focus A DCON Focus B Asterisk MeetMe Asterisk MeetMe 867100 QueryConferences Message Gateway Gateway Manager Manager B = 857 A = 867 User A_1 User A_1 User B_1 User B_1 QueryConf Memory Dispatcher 867100 Dispatcher Memory Retrieving… s2s established 867100 867100 Presence Manager S2S manager S2S manager Presence Manager SPACE SPACE If an user want to know the conferences in the distributed system, it can send a “QueryConferences” message. The Gateway checks if DCON is connected and in this case ask it for the conference information about all the active foci. The user is so aware of the conference active on the remote focus A

7. DCON Focus A DCON Focus B Asterisk MeetMe Asterisk MeetMe 867100 867100 JOIN to remote conference: AddCascaded and AddUser Messages Gateway Gateway AddCascaded AddUser Manager Manager B = 857 A = 867 867100 B_1’ in 867100 channel User A_1 User A_1 B_1 in 867100 channel User B_1 User B_1 Join 867100 Memory Dispatcher Dispatcher Memory s2s established 867100 867100 Presence Manager S2S manager S2S manager Presence Manager SPACE SPACE If now the user B_1 wants to join the remote conference 867100, he simply calls this conference number. The Gateway checks the prefix and understands this is a remote conference so: 1) Triggers the creation of the Local Stub Conference 867100 2) Sends the AddCascaded and AddUser messages to the remote focus by means of the dispatcher

8. DCON Focus A DCON Focus B Asterisk MeetMe Asterisk MeetMe RTP channel 867100 867100 867100 JOIN to remote conference: AddCascaded and AddUser Messages Gateway Gateway CascadedAdded UserAdded Manager Manager B = 857 A = 867 867100 B_1’ in 867100 channel User A_1 User A_1 B_1 in 867100 channel User B_1 User B_1 Memory Dispatcher Dispatcher Memory s2s established 867100 867100 Presence Manager S2S manager S2S manager Presence Manager SPACE SPACE The main focus adds the Cascaded conference, sends a CascadedAdded message and opens an RTP channel with the secondary focus so the Stub Conference is activated. Then it adds the remote user B_1 to the conference and sends the new assigned “userID” encapsuled into a UserAdded Message by means of the established B_1’ channel.