Search results

How did you set outbound route? About call direction, I had a same problem. I wrote about it here.

Hi Robert, check if you have call_direction correctly set by dialplan. I vaguely remember that I had a problem like this. I posted about it here. BR

just another important thing regarding upgrades on CentOS. Default FPBX install script for centos installs freeswitch-config-vanilla, whoes content gets deleted in the next steps. When upgrading, this package is installed again, which breaks everything. On new installs...

Hi, problem after upgrading to FS 1.10. Alredy solved in this thread, which is closed: https://www.pbxforums.com/threads/cant-connect-to-db.3434/ I will just leave here instructions for CentOS 7 + FS from Okay repo: cat << 'EOF' > /etc/freeswitch/autoload_configs/pre_load_modules.conf.xml...

because it's more of a workaround than a solution. I've just added: session:setVariable("sip_h_Diversion", "<sip:" .. caller_destination .. "@" .. domain_name .. ">;privacy=off;counter=1;screen=no"); in /usr/share/freeswitch/scripts/app/ring_groups/index.lua I am not sure thats the way to go...

looks like, this was triggered by adding a new domain. for now, I commented out the line $obj->copy_files(); from /var/www/fusionpbx/app/scripts/app_defaults.php

I agree, Kevin is the worst..

KonradSC, thanks a million :D I really hope that's it. Is there anything else that could do that?

Hi, here I have one CentOS 7 FPBX install. Customer's system requires Diversion header on transfered calls. There is no such functionality in FPBX, so I had to fix some scripts in /usr/share/freeswitch/scripts/, to include Diversion header. Problem I have now is that every now and then, the...

Hi noci, thanks for your suggestions. For now everything is working fine, so I will not play with it anymore if not needed. When some problem arises I will surely try your suggestion. Just fyi, I think "inline=true" has no meaning in export application?

in your log, I see: c3a98802-156a-4775-82d3-05e047b6e64e 2019-06-11 15:51:13.718681 [DEBUG] switch_channel.c:1250 sofia/internal/1111@pbx.example.com EXPORTING[export_vars] [rtp_secure_media]=[optional] to event That's why the SDP sent to B-leg looks like this...

that's why I used regex. afaik that's the way.. In your case I would use regex ^(3\d{2})$

you should set either inbound route for 304, or inbound route for regex num or a destination. My inbound route looks like this: <extension name="local-in" continue="false" uuid="26e002d7-de31-45d2-9150-46fe139d8be1"> <condition field="destination_number" expression="^(10690517[0-9])$">...

FS is sending both SRTP and RTP to b-leg. Maybe b-telephone does not like that. I had something similar once. Set FS to only SRTP

do you have problem with installation or with connecting to twillio?

It seems like you didn't set up inbound routes or destinations properly. What do you have there?

I do not have NAT on this system, it's on public IP, connected to the ACME SBC over TLS trunk. Phones are also connected through the SBC. So, you are probably talking about a problem from a sticky thread above? I saw you already found a solution, good job!

yes, but it's never set. it's always empty and thus set as "local" by the call-direction extension. I don't know what should set call-direction variable? I used info application and I saw that there was "direction" variable set, so I just set call-direction to direction, so now, when call hits...

Hi DD, what do you mean exactly? I've called from mobile to inside, hangup on mobile before answer or after answer and I do not see nothing in show channels. What do you mean by "showing on the extension" ?

When call hits call-direction extension, it's always empty and thus set as "local". I've tried to find out the reason but I'm not sure I got this right. I found out that FS sets the variable "direction", so I inserted another extension before "call-direction": <extension...