Re: [sipx-dev] Tandem call

Thanks Josh...I checked your scenario which is working fine... Regards, Kumaran T On 9/7/2012 11:29 AM, Josh Patten wrote: Kumaran, A tandem call is when 2 callers are bridged into a local phone conference, and then the phone that initiated the conference hangs up, but the 2 callers continue

Re: [sipx-dev] Tandem call

Kumaran, A tandem call is when 2 callers are bridged into a local phone conference, and then the phone that initiated the conference hangs up, but the 2 callers continue to have a conversation An example: 201 calls 220 202 calls 220 220 joins 201 and 202 into a local conference on the phone All

Re: [sipx-dev] FW: after 4.6 iso install, ant error from missing sipxcommons, then missing file/directory error

G Niculae, Sorry for getting back a little late. Actually, I was trying to use the ISO and then yum update because I was having problems getting OpenACD to run when I was installing from the nightly snapshot RPM Repository! Some erlang error along the lines of "cpx not defined" or something like

Re: [sipx-dev] homer capture still getting stuck capturing no records.

ok, thanks. On Thu, Sep 6, 2012 at 11:34 AM, Joegen Baclor wrote: > George, > > Here is the backtrace just in case you missed it > > #1 0x001e935b in SQLDriverConnect () from /usr/lib/libmyodbc5-5.1.5.so > #2 0x0809c129 in HEPDao::connect (this=0xb5b8, connection= > Traceback (most rece

Re: [sipx-dev] homer capture still getting stuck capturing no records.

George, Here is the backtrace just in case you missed it #1 0x001e935b in SQLDriverConnect () from /usr/lib/libmyodbc5-5.1.5.so #2 0x0809c129 in HEPDao::connect (this=0xb5b8, connection= Traceback (most recent call last): File "/usr/lib/../share/gdb/python/libstdcxx/v6/printers.py",

Re: [sipx-dev] homer capture still getting stuck capturing no records.

1. [root@pbx sipXecs]# gdb sipxhomer GNU gdb (GDB) Red Hat Enterprise Linux (7.2-56.el6) Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WA

Re: [sipx-dev] homer capture still getting stuck capturing no records.

I did. That was the entire output. On Thu, Sep 6, 2012 at 11:10 AM, George Niculae wrote: > On Thu, Sep 6, 2012 at 6:07 PM, Tony Graziano > wrote: >> it is, must have been in the wrong directory after all. sipxhomer is there. >> >> [Thread debugging using libthread_db enabled] >> >> sipxhomer ve

Re: [sipx-dev] homer capture still getting stuck capturing no records.

