Difference between revisions of "Network Object Reference"
From Zenitel Wiki
| Line 7: | Line 7: | ||
'''<header> <contents….>''' | '''<header> <contents….>''' | ||
| − | + | ||
| + | Where | ||
* '''<header>''' UINT1 defines both the length and the format: | * '''<header>''' UINT1 defines both the length and the format: | ||
** '''<length>''' 4 bits. The length of the representation not including the first byte itself. | ** '''<length>''' 4 bits. The length of the representation not including the first byte itself. | ||
** '''<format>''' 4 bits. The format of the representation. See the table below. | ** '''<format>''' 4 bits. The format of the representation. See the table below. | ||
* '''<contents>''' See the table below. | * '''<contents>''' See the table below. | ||
Revision as of 14:56, 21 June 2007
All exchange resources can be referenced either by directory numbers, or “physical numbers”. This is a challenge for the data protocol, as directory numbers can vary in size, and some resources have physical addresses with multiple parts. The NET_OBJ_REF is a “variant record” which has a header with byte count plus a type field. The rest of the information is then according to the type field and length. The total length can vary from 1 to 16 bytes.
NOTE: AlphaCom 08.00 have a fixed size internally of 6 bytes for NET_OBJ_REF fields!
<header> <contents….>
Where
* <header> UINT1 defines both the length and the format:
- <length> 4 bits. The length of the representation not including the first byte itself.
- <format> 4 bits. The format of the representation. See the table below.
- <contents> See the table below.