Skip to content
Snippets Groups Projects
  1. Mar 06, 2022
  2. Jul 22, 2021
  3. Jun 24, 2021
  4. Jun 17, 2021
  5. Jun 16, 2021
    • George Joseph's avatar
      res_pjsip_messaging: Overwrite user in existing contact URI · 702e1d33
      George Joseph authored
      When the MessageSend destination is in the form
      PJSIP/<number>@<endpoint> and the endpoint's contact
      URI already has a user component, that user component
      will now be replaced with <number> when creating the
      request URI.
      
      ASTERISK_29404
      
      Change-Id: I80e5910fa25c803d1440da0594a0d6b34b6b4ad5
      702e1d33
  6. Jun 15, 2021
    • Bernd Zobl's avatar
      res_pjsip/pjsip_message_filter: set preferred transport in pjsip_message_filter · 80478803
      Bernd Zobl authored
      Set preferred transport when querying the local address to use in
      filter_on_tx_messages(). This prevents the module to erroneously select
      the wrong transport if more than one transports of the same type (TCP or
      TLS) are configured.
      
      ASTERISK-29241
      
      Change-Id: I598e60257a7f92b29efce1fb3e9a2fc06f1439b6
      80478803
    • Naveen Albert's avatar
      pbx_builtins: Corrects SayNumber warning · 2b174a38
      Naveen Albert authored
      Previously, SayNumber always emitted a warning if the caller hung up
      during execution. Usually this isn't correct, so check if the channel
      hung up and, if so, don't emit a warning.
      
      ASTERISK-29475
      
      Change-Id: Ieea4a67301c6ea83bbc7690c1d4808d79a704594
      2b174a38
  7. Jun 11, 2021
    • Jaco Kroon's avatar
      func_lock: Prevent module unloading in-use module. · 6b678210
      Jaco Kroon authored
      
      The scenario where a channel still has an associated datastore we
      cannot unload since there is a function pointer to the destroy and fixup
      functions in play.  Thus increase the module ref count whenever we
      allocate a datastore, and decrease it during destroy.
      
      In order to tighten the race that still exists in spite of this (below)
      add some extra failure cases to prevent allocations in these cases.
      
      Race:
      
      If module ref is zero, an LOCK or TRYLOCK is invoked (near)
      simultaneously on a channel that has NOT PREVIOUSLY taken a lock, and if
      in such a case the datastore is created *prior* to unloading being set
      to true (first step in module unload) then it's possible that the module
      will unload with the destructor being called (and segfault) post the
      module being unloaded.  The module will however wait for such locks to
      release prior to unloading.
      
      If post that we can recheck the module ref before returning the we can
      (in theory, I think) eliminate the last of the race.  This race is
      mostly theoretical in nature.
      
      Change-Id: I21a514a0b56755c578a687f4867eacb8b59e23cf
      Signed-off-by: default avatarJaco Kroon <jaco@uls.co.za>
      6b678210
    • Jaco Kroon's avatar
      func_lock: Add "dialplan locks show" cli command. · 6f303335
      Jaco Kroon authored
      
      For example:
      
      arthur*CLI> dialplan locks show
      func_lock locks:
      Name                                     Requesters Owner
      uls-autoref                              0          (unlocked)
      1 total locks listed.
      
      Obviously other potentially useful stats could be added (eg, how many
      times there was contention, how many times it failed etc ... but that
      would require keeping the stats and I'm not convinced that's worth the
      effort.  This was useful to troubleshoot some other issues so submitting
      it.
      
      Change-Id: Ib875e56feb49d523300aec5f36c635ed74843a9f
      Signed-off-by: default avatarJaco Kroon <jaco@uls.co.za>
      6f303335
Loading