Administration HiPath 3000/5000 V7 IP systems

3000sb2.fm
For internal use only HiPath 3000 System Overview
Recommendations for CMA and CMS Utilization
Table 2-36 Recommendations for CMA and CMS Utilization
Trunk
connection
Reference
clock
HiPath Cordless
Office
Trunk
connection
Reference
clock
HiPath Cordless
Office
No Yes No Yes
● Networking via Ethernet/IP (10BaseT) lines:
System 1 System(s) n+1
No trunk/ – CMS
analog
trunk
3 CMS/CMA No trunk/ – CMS
(see Table 2- analog
37) trunk
3 CMS/CMA
(see Table 2-
37)
ISDN S0 (not alwaysac-
Via
ISDN S0 trunk con-
CMS
tive)nection (if active)
3 CMS/CMA
(see Table 2-
37)
ISDN S0 (not alwaysac-
Via
ISDN S0 trunk con-
CMS
tive)nection (if active)
3 CMS/CMA
(see Table 2-
37)
ISDN S0 (always
active)
Via
ISDN S0 trunk con-
– CMA
nection
2
ISDN S0 (always
active)
Via
ISDN S0 trunk con-
– CMA
nection
2
ISDN
S2M Via
ISDN S2M trunk con-
– CMA
nection
2
ISDN S2M Via
ISDN S2M trunk con-
– CMA
nection
2
1 CMS is not necessary if the reference clock supplied by the CO is always available via the networking lines (not a transparent
clock).
2 CMA is not necessary if ADPCM conversion is not needed for HiPath Cordless Office (see Table 2-37).
3 CMS is not necessary but is recommended for the following reasons: Although an Ethernet link is an asynchronous connection,
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.
P31003-H3570-Y100-4-7618, 2007-10-31
HiPath 3000/5000 V7, System Description 2-79