Displaying 20 results from an estimated 6000 matches similar to: "asterisk crashed on segmentation fault"
2011 Jun 10
4
Connected Line ID
Hai,
Does anybody have problems with a wrong Connected Line ID with asterisk version 1.6
The following bug was for version 1.4, but I cannot make up if this bug is still in version 1.6
http://forums.digium.com/viewtopic.php?t=7780
In version 1.8 it is possible to change the Connected Line ID, but this isn't the case in version 1.6
Regards,
Arjan Kroon
Mobillion BV
2010 Feb 25
1
Getting: Can't fix up channel from 5 to 7 because 7 is already in use, and pri_dchannel: Answer requested on channel 0/7 not in use on span 1
System have been working great for weeks, using an average 40 of 120
dahdi channels.
But today, I suddenly see scary things like this:
-- Moving call from channel 5 to channel 7
[Feb 25 10:18:12] WARNING[17129]: chan_dahdi.c:10608
pri_fixup_principle: Can't fix up channel from 5 to 7 because 7 is
already in use
[Feb 25 10:18:12] WARNING[17129]: chan_dahdi.c:11535 pri_dchannel:
Ringing
2009 Sep 07
5
TE420P configuration
Hello
I am trying to configure TE420P but i am confused what to give chan_dahdi :(
Below is configuration i am using for TDM400P
Please help what changes to make in it... Please provide a link as well
[trunkgroups]
[channels]
;default for channels
switchtype=national
rxwink=300
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
2011 Mar 30
0
asterisk and COLP
Hi,
Does asterisk version 1.6.2.12 support COLP (COnnected Line Presentation)
Regards
Arjan Kroon
Mobillion BV
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20110330/937ec861/attachment.htm>
2012 Jan 04
1
Rami
Hi,
Does anybody know if RAMI (Ruby Ami) is still functional?
And is this still compatible with asterisk 1.8
Best Regards,
Arjan Kroon
Mobillion BV
2010 Dec 04
1
Error messages with chan_dahdi
HI, I'm using asterisk-1.4.24, dahdi-linux-complete-2.4.0+2.4.0 and
libpri-1.4.11.4
When dial, when 492131 answer, in console appear some error messages
-- AGI Script Executing Application: (DIAL) Options: (DAHDI/g1/492131|60)
-- Requested transfer capability: 0x00 - SPEECH
-- Called g1/492131
[Dec 4 11:15:59] WARNING[7669]: chan_dahdi.c:1776 dahdi_enable_ec: Unable
to enable
2006 Jun 05
0
Plugin Namespace Oddities?
Hi all,
I''m trying to throw together an acts_as_copyable, to add the ability to:
@new_ar_object = @ar_object.copy
I''m using the Fox example for the basic loading into AR with a module:
http://wiki.rubyonrails.org/rails/pages/HowToWriteAnActsAsFoxPlugin
so in my instance methods:
module InstanceMethods
def copy( options = {} )
copyable_attributes
2010 Dec 27
1
Asterisk 1.4.38 - unknown signalling bri_cpe
Hi,
we upgraded an Asterisk 1.4 with mISDN to 1.6 with chan_dahdi. Due to
problems with iax channel posted earlier, we wanted to switch back to
1.4 version.
Server has 2 HBA cards, everything is running fine with 1.6, bri_cpe is
recognized and the 7 euroISDN channels are running well, ingoing and
outgoing.
Now we installed 1.4.38 version and no more ISDN. In logs we found this:
[2010-12-24
2006 Jan 13
2
X-web Lite
Hello,
I'm using X-web lite in a webpage to connect to one of our asterisk
server.
But now I have a problem, when you are connected to a voice script the
voice will not be heard after a couple of seconds.
When you press or say something that the voice will come back for a
couple of seconds.
When I thy X-Lite (stand-alone version) I had the same problem, but when
I turned off the
2010 Nov 10
1
MFC/R2 detected as ISDN PRI
Hi list,
I'm trying to setup an asterisk 1.8.0 with MFC/R2, but I'm having these
error messages loading chan_dahdi:
> module load chan_dahdi.so
ERROR[9241]: chan_dahdi.c:11848 mkintf: Signalling requested on channel
1 is MFC/R2 but line is in ISDN PRI signalling
ERROR[9241]: chan_dahdi.c:16180 build_channels: Unable to register
channel '1-15'
I got the config in
2013 Nov 11
0
[LLVMdev] [cfe-dev] Goal for 3.5: Library-friendly headers
On Nov 11, 2013, at 9:56 AM, Alp Toker <alp at nuanti.com> wrote:
> Done :-)
>
> The patchset is 532K so I've put it online:
>
> http://www.nuanti.com/tmp/llvm-api-stability/
>
> The bulk edits are split out and noted. They were refactored with an internal tool, so it's not a big hassle to keep this up to date until 3.4 is out the door.
>
> A handful
2004 Aug 06
2
yp dir listing
On Sun, Aug 03, 2003 at 02:15:40PM +0100, Karl Heyes wrote:
> >
> > Any ideas if this is a problem with my xml config in ices or a limitation
> > of the program/server?
>
> Do you have the <yp>1</yp> tags in the instances you want listed? The
> default is not to have them listed.
>
whoa whoa whoa, since when?
We've been having a major problem with
2010 Oct 05
2
CDR record for call originated from CLI originate
hello List,
i am in a situation where i cannot get cdr records for call originated from
CLI , i am not able to get when i used application or extension.
is there any solution regarding this ,i working since last 3 days onto this.
regards
Dhaval
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2006 Feb 20
0
automatically start application from thecommandprompt
Thankx MC,
This is the solution.
I've tried it and it works perfect.
But I've got a question.
I want to set a variable with the command SetVar
I place the following text file in the directory
/var/spool/asterisk/outgoing/
Channel: Zap/g1/0655871460
MaxRetries: 0
RetryTime: 30
WaitTime: 30
Context: call_outbound
Extension: s
Priority: 1
SetVar: call_outbound_id=0
2010 Sep 29
1
Weird Behavior with DAHDI
Hello,
I'm experiencing some weird problems on my server:
- 1) The following messages are filling up my logs:
[Sep 29 08:24:59] WARNING[7077]: chan_dahdi.c:2789 pri_find_dchan: No
D-channels available! Using Primary channel 140 as D-channel anyway!
[Sep 29 08:24:59] WARNING[7078]: chan_dahdi.c:2789 pri_find_dchan: No
D-channels available! Using Primary channel 171 as D-channel anyway!
2004 Aug 06
0
yp dir listing
On Sun, 2003-08-03 at 17:14, Arc wrote:
> On Sun, Aug 03, 2003 at 02:15:40PM +0100, Karl Heyes wrote:
> > >
> > > Any ideas if this is a problem with my xml config in ices or a limitation
> > > of the program/server?
> >
> > Do you have the <yp>1</yp> tags in the instances you want listed? The
> > default is not to have them listed.
2020 Feb 04
0
Asterisk 13.31.0 Now Available
The Asterisk Development Team would like to announce the release of Asterisk 13.31.0.
This release is available for immediate download at
https://downloads.asterisk.org/pub/telephony/asterisk
The release of Asterisk 13.31.0 resolves several issues reported by the
community and would have not been possible without your participation.
Thank you!
The following issues are resolved in this release:
2020 Feb 04
0
Asterisk 13.31.0 Now Available
The Asterisk Development Team would like to announce the release of Asterisk 13.31.0.
This release is available for immediate download at
https://downloads.asterisk.org/pub/telephony/asterisk
The release of Asterisk 13.31.0 resolves several issues reported by the
community and would have not been possible without your participation.
Thank you!
The following issues are resolved in this release:
2020 Feb 04
0
Asterisk 17.2.0 Now Available
The Asterisk Development Team would like to announce the release of Asterisk 17.2.0.
This release is available for immediate download at
https://downloads.asterisk.org/pub/telephony/asterisk
The release of Asterisk 17.2.0 resolves several issues reported by the
community and would have not been possible without your participation.
Thank you!
The following issues are resolved in this release:
2020 Feb 04
0
Asterisk 16.8.0 Now Available
The Asterisk Development Team would like to announce the release of Asterisk 16.8.0.
This release is available for immediate download at
https://downloads.asterisk.org/pub/telephony/asterisk
The release of Asterisk 16.8.0 resolves several issues reported by the
community and would have not been possible without your participation.
Thank you!
The following issues are resolved in this release: