Difference between revisions of "REQ TRANSF CALL"
From Zenitel Wiki
| Line 4: | Line 4: | ||
!style="background:#ffdead;" width="100pt"|0x0088 | !style="background:#ffdead;" width="100pt"|0x0088 | ||
!style="background:#ffdead;" width="30pt"|136 | !style="background:#ffdead;" width="30pt"|136 | ||
| − | !style="background:#ffdead; | + | !style="background:#ffdead;" |AMC 08.20 |
|- | |- | ||
|colspan="2"|$TRFC L101 L105||colspan="3"|''Put Peer of 101 in conversation with 106'' | |colspan="2"|$TRFC L101 L105||colspan="3"|''Put Peer of 101 in conversation with 106'' | ||
Revision as of 15:38, 25 October 2007
| REQ_TRANSF_CALL | 0x0088 | 136 | AMC 08.20 | |
|---|---|---|---|---|
| $TRFC L101 L105 | Put Peer of 101 in conversation with 106 | |||
| Transfer call in an Inquiry Call situation. This message is primarily for internal use. But it can also be used to transfer ordinary calls, se example above. | ||||
| 1 | NET_OBJ_REF | Intermediate destination, used for routing of request | ||
| NET_OBJ_REF<br\>(optional) | A-station in transferred call (source station) | |||
| UINT1<br\>(optional) | Flag (optional): 0 if request from external source (default). 1 if forwarded request, 2 if Sender was Inquiry station | |||
| UINT1<br\>(optional) | Node of original sender, to receive CMD_RESP | |||
| UINT1<br\>(optional) | Device of original sender, to receive CMD_RESP | |||
| Response: | COMMAND_RESPONSE | |||