Questo sito utilizza cookie di profilazione (propri e di terze parti) per ottimizzare la tua esperienza online e per inviarti pubblicità in linea con le tue preferenze. Continuando a utilizzare questo sito senza modificare le tue preferenze acconsenti all’uso dei cookie. Se vuoi saperne di più o negare il consenso a tutti o ad alcuni cookie clicca qui>
The website that you are visiting also provides Arabian language. Do you wish to switch language version?
يوفر موقع الويب الذي تزوره المحتوى باللغة العربية أيضًا. هل ترغب في تبديل إصدار اللغة؟
The website that you are visiting also provides Russia language Do you wish to switch language version?
Данный сайт есть в английской версии. Желаете ли Вы перейти на английскую версию?
no alarm, but nearly 10% pacakge loss displayed in Nlog statistic.
1. We first tried to change the bandwidth of conference and image resolution ratio but it didn't work.
2. We doubt a bad network may be involved. It works a bit after network optimization operating by the customer, but package loss problem still exist.
3. Capture media stream package on MCU, SC, TP and analyze it.
MCU ip address: 192.168.211.112
TP3106-70 ip address: 192.168.211.115
Standalone SC ip address: 192.168.211.111
MCU package capture:
TP package capture:
4. We found out that TP system and MCU both send theirmedia stream to SC when in a conference and all packages are transmitting by SC. According to the customer's current networking mode, media stream should not be transmitted by SC and the configuration of SC may have a problem.
Because of the configuration policy that there's no need to open media route function which is open in default, all media stream was handled by SC where media stream was processed repeatedly and thus caused package loss.
Modify the configuration by closing media route function and capture the package.
It turned out except for few registration signaling packages, no more pacakge sent to SC and no package loss occured when holding a conference by SMC2.0.