On Thursday 04 April 2019 at 17:59:07, Karsten Wemheuer wrote:
> Am Sonntag, den 10.03.2019, 12:46 +0300 schrieb Gokan Atmaca:
> >
> > Mynum: 6001 , Othernum: 6002.
> >
> > I can record as follows. But I do not enter individual records for
> > each internal required. I want to do it more smoothl
The Asterisk Development Team would like to announce the release of Asterisk
16.3.0.
This release is available for immediate download at
https://downloads.asterisk.org/pub/telephony/asterisk
The release of Asterisk 16.3.0 resolves several issues reported by the
community and would have not been p
Hi,
Am Sonntag, den 10.03.2019, 12:46 +0300 schrieb Gokan Atmaca:
> Hello
>
> Mynum: 6001 , Othernum: 6002.
>
>
> I can record as follows. But I do not enter individual records for
> each internal
> required. I want to do it more smoothly with a Macro.
>
> Thanks.
>
> exten => _6001,1,NoOp()
> ext
The Asterisk Development Team would like to announce the release of Asterisk
13.26.0.
This release is available for immediate download at
https://downloads.asterisk.org/pub/telephony/asterisk
The release of Asterisk 13.26.0 resolves several issues reported by the
community and would have not been
Thanks Joshua.
Hopefully I'll be able to retry tomorrow.
On Thu, 4 Apr 2019 at 15:30, Joshua C. Colp wrote:
> On Thu, Apr 4, 2019, at 11:27 AM, Mark Farmer wrote:
> > Thanks, I did enable debugging but didn't see any attempts to resolve
> > hostnames. I will give it another look.
> >
> > I did
On Thu, Apr 4, 2019, at 11:27 AM, Mark Farmer wrote:
> Thanks, I did enable debugging but didn't see any attempts to resolve
> hostnames. I will give it another look.
>
> I did have an empty resolver_unbound.conf (not even a general context)
> - would that likely cause issues? I would expect the
Thanks, I did enable debugging but didn't see any attempts to resolve
hostnames. I will give it another look.
I did have an empty resolver_unbound.conf (not even a general context) -
would that likely cause issues? I would expect the defaults to kick in but
I have now added:
[general]
hosts=syste
On Thu, Apr 4, 2019, at 11:18 AM, Mark Farmer wrote:
> Seems to be res_resolver_unbound.so
> Reading the documentation now but any hints greatly appreciated!
The general section of the resolver_unbound.conf file has various options,
including for using the /etc/hosts file. Per my previous email t
Seems to be res_resolver_unbound.so
Reading the documentation now but any hints greatly appreciated!
Mark.
On Thu, 4 Apr 2019 at 15:07, Joshua C. Colp wrote:
> On Thu, Apr 4, 2019, at 11:03 AM, Mark Farmer wrote:
> > Sorry, should have included that.
> >
> > Asterisk 16.2.1
>
> And what res_r
On Thu, Apr 4, 2019, at 11:03 AM, Mark Farmer wrote:
> Sorry, should have included that.
>
> Asterisk 16.2.1
And what res_resolver module is loaded and in use? Depending on the module it
may not be using /etc/hosts. You can also increase debug (debug to console in
logger.conf and core set debug
Sorry, should have included that.
Asterisk 16.2.1
Mark.
On Thu, 4 Apr 2019 at 14:56, Joshua C. Colp wrote:
> On Thu, Apr 4, 2019, at 10:53 AM, Mark Farmer wrote:
> > As I understand it, delays like this are almost always caused by slow
> > or failing DNS lookups. Running a packet capture on a
On Thu, Apr 4, 2019, at 10:53 AM, Mark Farmer wrote:
> As I understand it, delays like this are almost always caused by slow
> or failing DNS lookups. Running a packet capture on all interfaces
> filtering on port 53 shows no DNS traffic leaving the server. I have
> ensured that there is a DNS r
As I understand it, delays like this are almost always caused by slow or
failing DNS lookups. Running a packet capture on all interfaces filtering
on port 53 shows no DNS traffic leaving the server. I have ensured that
there is a DNS record for the server & that it can resolve it. I've also
added r
On Thu, 2019-04-04 at 15:08 +0200, Antony Stone wrote:
>
> It's not "Password", it's "Secret" :)
Ha ha. I knew it would be a head-smack type problem.
Cheers,
b.
signature.asc
Description: This is a digitally signed message part
--
On Thursday 04 April 2019 at 14:28:15, Brian J. Murrell wrote:
> # echo -e "Action: Login\r\nUsername: myasterisk\r\nPassword: a\r\n\r\n"
It's not "Password", it's "Secret" :)
Antony.
--
I don't know, maybe if we all waited then cosmic rays would write all our
software for us. Of course it m
I'm not sure how much more simple I can make this but I just cannot
seem to get my Asterisk 13 to accept a connection on the manager
interface:
--- manager.conf ---
[general]
enabled = yes
port = 5038
bindaddr = 127.0.0.1
[myasterisk]
secret=a
permit=0.0.0.0/0.0.0.0
read = all
write = all
So,
Hi all,
I switched an old asterisk 1.8 to a new 13 version, stock version from
Ubuntu 18.04 server.
I did some modification in dialplan but after a reload they are not
taken in account :(, even after restarting asterisk.
I checked logs and found lots of
merging incls/swits/igpats from old(
17 matches
Mail list logo
