Actions

Difference between revisions of "Network Object Reference"

From Zenitel Wiki

(New page: 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 som...)
 
Line 2: Line 2:
 
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.  
 
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.     
 
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!
 
NOTE:  AlphaCom 08.00 have a fixed size internally of 6 bytes for NET_OBJ_REF fields!
 
<header> <contents….>
 
<header> <contents….>

Revision as of 14:51, 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.