Actions

Difference between revisions of "CONN REQUEST"

From Zenitel Wiki

m
 
Line 2: Line 2:
 
{| border="1"
 
{| border="1"
 
|-
 
|-
!style="background:#ffdead;" width="90pt" colspan="2"|CONN_REQUEST
+
! colspan="2" style="background:#ffdead;" width="90pt" |CONN_REQUEST
!style="background:#ffdead;" width="100pt"|0x000A
+
! style="background:#ffdead;" width="100pt" |0x000A
!style="background:#ffdead;" width="30pt"|10
+
! style="background:#ffdead;" width="30pt" |10
!style="background:#ffdead;" |AMC 05.00
+
! style="background:#ffdead;" |AMC 05.00
 
|-
 
|-
|colspan="5"|'''$CONN L101 L102'''
+
| colspan="5" |'''$CONN L101 L102'''
 
|-
 
|-
|colspan="5"|Set up an conversation between users.  Priority setup:  Open call only, no camp­on 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\>  
+
| colspan="5" |Set up an conversation between users.  Priority setup:  Open call only, no camp­on busy.
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\>
+
 
 +
 
 +
- 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>.
 +
 
 +
 
 +
From AMC 07.60:  Supported across AlphaNet - A and B users can be in different nodes.   
 +
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 (either as explicit node number L(2)101, or as a global number L9501 which points to node 2)
 +
 
 +
 
 
Note:  Does not work well with ATLB (telephones), as it bypasses private ringing!
 
Note:  Does not work well with ATLB (telephones), as it bypasses private ringing!
 
|-
 
|-
|align=center|1||[[NET_OBJ_REF]]<br />{[[ECL_USER]]}||colspan="3"|The calling (A) user.  The user must have an associated station.  
+
| align="center" |1||[[NET_OBJ_REF]]<br />{[[ECL_USER]]}|| colspan="3" |The calling (A) user.  The user must have an associated station.
 
|-
 
|-
|align=center|2||[[NET_OBJ_REF]] <br />{[[ECL_USER]]},||colspan="3"|The called (B) user.  The user must have an associated station
+
| align="center" |2||[[NET_OBJ_REF]] <br />{[[ECL_USER]]},|| colspan="3" |The called (B) user.  The user must have an associated station
 
|-
 
|-
|align=center|3||[[UINT1]]<br />(optional from 07.60)||colspan="3"|Call Priority against A station (and B if no parameter 4): <br />1 = Override absent and private. Default behavior.<br />2 = Also override busy.  
+
| align="center" |3||[[UINT1]]<br />(optional from 07.60)|| colspan="3" |Call Priority against A station (and B if no parameter 4): <br />1 = Override absent and private. Default behavior.<br />2 = Also override busy.
 
|-
 
|-
|align=center|4||[[UINT1]]<BR\>(optional)||colspan="2"|Call Priority against B station:<br />
+
| align="center" |4||[[UINT1]]
 +
(optional)
 +
| colspan="2" |Call Priority against B station:<br />
 
1 = Override absent and private. Default behavior.<br />
 
1 = Override absent and private. Default behavior.<br />
 
2 = Also override busy.<br />  
 
2 = Also override busy.<br />  
 
Not specified: same priority as specified for A-station.  
 
Not specified: same priority as specified for A-station.  
|| AMC 07.30  
+
||AMC 07.30
 
|-
 
|-
|align=center|5||[[UINT1]]<br />(optional)||colspan="2"|Require acknowledges:<br />1 = Require acknowledge to setup and disconnection (default if parm 3). ([[CONN_REF_ACK]], [[DISCONNECTED_ACK]]) <br />
+
| align="center" |5||[[UINT1]]<br />(optional)|| colspan="2" |Require acknowledges:<br />1 = Require acknowledge to setup and disconnection (default if parm 3). ([[CONN_REF_ACK]], [[DISCONNECTED_ACK]]) <br />
 
2 = Do not require acknowledges. (default if parm 3 missing)<br />
 
2 = Do not require acknowledges. (default if parm 3 missing)<br />
 
Option added so that the command can be used as Event Handler Action.
 
Option added so that the command can be used as Event Handler Action.
 
||AMC07.30
 
||AMC07.30
 
|-
 
|-
|||Response:||colspan="3"|[[CONN_REFERENCE]], [[STATION_BUSY]], [[STATION_DOWN]], [[RESOURCE BUSY]], [[NO ACCESS]]
+
| ||Response:|| colspan="3" |[[CONN_REFERENCE]], [[STATION_BUSY]], [[STATION_DOWN]], [[RESOURCE BUSY]], [[NO ACCESS]]
 
|}
 
|}
  
 
[[Category: ACDP messages]]
 
[[Category: ACDP messages]]
 
[[AlphaNet_Data_Protocol#Station_Connect_Operations|Back to AlphaNet message list]]
 
[[AlphaNet_Data_Protocol#Station_Connect_Operations|Back to AlphaNet message list]]

Latest revision as of 12:40, 10 December 2019

AI.png
CONN_REQUEST 0x000A 10 AMC 05.00
$CONN L101 L102
Set up an conversation between users. Priority setup: Open call only, no camp­on busy.


- 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>.


From AMC 07.60: Supported across AlphaNet - A and B users can be in different nodes. 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 (either as explicit node number L(2)101, or as a global number L9501 which points to node 2)


Note: Does not work well with ATLB (telephones), as it bypasses private ringing!

1 NET_OBJ_REF
{ECL_USER}
The calling (A) user. The user must have an associated station.
2 NET_OBJ_REF
{ECL_USER},
The called (B) user. The user must have an associated station
3 UINT1
(optional from 07.60)
Call Priority against A station (and B if no parameter 4):
1 = Override absent and private. Default behavior.
2 = Also override busy.
4 UINT1

(optional)

Call Priority against B station:

1 = Override absent and private. Default behavior.
2 = Also override busy.
Not specified: same priority as specified for A-station.

AMC 07.30
5 UINT1
(optional)
Require acknowledges:
1 = Require acknowledge to setup and disconnection (default if parm 3). (CONN_REF_ACK, DISCONNECTED_ACK)

2 = Do not require acknowledges. (default if parm 3 missing)
Option added so that the command can be used as Event Handler Action.

AMC07.30
Response: CONN_REFERENCE, STATION_BUSY, STATION_DOWN, RESOURCE BUSY, NO ACCESS

Back to AlphaNet message list