Search results

You would normally associate the BLF key with a line or can be "0" if you have only one line. An example of provisioning BLFs in fusion is shown below in the Keys section of the device record:

It looks like the additional characters are HTML entities, when you see this it usually means that the HTML has been escaped more than once. https://www.w3schools.com/html/html_entities.asp

Without seeing a packet capture of the inbound call it is difficult to diagnose but in Gateway Advanced, you could try setting Extension to auto_to_user

It may be related to this thread: https://www.pbxforums.com/threads/500-internal-server-error-from-yealink-phones-on-blf-notify.2918/

BYE transactions that result in "SIP/2.0 481 Call Leg/Transaction Does Not Exist" are often caused by some sort of ALG in the nattting router. Some ALGs do a wholesale find and replace of anything that looks like an IP address in an attempt to change any internal addresses into external ones...

I believe by default, idle keys are solid green if set as BLF keys, but idle keys set as lines are off.

Do you have these keys configured as BLF or just line keys? The reason I ask is because an idle BLF (BLF LED mode = 0) will show solid green but for a line key, an idle line will cause the LED to be off.

You may want to make your NAT detection a little more aggressive, snippets from my Opensips config: In main route: # ----------------------------------------------------------------- # NAT Check/Fix Section only on customer IPs #...

Hi Philip, I'm UK based running VoIP since 2008 and commercially since 2016 and have never had the need to use 100rel. 1xx responses are classed as provisional responses like "100 Trying" or "180 Ringing". Unlike final responses (2xx - 6xx), which are acknowledged (ACK), originally there was...

Hmm... Sounds like it could be a bug, what software version are you running? Clearly something has been created otherwise you would not see the duplicate device error. If you are comfortable with SQL you could always query the devices table (v_devices) to see what is actually in it. There...

When you were creating the device (before saving), was the correct domain showing in the "Domain" select box for the device record? Did you try a "Show All" in the device listing to try and find what had been created?

It is certainly something to do with the year changing, some of these phones where first registered in 2018, some in 2020 and the same issue has occurred every New Year. It may well be related to the CSeq number being generated by FreeSWITCH following the roll over into the New Year. I do have...

I believe those default settings are used to pre-populate the form when you add a new device or new device line, they will not have any effect on device records that have already been created.

I don't believe that Fusion click-to-Call is something that you can embed on a website unless the pages concerned are accessed by specific users also known to FusionPBX. The reason is that the Click-to-Call needs to know which FusionPBX user is calling the application in order to know which...

This is probably one of the easiest solutions to use/adapt for your needs. I built two versions one for Chrome and one for Firefox. You may need to set up a Mozilla developer account if you want to get your version signed for a smooth Firefox install...

We do not use Docker for FusionPBX but we do use it for a Business to Business gateway with BT Openreach. I'm no Docker expert, in fact I have not touched it since I migrated the B2B on to it. So I guess you will start by spinning up a VM and loading Docker on to it. It is generally a good...

Happy New Year everyone! Just to let you know that this issue is happening again on my platform. Not sure if it is CSeq related as mentioned in the post above because my CSeq numbers for NOTIFY messages are still quite high: U 2021/01/01 10:40:06.214221 999.999.999.99:1058 ->...

It has been removed for security reasons, check out the thread below: https://www.pbxforums.com/threads/cannot-login-to-postgres-database-using-adminer.4602/

You should not need to put this in a profile record. If the edit controls for primary and secondary address are not showing on the line in your device record, you may need to enable them in Advanced->Group manager (click on Permissions for superadmin). Screenshot below:

I would definately start by looking at the "403 Too many simultaneous". Again, looking at the headers in that 403 message may help you further.