Custom Query (2195 matches)

The issues occurs when:

• Proxying a message that contains a WWW-Authenticate header.
• The WWW-Authenticate header contains a digest challenge.
• The challenge includes parameters that fall into PJSIP’s definition of "other_params", and these are quoted.

In this case, when the header is proxied, the quoted "other params" will be unquoted.

This is happening because parse_digest_challenge unquotes all the parameters it finds before storing them on the pjsip_digest_challenge. However print_digest_challenge does not re-quote them (if the "other_params" are required to be quoted, they must be stored as quoted values in the pjsip_digest_challenge before calling print_digest_challenge).

The fix is for parse_digest_challenge to not unquote "other_params". This seems better than the alternative of having print_digest_challenge add the quotes, as the latter approach does not allow the application to use "other_params" but avoid having them quoted.

Thanks to Alex Hockey for the patch.

Application may want to apply specific socket option to the transport by calling setsockopt.

For TCP and UDP, the options are defined using sockopt_params in pjsua_transport_config.

For TLS, the options are defined using sockopt_params in pjsip_tls_setting.

Support for libyuv library which provides YUV scaling and conversion functionality (​https://chromium.googlesource.com/libyuv/libyuv/).

Requirement

• Libyuv library. For building the library, we recommend using the steps described ​here, except for Android target as explained below.

This implementation will provide video scaling and conversion functionality.

Below are the steps to use the codec:

For GNU targets

1. Build Libyuv library. Make sure to execute the Release build step (ninja -j7 -C out/Release). The library will be built on ([libyuv_dir]/out/Release).
2. Run PJSIP's configure and specify the Libyuv folder using --with-libyuv option. E.g:

   ./configure --with-libyuv=/home/user/src/libyuv
   

For iOS targets

1. Build Libyuv library. Make sure to execute the Release build step (ninja -j7 -C out_ios/Release-iphoneos libyuv_unittest). The library will be built on ([libyuv_dir]/out_ios/Release-iphoneos).
2. Run PJSIP's configure-iphone and specify the Libyuv folder using --with-libyuv option. E.g:

   ./configure-iphone --with-libyuv=/home/user/src/libyuv
   

3. Add libyuv.a to application project in XCode. For armv7 architecture, also add libyuv_neon.a to the application project.

Notes for iOS targets:

• To build for armv7s, just follow the instructions for arm64, which will build libyuv for three architectures: armv7, armv7s, and arm64. armv7s it is still not supported because of the limitation from chromium build tools (documented in libyuv's issue ​here).

For Android targets

1. Get libyuv from ​here (tried to build using the official source, but failed).
2. From the libyuv-android directory, run ndk-build. The library will be built on ([libyuv_dir]/libs/armeabi).
3. Create dir out/Release under [libyuv_dir]/jni and copy the libyuv.so there. E.g:

   cd [libyuv_dir]
   mkdir -p jni/out/Release
   cp libs/armeabi/libyuv.so jni/out/Release
   

4. Run PJSIP's configure and specify the Libyuv folder using --with-libyuv option. E.g:

   ./configure --with-libyuv=[libyuv_dir]/jni
   

For Visual Studio

1. Build the Libyuv library.
2. Add Libyuv include and library location paths to Visual Studio search path settings.
3. Add this to your config_site.h:

   #define PJMEDIA_HAS_LIBYUV		1