search for: unauthent

Afternoon All, Today rolled a pre-production box from Trunk back to 1.4.7 (In an attempt to get a working SCCP channel). During the process Music On Hold appears to have died (Not, just when calling from a SCCP device, but coming in on SIP also). CLI is showing -- Executing [XXXXXXXX at unauthed-inbound:2] MusicOnHold("SIP/10.97.1.33-09f0cfc8", "sounds") in new stack

Good afternoon, please have a look into your MUA setup. You keep breaking threading for this thread (In-Reply-To header is set incorrectly). On Tue, 2020-02-11 at 13:40 +0000, user wrote: > > On Thu, 2020-02-06 at 19:20 +0000, user wrote: > > > 2020-01-08 09:59, Marvin Scholz wrote: > > > Expectation on malicious activity force me to put icecast behind reverse > >

Hello, When I tried to install chan_h323-1.0.1-module.i386 RPM i got these errors. Failed dependencies: libh323_linux_x86_r.so.1 is needed by chan_h323-1.0.1-module.i386 libpt_linux_x86_r.so.1 is needed by chan_h323-1.0.1-module.i386 But i found the same files in /usr/lib/libh323_linux_x86_r.so.1 /usr/lib/libpt_linux_x86_r.so.1 What to do for asterisk to detect the same

Philipp Schafft, who allow you to publish my private message? > Remove > > -Pete > > > On Feb 13, 2020, at 8:46 AM, Philipp Schafft <lion at lion.leolix.org> wrote: > > > > ???Good afternoon, > > > > please have a look into your MUA setup. You keep breaking threading for > > this thread (In-Reply-To header is set incorrectly). > >

Ok, here's what I think we should release as 1.17. I plan on doing that in a few days (Monday? Tuesday?), unless there's some good reason not to. Let me know if there's some critical (i.e. crashing) fixes that I've missed somehow. And, again, I think we can run a shorter 1.18 cycle, given the pent-up list of fixes. Sorry for not getting this wrapped up sooner. Turns out that

Hello all, I have installed the .deb packages of the Asterisk v1.8.3.3 from the upstream project on my Debian GNU/Linux Squeeze server and bought the Comodo's PossitiveSSL SSL certificate to be used for my SIP/TLS exercise. After setting up everything and trying to fix this problem, I am still getting a 401 Unauthorized SIP message. So as of this writing, I still cannot successfully REGISTER