Search results

Getting closer, have you got the keys set to the correct lines? I think you *can* do the Line 0 trick with BLFs, but I'm not sure.

As for the lua.conf.xml, that's perfectly normal unless you want the 'extended' uses of BLFs (i.e, monitor a call flow or a DND status). They're off by default as it does vary wildly from vendor to vendor.

Hmmm, that's interesting. If I had to guess: $yealink_rport That's off by default on Yealinks, but is almost mandatory in most setups. However it could be a SIP ALG thing.... Possibly: features.blf_led_mode = {$yealink_blf_led_mode} if you have change the default settings in the Yealink...

I believe it's a SIP INFO packet, with dialog+info XML inside it. It's very strange it works on some models but not others.

Normally a SIP Provider will be able to give you a list or prefix of IP addresses to whitelist, instead of opening it up to the entire internet.

Basically, it's a built in feature of mod_sofia for FreeSWITCH that doesn't appear to have anyway of disabling (if I recall, I haven't researched the source in a while). If the call is completed elsewhere, FreeSWITCH will send the reason 'Call Completed Elsewhere' and your phone will be...

You appear to be behind NAT, have you set your ext-sip-ip and ext-rtp-ip to be the public address you are presenting from? A 30 second termination means a packet is not being ACK'd and FreeSWITCH tears down a call after 30 seconds believing it to be invalid. You should be able to see this...

Not really, just that your phone is receiving the status change packets when a BLF actually changes.

Lol, no problem. Knew you were gonna kick yourself when I replied.

Odd, I would like to suggest something. But it's just a fundamental part of sip_sofia. Lights for call flows, dnd, etc are set in /etc/freeswitch/autoload_configs/lua.conf.xml but just normal BLF? I would recommend a packet capture either from the PBX using sngrep, or from the Yealink phones...

Ensure you have put the public IP address you get from Amazon in the sip and rtp address section in the variables. Otherwise it will bind to the internal address and Amazon won't use an ALG to fix it.

Enable those agent_authorized lines.

https://www.fusionpbx.com/support Probably best to speak to FusionPBX themselves.

We run the whole gamut of Yealink's in the 4 series, and have never had to do anything particularly special to get call park lights working. We either: - BLF = park+*5901 - Call Park = park+*5901 (Some of the older lads use BLF for EVERYTHING...) It is worth noting the the phones with dual...

destination_number(fo359937ip279332_00) is the clue in the log file here. Look for this default setting, you probably want the ${sip_to_user} option. Fairplay to Plusnet for filling RPID full of nonsense though! Real helpful from them. :rolleyes: Once you've changed this, you'll have to edit...

CPU free. I guess the FreeSWITCH people were sick of getting fault reports about people maxing out their hardware and complaining about lost calls? It makes no sense to me.

It only works with Google Firebase and Apple Push Service out of the box, and neither of those (if I recall) have the ability to wake up a random browser page and bring it to the foreground. You need to hook it into this service that triggers push notifications as you mentioned above. To...

If you haven't done a lot of crazy custom stuff, there's a schema upgrade tool in the upgrade area. This checks the DB schema and updates it. As always with server admin jobs, check your backups and ensure you can restore if anything goes wrong before doing this. As stated, this probably won't...

Have you triggered the Event Guard in your testing? Check it out and see if your IP address got blocked. Other than that, you can use 'sngrep' from the terminal to see if the SIP messages are making it to the PBX. You can also view the log files in /var/log/freeswitch/freeswitch.log or the...

[ERROR: column "call_block_direction" does not exist LINE 4: and call_block_direction = 'inbound' Your table is missing an entire column. I wonder if you missed an update schema some time ago. It might not affect functionality for this fault, but it would annoy the hell out of me. Also, your...