Call Group Pickup / Intercept

[dcitelecom]

I can't get call pickup to work in a group. I created a call group "ABC" with 4 extensions and want to pick up incoming calls to any extensions not answered on another extension. I tried *8 and ** but it's not working. Can anyone help? Thanks.

 

[krooney]

you need to make sure the path to the FreeSWITCH database is correct

 

[dcitelecom]

you need to make sure the path to the FreeSWITCH database is correct

I am not sure I understand. This system has been running without issues for 2 years. Surely database access is defined correctly. I only have a problem with the Call Group Pickup as explained above.

 

[krooney]

Just check
etc/fusionpbx/config.conf

And see if settings are good if using default or RAM drive

 

[dcitelecom]

Just check
etc/fusionpbx/config.conf

And see if settings are good if using default or RAM drive

#database
database.1.type = pgsql
database.1.host = 127.0.0.1
database.1.port = 5432
database.1.sslmode=prefer

#switch settings
switch.conf.dir = /etc/freeswitch
switch.sounds.dir = /usr/share/freeswitch/sounds
switch.database.dir = /var/lib/freeswitch/db
switch.recordings.dir = /var/lib/freeswitch/recordings
switch.storage.dir = /var/lib/freeswitch/storage
switch.voicemail.dir = /var/lib/freeswitch/storage/voicemail
switch.scripts.dir = /usr/share/freeswitch/scripts

#switch xml handler
xml_handler.fs_path = false
xml_handler.reg_as_number_alias = false
xml_handler.number_as_presence_id = true

 

[krooney]

In your switch variables what is set in DSN

 

[dcitelecom]

Thanks for trying to help but I don't know where to find these values. There is no DSN switch variable in fusionpbx.

 

[krooney]

If you go to menu advanced variables its there

 

[dcitelecom]

I have 72 switch variables. None are called DSN or Data Source

 

[krooney]

what is the error you get in fs_cli when trying to intercept

 

[markjcrane]

The answer to the question depends on the version of FusionPBX. Please share your version.

Note: The DSN is not in FusionPBX by default. It is added manually for certain circumstances.

 

[Chiral]

I had the same issue after updating to 5.3. The issue appears to be related to the updated version of the intercept.lua script file dated when upgrade completed. I restored the intercept.lua file to the version of the previous version and call pickup with *8 works again.

The updated intercept.lua script causes an INVALID PROFILE error in the logs on call pickup.