21 jun 2006 kl. 18.02 skrev md:
Hello,
if you use redirect manager action while the channel is hanging up
Asterisk crash and the last log is Putting channel ... in channel.c.
Is there a solution for this?
ยด
If you find a bug, always visit the bug tracker to see if someone
else have
Hello,
a protocol T.38 in trunk version still doesn't work. I suppose that is
caused by wrong response to T.38's INVITE. Pleas check From and to
field in SIP Message Header in Status:200 from asterisk to gateway.
Regards
Darek
___
--Bandwidth and
On Wednesday 21 June 2006 15:42, Marc Blanchet wrote:
not sure if this is the really right place to discuss since it is
more a release engineering question, but I'll go:
to help people get the current official release of asterisk when
they download it without having to look at all releases
On Thu, Jun 22, 2006 at 09:19:17AM -0400, Andrew Kohlsmith wrote:
On Wednesday 21 June 2006 15:42, Marc Blanchet wrote:
not sure if this is the really right place to discuss since it is
more a release engineering question, but I'll go:
to help people get the current official release of
On Thursday 22 June 2006 10:10, Tzafrir Cohen wrote:
As it is a symlink to a tarball that is untarred to asterisk-1.2.9.1 ,
you have nothing to worry about.
If that's the case then I'm all for it!
-A.
___
--Bandwidth and Colocation provided by
Sorry to be responding to myself, but due to some comments on
#asterisk-dev regarding possible bad hardware, I replicated the setup on
another server with the same results.
Any feedback appreciated.
Thanks,
Dan
On Wed, 21 Jun 2006, Dan wrote:
If I boot asterisk, dial into a mailbox,
Julian Lyndon-Smith wrote:
Kevin,
Slow down - it was meant to be read with a smiley. It *is* impossible
to manually go through all possible combinations of parameters to make
sure that they all work.
In regards to the AddQueueMember, I simply forgot to add @context to
the end of the device
On 6/22/06, Thomas Kenyon [EMAIL PROTECTED] wrote:
In regards to the AddQueueMember, I simply forgot to add @context to
the end of the device name. I don't think that this should cause a
segfault. On the other hand, I wouldn't expect you to be testing for
BJ Weschke wrote:
You're reading this out of context. @context is required for Local/
interfaces specified in AddQueueMember. The segfault condition has
been corrected and you get a warning on the CLI now when you do
something that you should not.
When I hadn't done this (back on 1.2.5) It
