thanks, media resource 是不是就是dspfarm 怎么reload? 很多概念对我来讲是新的,又处于全面接触整个网络的阶段, 来不及看书,消化。 公司网络就没有连线图,很乱。要从头开始画图。 里面放了什么设备,怎么连的,人家心里没数,不清楚, 属于小车不倒只管推那种。 just something looks like a switch. :) thanks, media resource 是不是就是dspfarm 怎么reload? 很多概念对我来讲是新的,又处于全面接触整个网络的阶段, 来不及看书,消化。 公司网络就没有连线图,很乱。要从头开始画图。 里面放了什么设备,怎么连的,人家心里没数,不清楚, just something looks like a switch. :) 属于小车不倒只管推那种。
【在 he 的大作中提到】 : CME#term mon : CME#debug ephone detail : 重现问题. : CME#u all : CME#term no mon : 耐心找一下缘故。找不到也就算了,CME的电话会议功能是个摆设,CME/CUE产品性价比 : 非常差,用户很少。 : CCNA v到CCVP,我觉得没有比Jeremy Cirora录像更好的自学资料了,网上搜搜可以下 : 载,理论+实际他齐活了。
f*8
36 楼
我也基本这么想。 因为NTP是根据Round-trip delay计算时间,不大可能十分精确吧。 所以才允许systematic bias (不过这我只是猜测,不懂。 题外话,按说所谓的卫星时钟同步,gps也够准的,当然gps也有漂移。 应该都是同步问题) WIKI:NTP Clock synchronization algorithm To synchronize its clock with a remote server, the NTP client must compute the round-trip delay time and the offset. The round-trip delay is computed as δ = (t3 t0) (t2 t1), where t0 is the time of the request packet transmission, t1 is the time of the request packet reception, t2 is the time of the response packet transmission and t3 is the time of the response packet reception. t3 t0 is the time elapsed on the client side between the emission of the request packet and the reception of the response packet, while t2 t1 is the time the server waited before sending the answer. The offset is given by \theta = {(t_1 - t_0) + (t_2 - t_ 3 ) \over 2} The NTP synchronization is correct when both the incoming and outgoing routes between the client and the server have symmetrical nominal delay. If the routes do not have a common nominal delay, the synchronization has a systematic bias of half the difference between the forward and backward travel times.[8]
"同事说signal一断通话马上结束了" impossible, check RFC 3261 if what I remember is correct; Signaling is signaling, nothing with data. Internet/Ethernet is not synced network like SONET/ATM so NTP does not matter as long as PHY could do clock recovery.