similar to: CDR dst value null after attended transfer

Please help find the cause of strange behavior res_pjsip. Making outgoint call to other sip server (CommuniGatePro), my asterisk suddenly sends BYE after picking up! Partial log of an outgoing call with full debug is attached and on web: http://pastebin.com/tLNCpx4d No diagnostic messages why asterisk suddenly decided to hangup i don't found :( There are suggestions or strong belief

Hi, I hope someone can help me with this.... Asterisk 1.0.6 Zaptel 1.0.6 Libpri 1.0.6, 1 Digium E100P card installed Panasonic TDA200 firmware v2.0.6 E1 Card Firmware 1.0.2 System is located in Australia, so as technologies go, I believe it is twist on the euro standard for the E1 signalling. Here is the situation. The TDA E1 card is set in cross over mode and I am using a functional

Hi folks, this does look like a bug to me: Asterisk replaces the @63.214.186.6 by @context which obviously leads to a failure. Any comments, do I have a configuration issue on my side that I missed? Cheers, Philipp -- Executing Dial("SIP/philipp-bd5f", "SIP/992365264680@nikotel- out|90") in new stack -- Called 99xxxxxxxxxx@nikotel-out -- Got SIP response 302

Hi, I happened to meet with a similar issue like https://bugs.centos.org/view.php?id=7051 I found the root cause might be fixed by commit f13d4f979c518119bba5439dd2364d76d31dcd3f. The commit in branch linux-2.6.32-y is 0bd9ac380a44611e953b1657d7f54075b2f77fb0 This issue is existed in centOS 6.6 also any ideas B.R. Justin

When I mount linux/windows samba shares with smbmount (command line or with komba2) I have this kind of error : [thomas@Daemon / ]$ cd Dance\ \&\ Techno [thomas@Daemon Dance & Techno]$ ls Unable to handle kernel paging request at virtual address cbff0000 *pde = 00031063 *pte = 00000000 Oops: 0000 CPU: 0 EIP: 0010:[<cc9f9c34>] Tainted: P EFLAGS: 00010246 eax: 00000000

Hi all, for the upgrade I followed this procedure: * put node in maintenance mode (ensure no client are active) * yum versionlock delete glusterfs* * service glusterd stop * yum update * systemctl daemon-reload * service glusterd start * yum versionlock add glusterfs* * gluster volume heal vm-images-repo full * gluster volume heal vm-images-repo info on each server every time

Hi, We have 5 Samba domain controllers, and 4 file servers. All are 4.2.10-Debian. Our file servers have been working fine until recently (on the 26th), when suddenly access to the \\users.store.example.com\user share (hostname p-cats) became extremely slow. Access to other shares on other machines is fine, and users is 128G total (smaller than other shares). The machine isn't under

Hi, I happened to meet with a similar issue like https://bugs.centos.org/view.php?id=7051 I found the root cause might be fixed by commit f13d4f979c518119bba5439dd2364d76d31dcd3f. The commit in branch linux-2.6.32-y is 0bd9ac380a44611e953b1657d7f54075b2f77fb0 This issue is existed in centOS 6.6 also any ideas

Dear helpeRs, I am looking for an R equivalent of the S function "randomize" but cannot find it anywhere (?randomize, help.search("randomize")). There are some references to "Randomize()" in the list archives, but it is not on my system (R 2.1.1 on Windows XP)... what package is it in? Thanks! Luis -- Luis Tercero, M.Sc. Engler-Bunte-Institut der

On 06/29/2017 01:08 PM, Paolo Margara wrote: > > Hi all, > > for the upgrade I followed this procedure: > > * put node in maintenance mode (ensure no client are active) > * yum versionlock delete glusterfs* > * service glusterd stop > * yum update > * systemctl daemon-reload > * service glusterd start > * yum versionlock add glusterfs* > *

Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-9+deb8u1 Severity: critical Justification: breaks the whole system Dear Maintainer, -- System Information: Debian Release: 8.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8,

I have a small site running Samba 2.2.8a from SuSE and I started wonder about the "stability" of Samba running with W2K clients, when I installed W2k on a machine that previous ran Win.98 without any problems. After the W2K installation's had been finished (with all security fixes, new drivers etc.) I noticed that when accessing shares on the samba server, Samba began generating

As part of our deployment of FC updates we have upgraded our office server from 3.0.24-3 to 3.0.24.4. We got some strange results. Shares that have the same name as the users home directory and/or the same name as their users id became inaccessible. For example, my user id is kens, my home directory is in /home/kens and there was a share of it called kens. There is also a common share

On Wed, Jun 28, 2017 at 9:45 PM, Ravishankar N <ravishankar at redhat.com> wrote: > On 06/28/2017 06:52 PM, Paolo Margara wrote: > >> Hi list, >> >> yesterday I noted the following lines into the glustershd.log log file: >> >> [2017-06-28 11:53:05.000890] W [MSGID: 108034] >> [afr-self-heald.c:479:afr_shd_index_sweep] >>

Hello when using Asterisk version 13.12.2 I notice that it takes up to 30 seconds (sometimes even longer) for a call queue to call its members. Example 1 : [Nov 21 08:17:57] pbx.c: Executing [queue at pbx-routing:15] Queue("SIP/incoming-00000246", "myqueue1,,,,300,,,") in new stack [Nov 21 08:17:57] res_musiconhold.c: Started music on hold, class 'default', on

On 21-11-16 15:17, Matthew Jordan wrote: > > On Mon, Nov 21, 2016 at 7:05 AM, Jonas Kellens > <jonas.kellens at telenet.be <mailto:jonas.kellens at telenet.be>> wrote: > > Hello > > when using Asterisk version 13.12.2 I notice that it takes up to > 30 seconds (sometimes even longer) for a call queue to call its > members. > >

The profile seems to suggest very high latencies on the brick at ovirt1.nwfiber.com:/gluster/brick1/engine ovirt2.* shows decent numbers. Is everything OK with the brick on ovirt1? Are the bricks of engine volume on both these servers identical in terms of their config? -Krutika On Wed, May 30, 2018 at 3:07 PM, Jim Kusznir <jim at palousetech.com> wrote: > Hi: > > Thank you. I

Paolo, Which document did you follow for the upgrade? We can fix the documentation if there are any issues. On Thu, Jun 29, 2017 at 2:07 PM, Ravishankar N <ravishankar at redhat.com> wrote: > On 06/29/2017 01:08 PM, Paolo Margara wrote: > > Hi all, > > for the upgrade I followed this procedure: > > - put node in maintenance mode (ensure no client are active)

Hi all again: I'm now subscribed to gluster-users as well, so I should get any replies from that side too. At this point, I am seeing acceptable (although slower than I expect) performance much of the time, with periodic massive spikes in latency (occasionally so bad as to cause ovirt to detect a engine bad health status). Often, if I check the logs just then, I'll see those call traces

I've been back at it, and still am unable to get more than one of my physical nodes to come online in ovirt, nor am I able to get more than the two gluster volumes (storage domains) to show online within ovirt. In Storage -> Volumes, they all show offline (many with one brick down, which is correct: I have one server off) However, in Storage -> domains, they all show down (although