Difference between revisions of "CONN REQUEST"
From Zenitel Wiki
| Line 8: | Line 8: | ||
|colspan="5"|'''$CONN L101 L102''' | |colspan="5"|'''$CONN L101 L102''' | ||
|- | |- | ||
| − | |colspan="5"| | + | |colspan="5"|Set up an conversation between users. Priority setup: Open call only, no campon busy. <BR\><BR\> - The <reference> field in the message header will be stored in the exchange for the duration of the conversation, and will be used in related disconnect messages. This means that the external application can monitor the conversation using an unique <internal reference>, much like the exchange uses the <connection reference>.<BR\><BR\>From AMC 07.60: Supported across AlphaNet - A and B users can be in different nodes.<BR\> |
| − | + | The message should preferably be addressed (net layer) to the exchange where the A user is located, but if it’s sent to the local exchange it will be routed based on the A user info given in parameter 1<BR\>(either as explicit node number L(2)101, or as a global number L9501 which points to node 2)<BR\><BR\> | |
| − | + | Note: Does not work well with ATLB (telephones), as it bypasses private ringing! | |
| − | |||
| − | |||
| − | |||
|- | |- | ||
|1||[[NET_OBJ_REF]]<br\>{[[ECL_STATION]], <BR\> [[ECL_USER]]}||colspan="3"|A - user or station. | |1||[[NET_OBJ_REF]]<br\>{[[ECL_STATION]], <BR\> [[ECL_USER]]}||colspan="3"|A - user or station. | ||
Revision as of 13:16, 11 June 2007
| CONN_REQUEST | 0x000A | 10 | AMC 05.00 | |
|---|---|---|---|---|
| $CONN L101 L102 | ||||
| Set up an conversation between users. Priority setup: Open call only, no campon busy. <BR\><BR\> - The <reference> field in the message header will be stored in the exchange for the duration of the conversation, and will be used in related disconnect messages. This means that the external application can monitor the conversation using an unique <internal reference>, much like the exchange uses the <connection reference>.<BR\><BR\>From AMC 07.60: Supported across AlphaNet - A and B users can be in different nodes.<BR\>
The message should preferably be addressed (net layer) to the exchange where the A user is located, but if it’s sent to the local exchange it will be routed based on the A user info given in parameter 1<BR\>(either as explicit node number L(2)101, or as a global number L9501 which points to node 2)<BR\><BR\> Note: Does not work well with ATLB (telephones), as it bypasses private ringing! | ||||
| 1 | NET_OBJ_REF<br\>{ECL_STATION, <BR\> ECL_USER} | A - user or station. | ||
| 2 | NET_OBJ_REF <br\>{ECL_STATION, <BR\> ECL_USER} | B - user or station | ||
| 3 | UINT2<br\>(optional) | Call mode options (default zero)<br\>Call mode options can be the sum of the following:<BR\>
1: Return CONN_REFERENCE, STATION_DOWN or STATION_BUSY. Send DISCONNECTED at disconnect (CSF_RETURN_ACK)<BR\> 2: Require CONN_REF_ACK and DISCONNECTED_ACK (CSF_3WAY_ACK)<BR\> 4: Reserved<BR\> 8: Reserved<BR\> 16: Do not disconnect A station if busy (CSF_NOT_FORCE_A)<BR\> 32: Do not follow call forwarding (CSF_NO_FORWARD)<BR\> 64: Transfer call, answer group call (CSF_TRANSFER_CALL) Forces both A and B stations.<BR\> 128: Force call in Open Duplex mode (CSF_OPEN_DUPLEX) (AMC 09.03) | ||
| 4 | UINT1<BR\>(optional) | A-call priority 1 - 4. Zero or omitted means that the NVRAM priority of A station is used | ||
| 5 | UINT1<br\>(optional) | B-call priority 1 - 4. Zero or omitted means that the NVRAM priority of A station is used | ||
| 6 | NET_OBJ_REF<br\>{ECL_STATION}<br\>(optional) | B Station if User B is not at own station. | ||
| Response | CONN_REFERENCE, STATION_DOWN or STATION_BUSY, or none | |||