Search results

  1. M

    Freeswitch WSS crash after 1 week

    After a long follow-up on this topic (https://github.com/bigbluebutton/bigbluebutton/issues/9667) I still haven't found the exact cause. looks like freeswitch user doesn't use wss
  2. M

    Freeswitch WSS crash after 1 week

    Describe the bug Freeswitch stops working after recurring period of time, mostly after one or two days. Clients are unable to connect and receive WebSocket Secure port 7443 and SIP port 5060. Freeswitch not response. Restart freeswitch of the complete is needed. Afterwards everything works fine...
  3. M

    Click to call

    Sadly, the cdr of the call by clicking to call is incorrect, the important thing is: the billecard is incorrect. Request to ext 1000 => answered Wait to call MOBILE => Wait 20s MOBILE answered => talk 10s Hangup => Billsec = 30s If accurate, it must be 10 seconds Can you give me some advice ??
  4. M

    Performance tuning fusionpbx

    Many thanks for your reply!! @Adrian Fretwell Your share is extremely useful, to be able to optimize systems that require a lot of experience including systems, networks, ... and a logical thought. I think I need to learn more before I can start to optimize system
  5. M

    Performance tuning fusionpbx

    Hi all, My Fusionpbx had an audio failure when it reached 700 session (350 call). CPU 30% , RAM 30%, I/O a few Call is connected but lost sone sound. Very uncomfortable I think problem in UDP package or config jitter in freeswitch. What can I do to handle this situation ???
  6. M

    How to use xml_cdr command

    Hi there, Fusionpbx 4.4.1 ; Freeswitch 1.8.6 ; Debian 9.9 I have file xml_cdr.conf.xml <param name="url" value="http://127.0.0.1/app/xml_cdr/v_xml_cdr_import.php"/> <param name="cred" value="Uhu7mgti8YC2xys2:1zMeO3p2XJrNzNwg"/> <param name="log-dir" value=""/> <param...