Multiparty SS » History » Version 1
laforge, 06/03/2018 10:07 PM
| 1 | 1 | laforge | h1. Multiparty SS |
|---|---|---|---|
| 2 | |||
| 3 | The multi-party supplementary service builds on top of the [[Call_Hold_SS|Call Hold (HOLD)]] supplementary service |
||
| 4 | h2. Relevant Specifications |
||
| 5 | |||
| 6 | * "3GPP TS 22.084: Multi Party (MPTY) supplementary service; Stage 1" |
||
| 7 | * "3GPP TS 23.084: Multi Party (MPTY) supplementary service; Stage 2" |
||
| 8 | * "3GPP TS 24.010: Supplementary services specification" |
||
| 9 | * "3GPP TS 24.080: supplementary services specification; Formats |
||
| 10 | and coding" |
||
| 11 | * "3GPP TS 24.084: Multi Party (MPTY) supplementary service; Stage 3":http://www.etsi.org/deliver/etsi_ts/124000_124099/124084/14.00.00_60/ts_124084v140000p.pdf |
||
| 12 | |||
| 13 | h2. Notes |
||
| 14 | |||
| 15 | * the previously held party will get notification by means of a single SS Facility with two components: |
||
| 16 | ** Invoke/NotifySS/CallRetrieved |
||
| 17 | ** Invoke/NotifySS/MPTYindicator |
||
| 18 | * the previously active party will receive |
||
| 19 | ** Invoke/NotifySS/MPTYindicator |
||
| 20 | |||
| 21 | h3. Putting MPTY call on hold |
||
| 22 | |||
| 23 | this is typically done to do another call? |
||
| 24 | |||
| 25 | * Facility/Invoke/HoldMPTY |
||
| 26 | |||
| 27 | h3. Splitting MPTY call to have a private conversation with one participant |
||
| 28 | |||
| 29 | * Facility/Invoke/SplitMPTY |
||
| 30 | |||
| 31 | h3. Call termination |
||
| 32 | |||
| 33 | * simply use normal call clearing using the TI of the specific call |
||
| 34 | |||
| 35 | h3. Retrieving a MPTY call |
||
| 36 | |||
| 37 | * Facility/Invoke/RetrieveMPTY |
||
| 38 | ** no call retrieved notification is sent to remote parties |
