Custom Query (2195 matches)

When presence publication is enabled in pjsua account, pjsua-api sends PUBLISH overlapping with REGISTER, and when the REGISTER is challenged with 401/407, the PUBLISH request will be rejected with 404/Not Found.

Thanks Edward Tian for reporting the problem.

Currently when buddy's presence subscription fails in pjsua-api (i.e. SUBSCRIBE request fails to establish subscription), PJSUA-API will not try to send another SUBSCRIBE ever, so if buddy is online then we won't get notified. Application is currently responsible for managing timer to send another subscribe periodically to probe to buddy's presence.

Ideally PJSUA-API should maintain this timer internally on behalf of application to make life easier.

Note that this only applies to when SUBSCRIBE fails - if SUBSCRIBE succeeds, then buddy's presence will be monitored normally.

When the configure script detects the availability of OpenSSL and ALSA libraries, TLS and ALSA support will be included with the library.

But unfortunately this causes undefined symbol error when running Python application, for example:

python pjsua_app.py
 Traceback (most recent call last):
   File "pjsua_app.py", line 8, in ?
     import py_pjsua
 ImportError: /usr/lib/python2.4/site-packages/py_pjsua.so: undefined symbol: 
 snd_pcm_close

Thanks Matthias Laur for the report.