Changes between Version 29 and Version 30 of FAQ


Ignore:
Timestamp:
Feb 4, 2008 7:19:10 AM (11 years ago)
Author:
bennylp
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • FAQ

    v29 v30  
    960960This problem is caused by lack of network connectivity, just like [#wm-resolve PJ_ERESOLVE error on Windows Mobile] above. PJSIP (and SIP programs in general) does not work with HTTP proxy, so even if networking seems to be working with Internet Explorer with proxy configured, SIP messages won't be able to reach the destination unless networking is properly configured. Please see [#wm-resolve PJ_ERESOLVE error on Windows Mobile] topic above on how to configure networking on Windows Mobile/PocketPC emulator. 
    961961 
     962=== Bad audio quality on Windows Mobile === #wm-bad-audio 
     963 
     964[http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/2008-January/001534.html Tzury Bar Yochay posted this] on PJSIP mailing list: 
     965 
     966 ''"Within a layout of Asterisk as server, a soft-phone on a desktop workstation (SJPhone), and pjsua_wince on WM5 device I am experiencing the following symptom: Voice spoken at the desktop end is heard well in the mobile device, but not the vice versa. e.g., words spoken on the mobile device yields a metallic effect in the PC Speaker."'' 
     967 
     968The solution is to increase the sound buffer count to accommodate audio frame burstiness on Windows mobile, by declaring this on your {{{config_site.h}}}: 
     969 
     970{{{ 
     971  #define PJMEDIA_SOUND_BUFFER_COUNT  16 
     972}}} 
     973 
     974Increasing sound buffer count will increase audio latency, so please do some experiments to get the lowest value to get the best latency without breaking the audio quality. 
     975 
     976 
    962977---- 
    963978