similar to: asterisk 1.2 with grandstream ht-496 2nd port registration issues

Hi, Has anybody come across a situation where they were unable to register with Asterisk through a SIP stateless proxy server? I'm getting an error: "403 Authentication user name does not match account name" As far as I can tell the requests reaching Asterisk with and without the proxy are identical excepting the IP address the REGISTER request is coming from and the Via header

Hi. I'm stuck into an odd situation. Here's what happens: 4 Thomson ST2030S 2 Cisco 7912 3 Cisco 7940 2 AAstra 480i Asterisk 1.2.17 Diva 4BRI + chan_capi I've just upgraded yesterday from Asterisk 1.2.13 to 1.2.17. Until yesterday, everything was just fine with 1.2.13. Immediately after the upgrade, *all* the 7940 are no more able to make calls, just receive them, while 7912

I am having a problem registering my cisco phones which is exactly like that described in http://lists.digium.com/pipermail/asterisk-users/2011-May/262306.html except that I am on Asterisk 1.8.3.3 and using sip level POS3-07-4-00 The symptoms are: o 7960 lines show [X] o Outbound calls can be made from the phone, including call pickup of inbound calls, but not to it. o Trace shows REGISTER

merb_dispatcher.rb:28 controller = klass.build(request.body, request.params, route, response) Why not just use a typical constructor? merb_dispatcher.rb:35 raise Merb::HTTPMethodNotAllowed.new(method, allowed) Why not check for this after the action has been dispatched to the controller? controller_mixin.rb:149 def query_parse(qs, d = ''&;'') Why not offload query parsing

> > - many directories are not svn:ignore'd in llvm-top, e.g. > > cfe, llvm-gcc-4.0, llvm. "svn st" shows you which one. > > Yeah, again, that's a module maintainer's issue. I can't be > cleaning up after everyone. People are just going to have to > learn how to use subversion properly. I try to fix things > where I find them, but there's

Should I submit this as a proper bug, or will someone look at it? Basically, between 4.7-REL and 4.8-REL ssh was upgraded and now exhibits the following bug. If you connect with protocol v1 you get three ssh processes, one of which never dies, even after the ssh session has been closed. % ps aux | grep ssh root 219 0.0 0.0 4076 0 ?? IW - 0:00.00 sshd: paul [priv root

Sadly the patch on https://reviews.llvm.org/D55585 didn't apply on my clone of llvm at all :( It will take me quite some time to test this out. On Mon, Feb 25, 2019 at 5:08 PM Alexandre Ganea <alexandre.ganea at ubisoft.com> wrote: > > For enabling large memory pages, see this link: https://support.sisoftware.co.uk/knowledgebase.php?article=52 > > Meow hash isn't in the

Times for lld compiled with LTO: Input File Reading: 1430 ms ( 3.3%) Code Layout: 486 ms ( 1.1%) PDB Emission (Cumulative): 41042 ms ( 94.6%) Add Objects: 33117 ms ( 76.4%) Type Merging: 25861 ms ( 59.6%) Symbol Merging: 7011 ms ( 16.2%) TPI Stream Layout: 996 ms ( 2.3%) Globals Stream Layout:

Hi Holger, On Thu, 2007-08-16 at 09:02 +0200, Holger Schurig wrote: > Hi Raid ! > > I used llvm-top at home and in the company and I basically I like > it. Thanks for trying it out! :) > Here are some comments: > > - the README.txt says that all routines use a common library > and therefore accept a common set of arguments. But this > is confusing, because

As for multithreaded ghashes: Even if the hashtable stores 32-bit indices to SeenHashes, you would still need to compare the ghashes for collisions: https://github.com/llvm/llvm-project/blob/master/llvm/include/llvm/ADT/DenseMap.h#L627 Finding the 32-bit index in the hashtable doesn’t necessarily mean it’s the right one. The following table shows the collision distribution when inserting (type)

Hi Raid ! I used llvm-top at home and in the company and I basically I like it. Here are some comments: - the README.txt says that all routines use a common library and therefore accept a common set of arguments. But this is confusing, because things like VERBOSE look like an environment variable. Somehow people are used that arguments are always starting with - and that they are

This could be ICF. There were lots of issues with ICF on ARM64, but they are not inherently ARM64-specific, they just come up there more often. See https://reviews.llvm.org/D56986 which fixes that. Easiest thing is always to profile or add /time to see what's slow. On Wed, Feb 27, 2019 at 6:30 AM Leonardo Santagada <santagada at gmail.com> wrote: > Anyone would know why lld takes

Hi all, I''m new to shorewall and have been struggling with several problems for several days now. Most of them are solved, but one still persists. The firewall is running on my server under Debian Sarge (Kernel 2.6) I''ve got three network interfaces: ppp0 (DSL Internet) eth1 (lan) ath0 (wlan) eth1 and ath0 are bridged together to br0. The problem is, that Samba (also running

Yes, -Tllvm works. [cid:image002.jpg at 01D4CCF6.C440CFF0] From: Zachary Turner <zturner at google.com> Sent: Monday, February 25, 2019 10:36 AM To: Leonardo Santagada <santagada at gmail.com> Cc: Alexandre Ganea <alexandre.ganea at ubisoft.com>; Reid Kleckner <rnk at google.com>; llvm-dev <llvm-dev at lists.llvm.org> Subject: Re: [llvm-dev] Making LLD PDB