On Thu, Sep 6, 2012 at 6:07 PM, Tony Graziano wrote: > it is, must have been in the wrong directory after all. sipxhomer is there. > > [Thread debugging using libthread_db enabled] > > sipxhomer version 1.0 - All Rights Reserved. > > [New Thread 0xb7fe4b70 (LWP 17738)] > [Thread 0xb7fe4b70 (LWP 17

Re: [sipx-dev] homer capture still getting stuck capturing no records.

it is, must have been in the wrong directory after all. sipxhomer is there. [Thread debugging using libthread_db enabled] sipxhomer version 1.0 - All Rights Reserved. [New Thread 0xb7fe4b70 (LWP 17738)] [Thread 0xb7fe4b70 (LWP 17738) exited] Program received signal SIGSEGV, Segmentation fault.

Re: [sipx-dev] homer capture still getting stuck capturing no records.

On Thu, Sep 6, 2012 at 5:58 PM, George Niculae wrote: > On Thu, Sep 6, 2012 at 5:50 PM, Tony Graziano > wrote: >> this is my input in gdb: >> >> run --log-file /var/log/sipxpbx/sipxhomer.log --config-file >> /etc/sipxpbx/sipxhomer.ini --pid-file /var/run/sipxpbx/sipxhomer.pid >> --exec-file /usr/

Re: [sipx-dev] homer capture still getting stuck capturing no records.

On Thu, Sep 6, 2012 at 5:50 PM, Tony Graziano wrote: > this is my input in gdb: > > run --log-file /var/log/sipxpbx/sipxhomer.log --config-file > /etc/sipxpbx/sipxhomer.ini --pid-file /var/run/sipxpbx/sipxhomer.pid > --exec-file /usr/libexec/sipXecs/sipxhomer > > *** > (gdb) run --log-file /var/lo

Re: [sipx-dev] homer capture still getting stuck capturing no records.

this is my input in gdb: run --log-file /var/log/sipxpbx/sipxhomer.log --config-file /etc/sipxpbx/sipxhomer.ini --pid-file /var/run/sipxpbx/sipxhomer.pid --exec-file /usr/libexec/sipXecs/sipxhomer *** (gdb) run --log-file /var/log/sipxpbx/sipxhomer.log --config-file /etc/sipxpbx/sipxhomer.ini --p

Re: [sipx-dev] homer capture still getting stuck capturing no records.

On Thu, Sep 6, 2012 at 5:46 PM, Tony Graziano wrote: > -This is the 3rd install on 32 bit, they all broke. It broke last > month after an update. > > Having problems getting backtrace. PID file is there (exists but dead). > > I think the command is missing the executable argument. > > run --log-fi

Re: [sipx-dev] homer capture still getting stuck capturing no records.

-This is the 3rd install on 32 bit, they all broke. It broke last month after an update. Having problems getting backtrace. PID file is there (exists but dead). I think the command is missing the executable argument. run --log-file /var/log/sipxpbx/sipxhomer.log --config-file /etc/sipxpbx/sipxho

Re: [sipx-dev] homer capture still getting stuck capturing no records.

On Thu, Sep 6, 2012 at 5:24 PM, Tony Graziano wrote: > After enabling and renaming the CentOS-Debuginfo.repo to > CentOS-Debug.repo I was able to install glibc-debuginfo but cannot > install debuginfo-install, so I am stuck. I don't see > debuginfo-install rpm available. > Try just yum install si

Re: [sipx-dev] homer capture still getting stuck capturing no records.

Tony, Is this a confirmed behavior on 32 bits? You did try to install this on a second 32 bit machine and got the same behavior? Most developers are in 64 bit environment so I wont be surprised if there are some surprises with 32 bit boxes. A back trace as advised by George might bring us c

Re: [sipx-dev] homer capture still getting stuck capturing no records.

After enabling and renaming the CentOS-Debuginfo.repo to CentOS-Debug.repo I was able to install glibc-debuginfo but cannot install debuginfo-install, so I am stuck. I don't see debuginfo-install rpm available. On Thu, Sep 6, 2012 at 9:00 AM, George Niculae wrote: > On Thu, Sep 6, 2012 at 3:51 P

Re: [sipx-dev] homer capture still getting stuck capturing no records.

On Thu, Sep 6, 2012 at 3:51 PM, George Niculae wrote: > On Thu, Sep 6, 2012 at 3:48 PM, Tony Graziano > wrote: >> We still see this on 32 bit ISO installs with the latest updates: >> >> kernel: sipxhomer[633]: segfault at 10009 ip 07035bc6 sp bfdea274 >> error 4 in libc-2.12.so[6fb7000+18c000] >

Re: [sipx-dev] homer capture still getting stuck capturing no records.

On Thu, Sep 6, 2012 at 3:48 PM, Tony Graziano wrote: > We still see this on 32 bit ISO installs with the latest updates: > > kernel: sipxhomer[633]: segfault at 10009 ip 07035bc6 sp bfdea274 > error 4 in libc-2.12.so[6fb7000+18c000] > > sipxhomer is dead but pid exists. sipxhomer is unusable on 3

Re: [sipx-dev] homer capture still getting stuck capturing no records.

We still see this on 32 bit ISO installs with the latest updates: kernel: sipxhomer[633]: segfault at 10009 ip 07035bc6 sp bfdea274 error 4 in libc-2.12.so[6fb7000+18c000] sipxhomer is dead but pid exists. sipxhomer is unusable on 32 bit still. On Thu, Sep 6, 2012 at 8:21 AM, Joegen Baclor w

Re: [sipx-dev] homer capture still getting stuck capturing no records.

Just updating this thread. It was discovered that auto-reconnect feature of mysql odbc driver is not working and sipxhomer fails to recover a connection. This is one confirmed cause of sipxhomer suddenly stop feeding data to mysql. It is yet to be discovered if there are more issues we can un

[sipx-dev] Tandem call

Hi All, Can any please describe the tandem calls and how to check it? Regards, Kumaran T ___ sipx-dev mailing list sipx-dev@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-dev/

Re: [sipx-dev] Help with an enhancement to SipXCallController

Hi, I am glad to hear that there is interest in callcontroller functionally, and we do recognize that there is room for improvement. We do plan to improve it, and any feedback on callcontroller functionality is much appreciated. We do not have an exact schedule right now as when to make it better,