Search results

I have spotted this but think its cost prohibitive to be honest https://www.broadbandbuyer.com/products/35796-cisco-cp-8821-k9%3D/#content

Adrian thanks for that suggestion howerver they have to be able to cary the phone around on them. I knwo pita :)

Adrian I totally agree with you on this one, but on this occasion these phones are going into peoples actual homes until they can return to work and may also be getting passed around to different houses (Care workers). Hence the need for a more compact solution.

Hi Ive been asked to source a cordless dect phone. The stipulation is that it must not have a separate hub for example the charger for the phone is also the hub that connects to the network. If that makes sense.

Thats why I prefare the phonebook method OK I have to manully add the url to the phones but once its done its done.

Managed it using 'https://{username}:{password}@{domain}.com/app/provision' although I dont know if this is going to be useful for me and we use multi tenant and like to configure the phones before we send them out.

The contacts App on fusion is not very user friendly though the phonebook seems ta lot easier for users who need to login and use.

its gave me a head ache to start with but that was because my install is not playing nicely with the spi keys :)

Sorry for soounding a bit think but how do you take account for the provisioing username and password using option 66. also I dont think this would fit our needs as usually we wont have access to customers dhcp.

Phonebook app mantion here: https://www.pbxforums.com/threads/phonebook-only-supports-yealink-currently.161/ Ill have a look at the DHCP option 66

Hi Me again Not looked at autoprovisiong before to be honest asn we oly get the phones and set them up manulaly before we deliver them and never in any great numbers 10 or so at the most. But today ive been trying to convice myself we should do it more so that if we need to change a setting...

Is it possible to use SRV records to register phones on Multi tenant pbx? sorry if this is a dumb question but then again I am dumb :) Edit : Thought i had better explain myself a little better here. Not very clued up on this type of thing really. as I understand it (limited as you can...

I ended up reinstallin the server although still having issues ill keep you updated :)

postgres@pbx:~$ psql psql (9.4.15) Type "help" for help. postgres=# \d No relations found. postgres=# \db List of tablespaces Name | Owner | Location ------------+----------+---------- pg_default | postgres | pg_global | postgres | (2 rows) postgres=# so seems the db is...

mmmmm root@pbx:/etc/cron.daily# service freeswitch stop root@pbx:/etc/cron.daily# service nginx stop root@pbx:/etc/cron.daily# service postgresql stop root@pbx:/etc/cron.daily# service postgresql start root@pbx:/etc/cron.daily# su postgres bash: /etc/bash.bashrc: Permission denied bash-4.3$

It sounds like whatever you ran in cron.daily has done something nasty to your database. But at least you have a backup right? This i sthe test server i setup to see if i can do a restore to be honest so im not that fussed but i do need for my own sanity to find out where i have gone wrong...

at the end of the log file i get this 2020-06-25 08:06:01 UTC [25848-2] fusionpbx@fusionpbx STATEMENT: select * from v_domains 2020-06-25 08:06:01 UTC [25848-3] fusionpbx@fusionpbx ERROR: relation "v_software" does not exist at character 15 2020-06-25 08:06:01 UTC [25848-4]...

2020-06-21 14:14:20 UTC [24851-1] fusionpbx@fusionpbx ERROR: duplicate key valu e violates unique constraint "v_xml_cdr_pkey" 2020-06-21 14:14:20 UTC [24851-2] fusionpbx@fusionpbx DETAIL: Key (xml_cdr_uuid )=(58bb99a4-bd2f-4867-a897-6ec2d41815d8) already exists.

Morning Adrian Hope your well and thanks for replying so quickly root@pbx:~# ps ax | grep postgres 1850 pts/2 S+ 0:00 grep postgres root@pbx:~#

Hi I have been testing the back up and restore to a different server I ran it manually last night and it all worked fine from what i could see. I places the script into cron.daily but i think i did something wrong. This morning I tried to connect to the new server and got this: error...