Uploaded image for project: 'FreePBX'
  1. FreePBX
  2. FREEPBX-21523

Updating pjsip settings creates multiple duplicate key-values in database

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Not an issue
    • Affects Version/s: 15.0.16.42
    • Fix Version/s: None
    • Component/s: Asterisk SIP Settings
    • Labels:
      None
    • Bug Tracker:
      Customer Issue
    • ToDo:
    • Asterisk Version:
      13.20.0
    • Distro Version:
      18.04
    • Distro:
      Self Install Ubuntu

      Description

      When updating certain fields on the pjsip settings page, additional key-value pairs are created in the database, rather than updating the existing ones.

      When reloading the page, it shows the first instance of the relevant key-value pairs.

      When applying the configuration, it uses the first instance of the relevant key-value pairs.

      Therefore, the GUI cannot be used to change these values.

      To replicate:

      • Goto SIP Settings (chan_pjsip) - /admin/config.php?display=sipsettings
      • Change any of these values:
        • Transports (udp, tcp, tls, ws, wss)
        • Endpoint Identifier Order
        • Any of the specific transport settings (e.g. UDP / port to listen to)
      • Click SUBMIT and then "Apply Config"
      • Navigate away from the page and back again to force the script to reload the values from the database
      • The previous values will be displayed - the updated values are not shown
      • Examine the contents of the relevant pjsip*.conf files in /etc/asterisk
      • The file timestamps are updated, but the values are the previous values
      • Use an SQL Browser to inspect table kvstore_Sipsettings
      • There will be multiple entries using the keys "binds", "pjsip.identifiers.order", "pjsip_identifiers_order" etc. with varying values
      • There may be more fields affected than this - I didn't exhaustively test.

      Workaround:

      • In the SQL browser, delete the duplicate key-value records and create only one key-value pair with the desired value.

      I don't believe this is the intended behaviour of updating values, so raising this is a bug.

      Note - this is on FreePBX 15.0.16.49, which isn't available as a version in the Affects Version field.

       

        Gliffy Diagrams

          Attachments

          1. image-2021-05-21-12-27-15-580.png
            image-2021-05-21-12-27-15-580.png
            35 kB
          2. pjsip.transports.conf
            3 kB
          3. sql_browse.png
            sql_browse.png
            46 kB
          4. sql_dump.png
            sql_dump.png
            38 kB

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                nickpiggott Nick Piggott
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  NextupJiraPlusStatus

                  Error rendering 'slack.nextup.jira:nextup-jira-plus-status'. Please contact your Jira administrators.