Actions

Difference between revisions of "CDC STATE"

From Zenitel Wiki

Line 16: Line 16:
 
|-
 
|-
 
|align=center|3||[[UINT1]]||colspan="3"|State of billing sequence.<br>
 
|align=center|3||[[UINT1]]||colspan="3"|State of billing sequence.<br>
1 START, user has initiated a feature requiring CDC (5 = feature dirno)<br>
+
1. START, user has initiated a feature requiring CDC (5 = feature dirno)<br>
2 DIGIT, user has dial a digit (5 = digit netref) <br>
+
2. DIGIT, user has dial a digit (5 = digit netref) <br>
3 ESTABLISHED, (SIP)connection established (200 OK received)<br>
+
3. ESTABLISHED, (SIP)connection established (200 OK received)<br>
4 ACTIVE, call is still active, will come every 10 second during connection<br>
+
4. ACTIVE, call is still active, will come every 10 second during connection<br>
5 DISCONNECT, CDC sequence ended, ABSD to release call.<br>
+
5. DISCONNECT, CDC sequence ended, ABSD to release call.<br>
6 SPEECH_START, [[ABSD_Billing#AudioCodes_X-detect|Speech detected by AudioCodes]]<br>
+
6. SPEECH_START, [[ABSD_Billing#AudioCodes_X-detect|Speech detected by AudioCodes]]<br>
7 SPEECH_END,  Speech detect end by AudioCodes<br>
+
7. SPEECH_END,  Speech detect end by AudioCodes<br>
8 CHANGE_A_IDENTITY, Change A extension, continue Billing sequence, AMCD must send ACTIVE_SYNC from new A extension within 3 seconds<br>
+
8. CHANGE_A_IDENTITY, Change A extension, continue Billing sequence, AMCD must send ACTIVE_SYNC from new A extension within 3 seconds<br>
9 ACTIVE_SYNC, first message/event from new A extension after CHANGE_A_IDENTITY, synchronize AMCD and ABSD with new message header
+
9. ACTIVE_SYNC, first message/event from new A extension after CHANGE_A_IDENTITY, synchronize AMCD and ABSD with new message header
 +
10.TRUNK_BUSY, Reply when requested trunk is unavailable.
 
|-
 
|-
 
|align=center|4||[[NET_OBJ_REF]]||colspan="3"|Netref related to state type, (Feature, B-station or digit)
 
|align=center|4||[[NET_OBJ_REF]]||colspan="3"|Netref related to state type, (Feature, B-station or digit)

Revision as of 09:04, 7 May 2010

Related to Billing

CDC_STATE 0x009E 158 AMC 10.40
Message used for billing control, from AMCD to ABSD

CDC = Call Detail Control. Response is CDC_CMD.

1 UINT2 Connection Reference for this "dialing" sequence (actually ST_IND of A-station)
2 NET_OBJ_REF A-station (billed station), in NRF_LOCAL_DIRNO format.
3 UINT1 State of billing sequence.

1. START, user has initiated a feature requiring CDC (5 = feature dirno)
2. DIGIT, user has dial a digit (5 = digit netref)
3. ESTABLISHED, (SIP)connection established (200 OK received)
4. ACTIVE, call is still active, will come every 10 second during connection
5. DISCONNECT, CDC sequence ended, ABSD to release call.
6. SPEECH_START, Speech detected by AudioCodes
7. SPEECH_END, Speech detect end by AudioCodes
8. CHANGE_A_IDENTITY, Change A extension, continue Billing sequence, AMCD must send ACTIVE_SYNC from new A extension within 3 seconds
9. ACTIVE_SYNC, first message/event from new A extension after CHANGE_A_IDENTITY, synchronize AMCD and ABSD with new message header 10.TRUNK_BUSY, Reply when requested trunk is unavailable.

4 NET_OBJ_REF Netref related to state type, (Feature, B-station or digit)



Call Transfer and CDC_STATE Event

For the a Billed call transferred, AMCD will send :

  • CDC_STATE(old_conn_ref; new_a_netref; CHANGE_A_IDENTITY) from the old node.
  • CDC_STATE(new_conn_ref; new_a_netref; ACTIVE_SYNC) from the new node.

If the second message is not received with seconds, the transfer was unsuccessful.

Also see CALL_SETUP, param#3.

If the call is transferred to a station in an other node, the call will still be related to the original ABSD node. Even if the new node is configured to use an other ABSD node, or is not configured for billing at all.


Back to AlphaNet message list