Specifications

HiPath 3000 System Overview For internal use only
P31003-H3560-X100-1-7618, 09/05
2-110 HiPath 3000/5000 V6.0, System Description
3000sb2.fm
Recommendations for CMA and CMS Utilization
● Networking via Ethernet/IP (10/100 BaseT) lines:
System 1 System(s) n+1
No trunk/
analog
trunk
–CMS
3
CMS/CMA
(see Table 2-
51)
No trunk/
analog
trunk
–CMS
3
CMS/CMA
(see Table 2-
51)
ISDN S
0
(not al-
ways ac-
tive)
Via
ISDN S
0
trunk con-
nection
(if active)
CMS
3
CMS/CMA
(see Table 2-
51)
ISDN S
0
(not al-
ways ac-
tive)
Via
ISDN S
0
trunk con-
nection
(if active)
CMS
3
CMS/CMA
(see Table 2-
51)
ISDN S
0
(always
active)
Via
ISDN S
0
trunk con-
nection
–CMA
2
ISDN S
0
(always
active)
Via
ISDN S
0
trunk con-
nection
–CMA
2
ISDN
S
2M
Via
ISDN S
2M
trunk con-
nection
–CMA
2
ISDN S
2M
Via
ISDN S
2M
trunk con-
nection
–CMA
2
1 CMS is not necessary if the reference clock supplied by the CO is always available via the networking lines (not a trans-
parent clock).
2 CMA is not necessary if ADPCM conversion is not needed for HiPath Cordless Office (see Table 2-51).
3 CMS is not necessary but is recommended for the following reasons: Although an Ethernet link is an asynchronous con-
nection, buffer overflow/underflow can cause transmission errors. To avoid this, the clock difference between the master
and the slave systems should be as small as possible so that the receive and send buffer can be read and addressed at
the same speed on both sides. The more accurate the clock source in the relevant systems, the fewer the faults.
Table 2-50 Recommendations for CMA and CMS Utilization
Trunk
connec-
tion
Reference
clock
HiPath Cordless
Office
Trunk
connec-
tion
Refer-
ence
clock
HiPath Cordless
Office
No Yes No Yes