Recent content by whut

It may be wise to add libtool to dependencies in the install.sh https://github.com/fusionpbx/fusionpbx-install.sh/blob/master/debian/install.sh

watch the installation and see all of the errors. there are probably many freeswitch errors throughout, starting with installation of freeswitch perhaps

Run these 2 suggested commands. One of them will probably provide more details on the issue.

Are you logging B-leg? You do see extra records in CDR page (a-leg cdr and b-leg cdr) if you have enabled logging b-leg.

you can search freeswitch logs cd /var/log/freeswitch/ grep -Ern --color --include=freeswitch.log* "REGISTER.*for.*from ip" in fs cli fs_cli -x "show registrations" fs_cli -x "show registrations as xml" count: fs_cli -x "show registrations as xml" | grep reg_user | wc -l I would add to a...

this displays automatic provisioned devices ONLY. You are out of luck checking log files etc for manually provisioned devices, so be aware of the pain of no data manually provisioned devices. Device log page you will see that device xyz hit the server again on intervals to update the remote...

Hey! `sofia global siptrace on` did it. I now have these variables that include "hold" hold_stamp 2025-03-27 16:52:50 hold_events {{1743094370484252,1743094373098185}} hold_accum_ms 2613 hold_accum_usec 2613933 last_hold_epoch 1743094370 last_hold_uepoch...

Oh! Now how/why do we not have any of these values on so many servers? Did you modify any of the autoload_config xml files to enable? I don't know how to enable. I am using hardware phones.

Do you have these variables populated? I have many installations with multiple branches and so far I do not see any CDRs with these values != 0

I am wanting to know a few things about a call in fusionpbx like "has this call been on hold?" and "what is the total time this call has been on hold?". I found these variables inside the CDR details, but they are always 0. hold_accum_ms 0 hold_accum_usec 0 last_hold_epoch 0...

You will probably need to export and evaluate removing duplicates or write a SQL query to get the distinct list of devices.

I have disabled ring groups and I have disabled end points within ring groups and I cannot duplicate your bug @pbxgeek. What is your version of fusionpbx code?

Try device logs https://github.com/fusionpbx/fusionpbx-app-device_logs

hmmm. That is good to be aware of. Were you having an issue registering through UDP when automatic provisioning? I would not expect that you would have an issue with this when automatically provisioning because the yealink_rport default setting is enabled by default and the Yealink provisioning...

But if you were to delete the table you do not need to figure out how to recreate it and the perfect schema manually. Fusionpbx will recreate it when you run the updates 2 - 5 on the upgrades page. That is part of the brilliance and power built into fusionpbx.