Show last authors
1 = Current state =
3 The Flexisip group chat feature can be deployed into an existing SIP network running with third party SIP servers provided that the conditions listed below are met:
5 1. //The SIP network must comprise one or more SIP proxies connected directly with SIP clients. Typical SIP proxy software are: kamailio, opensips, ser.//
6 1. //The third party SIP proxy must perform authentication, push notification (when applicable) and routing of SIP messages.//
7 1. //The third party SIP proxy must forward the accepted REGISTER requests from clients to the Flexisip machine, even if it directly responds to clients. In practice, it means that it should duplicate REGISTER received from clients and expedite them to the Flexisip server. It can ignore the 200 OK response made by the Flexisip server.//
8 1. //The third party SIP proxy must have a routing rule so that all requests targeted to "sip:conference-factory@sip-domain" or matching the pattern "sip:chatroom-~*~**@sip-domain" are forwarded to the Flexisip server.//
9 1. //The third party SIP proxy must allow all requests coming from the Flexisip machine (without authentication challenge).//
10 1. //The machine on which Flexisip is deployed must run flexisip conference and proxy services, with REDIS backend configured.//
12 = Future evolutions =
14 In a second step, we will make the requirements listed above evolve, in order to have a more standard way of interoperating with third party equipments.
16 Requirement 3 will be replaced by:
18 //The third party SIP proxy must support the event package for registrations (RFC3680 [[https:~~/~~/>>url:]]// //) in order to respond to SIP SUBSCRIBE coming from the Flexisip server. This is necessary for the Flexisip server get a realtime information of current registrations of SIP clients//.
20 Requirement 6 will be replaced by:
22 //The machine on which Flexisip is deployed must run flexisip conference service only. The REDIS backend can remain disabled.//