similar to: Why is CDR(recordingfile) not being written to the database despite being set in the dialplan?

El 07/04/15 a las 17:38, Alex Villac??s Lasso escribi?: > I am trying to collect enough information about an problem a client is having with its asterisk 11.17.0 x86_64. This issue was observed before in 1.8.20, and we upgraded to 11.15.0 and then to 11.17.0 with no solution. > > Background: this client is a telemarketing call-center that generates outgoing calls with close to a hundred

On Tue, Nov 06, 2018 at 05:24:15PM +0100, Thierry Reding wrote: > From: Thierry Reding <treding at nvidia.com> > > Irrespective of whether or not the device has any usable outputs, the > modesetting helpers will try to register all the resources such as CRTCs > and planes. Unfortunately, the helpers rely on drm_mode_config_init() to > properly set up internal data

Have you tried Asterisk 13? The bridging mechanism has been completely rewritten on Asterisk 12, so there's no longer channel masquerading and zombie channels. Might be worth a try. 2015-04-07 20:33 GMT-03:00 Alex Villac??s Lasso <a_villacis at palosanto.com>: > El 07/04/15 a las 17:38, Alex Villac??s Lasso escribi?: > > I am trying to collect enough information about an

I am trying to record calls on demand both inbound and outbound calls. I can record outbound calls just fine but not inbound calls or calls from an internally between extensions. I am using the latest asterisk 1.8.x certified version. On an outbound call I see: == Using SIP RTP CoS mark 5 -- Called SIP/ BVTrunk /7190000000 -- SIP/BVTrunk-00000163 is making progress passing it to

On Sat, Dec 08, 2018 at 02:54:45PM +0000, Marcel Ziswiler wrote: > Hi Thierry et al. > > I noticed that since commit 3dde5a2342cd ("ARM: tegra: Add VIC on > Tegra124") graphics on Apalis TK1 is broken. During boot it fails > loading the vic firmware: > > [ 1.595824] tegra-vic 54340000.vic: Direct firmware load for > nvidia/tegra124/vic03_ucode.bin failed with

From: Thierry Reding <treding at nvidia.com> Irrespective of whether or not the device has any usable outputs, the modesetting helpers will try to register all the resources such as CRTCs and planes. Unfortunately, the helpers rely on drm_mode_config_init() to properly set up internal data structures. Since the Tegra GPU does not have a display engine, the Nouveau driver doesn't set

I am trying to collect enough information about an problem a client is having with its asterisk 11.17.0 x86_64. This issue was observed before in 1.8.20, and we upgraded to 11.15.0 and then to 11.17.0 with no solution. Background: this client is a telemarketing call-center that generates outgoing calls with close to a hundred agents operating simultaneously in peak hours. The system uses

On Mon, Dec 10, 2018 at 03:20:19PM +0000, Marcel Ziswiler wrote: > Hi Thierry > > On Mon, 2018-12-10 at 12:00 +0100, Thierry Reding wrote: > > On Mon, Dec 10, 2018 at 11:21:47AM +0100, Thierry Reding wrote: > > > On Sat, Dec 08, 2018 at 02:54:45PM +0000, Marcel Ziswiler wrote: > > > > Hi Thierry et al. > > > > > > > > I noticed that

Hi Thierry On Mon, 2018-12-10 at 12:00 +0100, Thierry Reding wrote: > On Mon, Dec 10, 2018 at 11:21:47AM +0100, Thierry Reding wrote: > > On Sat, Dec 08, 2018 at 02:54:45PM +0000, Marcel Ziswiler wrote: > > > Hi Thierry et al. > > > > > > I noticed that since commit 3dde5a2342cd ("ARM: tegra: Add VIC on > > > Tegra124") graphics on Apalis

Hi Thierry et al. I noticed that since commit 3dde5a2342cd ("ARM: tegra: Add VIC on Tegra124") graphics on Apalis TK1 is broken. During boot it fails loading the vic firmware: [ 1.595824] tegra-vic 54340000.vic: Direct firmware load for nvidia/tegra124/vic03_ucode.bin failed with error -2 [ 1.606140] tegra-vic: probe of 54340000.vic failed with error -2 Subsequently Tegra HDMI

On Mon, Dec 10, 2018 at 11:21:47AM +0100, Thierry Reding wrote: > On Sat, Dec 08, 2018 at 02:54:45PM +0000, Marcel Ziswiler wrote: > > Hi Thierry et al. > > > > I noticed that since commit 3dde5a2342cd ("ARM: tegra: Add VIC on > > Tegra124") graphics on Apalis TK1 is broken. During boot it fails > > loading the vic firmware: > > > > [

hi, Am Mittwoch, den 27.04.2011, 12:37 +0300 schrieb Timo Sirainen: > Give "bt full" command here and show the output. lot of lines :-) ============================ (gdb) bt full #0 0xfeb559f8 in strcmp () from /lib/libc.so.1 No symbol table info available. #1 0xfee73e7a in settings_find_key_nth (ctx=0x809bec0, key=0x807ab38 "plugin//imap", n=0x80477f0,

I have two servers, each connected to the PTSN via PRI. When I call from site A (951-999-9999) to site B (555-1212) and the phone at site B is on the phone, I hear the normal ring tone for about 20 seconds, then the message "all circuits are busy now. please try your call again latter" followed by the congestion tone. Instead, I want this to busy ring and then hang up without any

Good afternoon list. I am experiencing a problem with the CDR and callfiles. What is happening is this: When generating a call with a callfile, everything works perfectly, but the CDR is recorded in the table when they answer the call destination. The field disposition is being recorded correctly, but the duration field is marked with the ring time and billsec is marked with 0. This just happens

The Asterisk Development Team would like to announce the release of Asterisk 15.1.0. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk The release of Asterisk 15.1.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:

The Asterisk Development Team would like to announce the release of Asterisk 14.7.0. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk The release of Asterisk 14.7.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:

The Asterisk Development Team would like to announce the release of Asterisk 13.18.0. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk The release of Asterisk 13.18.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:

hello list i have an issue related to outbound calls i can contact all the number except on number given by our provider in trunk the issue just when i configure my trunk in our server but when i configure the trunk directly in x-lite i can contact this number without issue below the cli == Using SIP RTP TOS bits 184 == Using SIP RTP CoS mark 5 -- Executing [0149xxxxxx at

Hi, I'm trying to register SIP phone with an asterisk serve, failing miserably. The server is sending "401 Unauthorized" responses to the registration attempts, but every time the phone is re-REGISTERing without authorization. I'd think this was a problem with the IP phone, except... the very same phone registers correctly (authenticated) with another asterisk box, same brand,

Still no luck using asterisk as a proxy. 48 hours solid working on this. I'm beginning to think asterisk isn't going to be compatible with the provider I'm using :( Has anyone got *any* clues as to what can cause this message? It's definately provider specific (voiptalk works, pipecall doesn't) but confusingly seems to be caused by something in the client phone app. I