To have a better experience, please upgrade your IE browser.upgrade
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?
Данный сайт есть в английской версии. Желаете ли Вы перейти на английскую версию?
Customer has enabled the call settings so he can manually configure the call options.
He choosed video call but in the call history list, that specific call was stored as Voice call.
Because in the Remote control UI there is no indication of call types in the history, he complained about the fact that every call from history are audio calls only.
TE10 firmware version: V500R003C30SPC200
For a precise analysis, we asked the customer to replicate the issue and asked for network captures:
1. The first INVITE packet is indeed sent with Video SDP negotiation paramters, confirming the customer's scenario:
2. The 200 OK received indicates the remote side negotiated only audio. The conclusion is that the call is audio ONLY and it will be stored as Voice.
3. Customer thought this call was video and when he chose it from history, it started automatically as audio. This is also revealed in the captured packets of the second call:
The SDP contains only audio parameters. This call is Voice.
4. It is obvious that the 200 OK SDP will contain only audio paramters:
As a conclusion, if the call is eventually negotiated as audio, will be recorded as Voice. And if it is negotiated as video, will be recorded as Video.