You may also like
This thread is direct forward from Microsoft MSDN website: http://technet.microsoft.com/zh-cn/aa965245 Easlier in this month, I was researching hardware video encoding/decoding supports for […]
Encountered a capability negotiation issue when conferencing with a HUAWEI terminal. It happened in a dual stream(H.239) capability negotiation. Environments: 1. According […]
People love Google+ Hangouts for meetings. People also love big LCD screens in conference rooms for meetings. What if they both moved to […]
As you may know, to be a robust meeting entity, we must take good care of compatibility requirements for different facilities from different manufacturers. In H.323 protocol, we can use fields like Vendor ID, Product ID, Version ID in the signaling commands. But how to do this when you are using SIP protocol? Definitions in RFC 3261 20.35 Server The Server header field contains information about the software used by the UAS to handle the request. Revealing the specific software version of the server might allow the server to become more vulnerable to attacks against software that is known to contain security holes. Implementers SHOULD make the Server header field a configurable option. Example: Server: HomeServer v2 20.41 User-Agent The User-Agent header field contains information about the UAC originating the request. The semantics of this header field are defined in [H14.43]. Revealing the specific software version of the user agent might allow the user agent to become more vulnerable to attacks against software that is known to contain security holes. Implementers SHOULD make the User-Agent header field a configurable option. […]