mirror of https://github.com/sipwise/sems.git
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
84 lines
2.9 KiB
84 lines
2.9 KiB
|
|
*******************************
|
|
* Conferencing plug-in README *
|
|
*******************************
|
|
|
|
|
|
Description:
|
|
------------
|
|
|
|
The 'conference' plug-in works very easy:
|
|
every call having the same request URI will
|
|
be in the same conference room.
|
|
|
|
Dialout feature:
|
|
----------------
|
|
|
|
Dialout is supported through AVT tones. Somebody
|
|
who has been 'dialed out' cannot use this functionnality
|
|
due to billing issues. If you still want that, you can
|
|
turn it out in the code (search for 'if(dialedout)').
|
|
|
|
keys:
|
|
- '#*' to trigger dialout. Then type in the number and finish with '*'.
|
|
- you be first connected to the callee only
|
|
- press '*' to connect the callee to the conference.
|
|
- press '#' to drop the call.
|
|
|
|
Dialout is only enabled if dialout_suffix is defined (see below).
|
|
Configuration:
|
|
--------------
|
|
|
|
default_announce: announcement to be played to the
|
|
first participant as he enters the
|
|
conference room.
|
|
|
|
join_sound: sound to be played to all the participants
|
|
when a new one joins the conference. (optional)
|
|
|
|
drop_sound: sound to be played to all the participants
|
|
when a participant leaves the conference. (optional)
|
|
|
|
dialout_suffix: suffix to be append to the numbered entered by
|
|
the user. Example: @iptel.org
|
|
|
|
playout_type: adaptive_playout, adaptive_jb, or simple:
|
|
select playout mechanism.
|
|
adaptive_playout : Adaptive Playout buffer
|
|
(default, recommended)
|
|
adaptive_jb : Adaptive Jitter buffer
|
|
simple : simple (fifo) playout buffer
|
|
See sems core documentation for an explanation of the
|
|
methods.
|
|
|
|
Adding participants with "Transfer" REFER:
|
|
------------------------------------------
|
|
The "Transfer REFER" is a proprietary REFER call flow which transfers a
|
|
SIP dialog and session to another user agent ('taker'). If the transfer
|
|
REFER is accepted, the one transfering the call just "forgets" the dialog
|
|
and associated session, while the taker can send a re-Invite, thus overtaking
|
|
the dialog and session. For this to work, both transferer and taker must
|
|
be behind the same record routing proxy, and the callers user agent must
|
|
properly support re-Invite (updating of contact, and session, as specified
|
|
in RFC3261).
|
|
|
|
The transfer request sent out has two headers, which are needed by the
|
|
entity taking the call:
|
|
P-Transfer-RR : route set of the call
|
|
P-Transfer-NH : next hop
|
|
|
|
These headers must be configured in ser.cfg to be passed to the conference
|
|
application, for example using the following tw_append:
|
|
|
|
# appends for REFER
|
|
modparam( "tm", "tw_append",
|
|
"refer_append:hdr[P-Transfer-NH];hdr[P-Transfer-RR]")
|
|
|
|
...
|
|
|
|
t_write_unix("/tmp/msp_conference_sock","conference/refer_append");
|
|
|
|
Note that while this request has the method 'REFER', it does not follow rfc3515,
|
|
for example the Refer-To header is not used.
|
|
|