Le 07/05/2014 00:57, Rusty Newton a écrit :
On Thu, May 1, 2014 at 11:08 AM, Administrator TOOTAI ad...@tootai.net wrote:
snip
As explained in one on my previous message, it's a bug, easily reproducible:
take a queues.conf (or sip.conf or iax.conf or voicemail.conf or ...) like
this (what is
Le 07/05/2014 01:28, Steve Edwards a écrit :
On Thu, May 1, 2014 at 11:08 AM, Administrator TOOTAI
ad...@tootai.net wrote:
snip
As explained in one on my previous message, it's a bug, easily
reproducible: take a queues.conf (or sip.conf or iax.conf or
voicemail.conf or ...) like this
Le 07/05/2014 00:57, Rusty Newton a écrit :
[...]
I tried to reproduce using your description here and could not
reproduce the issue.
I tried with both sip.conf and queues.conf.
Making a change in an included .conf file, but NOT the parent .conf
file and then reloading that module from the
On Wed, May 7, 2014 at 2:46 AM, Administrator TOOTAI ad...@tootai.net wrote:
I got it: if the filename is given in totality it's working (as you do it).
It's the #include /path to directorie/*.conf which is not taking in
account (here *.conf description)
That still works for me as well.
I
Le 07/05/2014 16:50, Rusty Newton a écrit :
On Wed, May 7, 2014 at 2:46 AM, Administrator TOOTAI ad...@tootai.net wrote:
I got it: if the filename is given in totality it's working (as you do it).
It's the #include /path to directorie/*.conf which is not taking in
account (here *.conf
Administrator TOOTAI wrote:
Le 07/05/2014 16:50, Rusty Newton a écrit :
On Wed, May 7, 2014 at 2:46 AM, Administrator TOOTAI
ad...@tootai.net wrote:
I got it: if the filename is given in totality it's working (as you
do it).
It's the #include /path to directorie/*.conf which is not taking in
Le 07/05/2014 17:22, Joshua Colp a écrit :
Administrator TOOTAI wrote:
Le 07/05/2014 16:50, Rusty Newton a écrit :
On Wed, May 7, 2014 at 2:46 AM, Administrator TOOTAI
ad...@tootai.net wrote:
I got it: if the filename is given in totality it's working (as you
do it).
It's the #include /path
On Wed, May 7, 2014 at 10:14 AM, Administrator TOOTAI ad...@tootai.net wrote:
Le 07/05/2014 16:50, Rusty Newton a écrit :
I contructed a basic sip.conf, and added this line to the end:
#include /etc/asterisk/sip_includes/*.conf
Here is the point. Modify it the way explained in previous
Le 07/05/2014 18:53, Rusty Newton a écrit :
On Wed, May 7, 2014 at 10:14 AM, Administrator TOOTAI ad...@tootai.net wrote:
Le 07/05/2014 16:50, Rusty Newton a écrit :
I contructed a basic sip.conf, and added this line to the end:
#include /etc/asterisk/sip_includes/*.conf
Here is the point.
On Wed, May 7, 2014 at 12:59 PM, Administrator TOOTAI ad...@tootai.net wrote:
Please try the includes *exactly* as I have them in sip.conf (same
directories name and subdirectories) knowing that local is in /etc/asterisk
I used your identical config to narrow it down. I re-opened
On Thu, May 1, 2014 at 11:08 AM, Administrator TOOTAI ad...@tootai.net wrote:
snip
As explained in one on my previous message, it's a bug, easily reproducible:
take a queues.conf (or sip.conf or iax.conf or voicemail.conf or ...) like
this (what is important is the #include):
snip
On Thu, May 1, 2014 at 11:08 AM, Administrator TOOTAI ad...@tootai.net
wrote:
snip
As explained in one on my previous message, it's a bug, easily
reproducible: take a queues.conf (or sip.conf or iax.conf or
voicemail.conf or ...) like this (what is important is the #include):
snip
On Wed, Apr 30, 2014 at 8:37 AM, Administrator TOOTAI ad...@tootai.netwrote:
Le 30/04/2014 15:19, Matthew Jordan a écrit :
On Wed, Apr 30, 2014 at 8:13 AM, Administrator TOOTAI
ad...@tootai.netmailto:
ad...@tootai.net wrote:
Please, people from Digium, Matt again closed the new bug
Le 01/05/2014 16:28, Matthew Jordan a écrit :
On Wed, Apr 30, 2014 at 8:37 AM, Administrator TOOTAI
ad...@tootai.net mailto:ad...@tootai.net wrote:
Le 30/04/2014 15:19, Matthew Jordan a écrit :
On Wed, Apr 30, 2014 at 8:13 AM, Administrator TOOTAI
ad...@tootai.net
: asterisk-users-boun...@lists.digium.com
[mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Administrator
TOOTAI
Sent: Thursday, May 01, 2014 11:04 AM
To: asterisk-users@lists.digium.com
Subject: Re: [asterisk-users] Reload problems with 1.8.27 and 11.9.0 - Someone
else ?
Le 01/05/2014 16
Le 01/05/2014 17:24, Eric Wieling a écrit :
In my experience DNS issues will cause Asterisk to take a long time to reload
and could stop Asterisk for working at all.
List all the IPs of the box in /etc/hosts and make sure /etc/resolv.conf points
to a working nameserver. See if that helps at
Hi,
after upgrade from 11.8.1 to 11.9.0 on our test server, and from
1.8.26.1 to 1.8.27 on production one, some CLI commands like sip
reload or iax2 reload does nothing.
We opened bug 23683 but it was immediately closed by Matt Jordan,
telling that he can't reproduce it. But we can.
Le 30/04/2014 12:15, Administrator TOOTAI a écrit :
Hi,
after upgrade from 11.8.1 to 11.9.0 on our test server, and from
1.8.26.1 to 1.8.27 on production one, some CLI commands like sip
reload or iax2 reload does nothing.
We opened bug 23683 but it was immediately closed by Matt Jordan,
Hi,
some more information could be usefull.
On Wed, Apr 30, 2014 at 12:15:03PM +0200, Administrator TOOTAI wrote:
after upgrade from 11.8.1 to 11.9.0 on our test server, and from
1.8.26.1 to 1.8.27 on production one, some CLI commands like sip
reload or iax2 reload does nothing.
Is Asterisk
Le 30/04/2014 12:39, Administrator TOOTAI a écrit :
Le 30/04/2014 12:15, Administrator TOOTAI a écrit :
Hi,
after upgrade from 11.8.1 to 11.9.0 on our test server, and from
1.8.26.1 to 1.8.27 on production one, some CLI commands like sip
reload or iax2 reload does nothing.
We opened bug
Does a reload (not a sip reload) reload everything or does it also require
the sip.conf file to be modified?
On Wed, Apr 30, 2014 at 5:00 AM, Administrator TOOTAI ad...@tootai.netwrote:
Le 30/04/2014 12:39, Administrator TOOTAI a écrit :
Le 30/04/2014 12:15, Administrator TOOTAI a écrit :
Le 30/04/2014 13:04, Derek Andrew a écrit :
Does a reload (not a sip reload) reload everything or does it also
require the sip.conf file to be modified?
reload as well as module reload chan_sip.so does nothing. Only way i had
till I found why was to restart asterisk :-(
On Wed, Apr 30,
Please, people from Digium, Matt again closed the new bug ASTERISK-23689
I opened (clone from 23683) telling that it's not a bug. Did he
carefully read the comments on the new bug? If not, please forward him
this email, *it's* a bug or you have to explain me why it is not!
Le 30/04/2014
asterisk-users@lists.digium.com
Subject: Re: [asterisk-users] Reload problems with 1.8.27 and 11.9.0 -
Someone else ?
Please, people from Digium, Matt again closed the new bug ASTERISK-23689
I opened (clone from 23683) telling that it's not a bug. Did he
carefully read the comments on the new
On Wed, Apr 30, 2014 at 8:13 AM, Administrator TOOTAI ad...@tootai.netwrote:
Please, people from Digium, Matt again closed the new bug ASTERISK-23689 I
opened (clone from 23683) telling that it's not a bug. Did he carefully
read the comments on the new bug? If not, please forward him this
Le 30/04/2014 15:19, Matthew Jordan a écrit :
On Wed, Apr 30, 2014 at 8:13 AM, Administrator TOOTAI
ad...@tootai.net mailto:ad...@tootai.net wrote:
Please, people from Digium, Matt again closed the new bug
ASTERISK-23689 I opened (clone from 23683) telling that it's not a
bug.
26 matches
Mail list logo
