Difference between revisions of "Node"
From Zenitel Wiki
| Line 2: | Line 2: | ||
<'''Node'''> is one byte.<br> | <'''Node'''> is one byte.<br> | ||
| − | {| border="1" | + | {| border="1" colpadding="3" |
! style="background:#ffdead;" width="100" |Value (decimal) | ! style="background:#ffdead;" width="100" |Value (decimal) | ||
! style="background:#ffdead;" width="100" |Value (Hex) | ! style="background:#ffdead;" width="100" |Value (Hex) | ||
| Line 20: | Line 20: | ||
<br> | <br> | ||
<br> | <br> | ||
| − | |||
| − | |||
Revision as of 22:20, 19 June 2007
All ACDP data messages are addressed to a device. A device is always related to (owned by) a node. A full device address consists of <node> <device>.
<Node> is one byte.
| Value (decimal) | Value (Hex) | Node Type |
|---|---|---|
| 0 | 0x00 | Node 0 is interpreted by the exchange which receives it as "own node", and it will replace the value 0 with it’s own node number before processing takes place.
Response messages will thus NOT contain any node 0 references |
| 1 - 254 | 0x01 - 0xFE | Exchanges in AlphaNet |
| 255 | 0xFF | Broadcast to all nodes
- All AlphaNet nodes will re-send messages addressed to 0xFF to all other AlphaNet signaling links. - The Network layer manages broadcast messages to avoid excessive signaling traffic and discards messages that has jumped too many times. |