Sent: Thursday, October 04, 2012 4:39 PM
To: Discussion list for users of sipXecs software
Cc: darthzejdr
Subject: Re: [sipx-users] 4.6 Cluster
Finally I got the trace I need to provide you with an analysis
./Server1/sipregistrar.log-20121004:"2012-10-03T11:28:33.730099Z":367:INCOM
Can you please describe the steps to reproduce it...I will check in our
testing servers...
Regards,
Kumaran T
On 10/5/2012 11:56 AM, Todd Hodgen wrote:
> In my testing, it was during the playing of the mailbox message. Pressing
> the "*" should allow you to move to another voicemail box by ente
In my testing, it was during the playing of the mailbox message. Pressing
the "*" should allow you to move to another voicemail box by entering the
extension and password of an alternative box. In my scenario, it terminated
the call.
-Original Message-
From: sipx-users-boun...@list.sipfo
On 10/5/2012 4:21 AM, George Niculae wrote:
> On Thu, Oct 4, 2012 at 10:18 PM, George Niculae wrote:
>> On Thu, Oct 4, 2012 at 10:01 PM, Todd Hodgen wrote:
>>> Hi George, thanks for the comments. Not related to MWI.
>>>
>>> Scenario - from extension 701 - dialed 8750 to go directly to ext 750
64 bit RPM.
-Original Message-
From: sipx-users-boun...@list.sipfoundry.org
[mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of George Niculae
Sent: Thursday, October 04, 2012 3:51 PM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] 4.6 voicemail hangup
On Thu, Oct 4, 2012 at 6:51 PM, George Niculae wrote:
> On Thu, Oct 4, 2012 at 10:18 PM, George Niculae wrote:
> > On Thu, Oct 4, 2012 at 10:01 PM, Todd Hodgen
> wrote:
> >> Hi George, thanks for the comments. Not related to MWI.
> >>
> >> Scenario - from extension 701 - dialed 8750 to go
On Thu, Oct 4, 2012 at 10:18 PM, George Niculae wrote:
> On Thu, Oct 4, 2012 at 10:01 PM, Todd Hodgen wrote:
>> Hi George, thanks for the comments. Not related to MWI.
>>
>> Scenario - from extension 701 - dialed 8750 to go directly to ext 750
>> voicemail.
>> Voicemail answered prompting for
Not at this time...
On Thu, Oct 4, 2012 at 3:42 PM, Aaron Carlson wrote:
> Does OpenACD have any sort of functionality of this nature?
>
>
>
>
> On Thu, Oct 4, 2012 at 1:10 PM, Tony Graziano <
> tgrazi...@myitdepartment.net> wrote:
>
>> I don't know if it is still available...
>>
>> http://wiki.
Does OpenACD have any sort of functionality of this nature?
On Thu, Oct 4, 2012 at 1:10 PM, Tony Graziano
wrote:
> I don't know if it is still available...
>
> http://wiki.voiceworks.pl/display/vwost/sipXworks+example+queue+stats+screen
>
>
> On Thu, Oct 4, 2012 at 12:55 PM, Aaron Carlson wrote
With 4.6 though, we really recommend 4 GB of RAM otherwise you may run into
swapping issues...
Mike
On Thu, Oct 4, 2012 at 1:27 PM, Todd Hodgen wrote:
> I would suggest looking at the hardware as well. I run sipxecs 4.4 as a
> demo system on a laptop with smaller processor and 2gb memory witho
On Thu, Oct 4, 2012 at 10:01 PM, Todd Hodgen wrote:
> Hi George, thanks for the comments. Not related to MWI.
>
> Scenario - from extension 701 - dialed 8750 to go directly to ext 750
> voicemail.
> Voicemail answered prompting for password. I press * and call drops.
> 00:sipxivr:"depositV
Hi George, thanks for the comments. Not related to MWI.
Scenario - from extension 701 - dialed 8750 to go directly to ext 750
voicemail.
Voicemail answered prompting for password. I press * and call drops.
Relevant logs are below - full log attached.
Maybe I have to enter "*" as an option in
On Thu, Oct 4, 2012 at 8:16 PM, Todd Hodgen wrote:
> I was trying to get to my voicemail from another phone to test something and
> when I pressed *, rather than allowing me to enter my alternative extension
> and password it hung up on me. Using Polycom 550 and vvx500 same results.
>
>
>
> I’d
I would suggest looking at the hardware as well. I run sipxecs 4.4 as a
demo system on a laptop with smaller processor and 2gb memory without issue.
It is very stable, and I suspect your issue is more related to a hardware
issue.
Additionally, I have it running on at least a dozen machines wit
I was trying to get to my voicemail from another phone to test something and
when I pressed *, rather than allowing me to enter my alternative extension
and password it hung up on me. Using Polycom 550 and vvx500 same results.
I'd like to confirm if others see the same thing on 4.6?
What
I don't know if it is still available...
http://wiki.voiceworks.pl/display/vwost/sipXworks+example+queue+stats+screen
On Thu, Oct 4, 2012 at 12:55 PM, Aaron Carlson wrote:
> I'm using 4.4, just getting things set up, trying to transition away from
> our POTS system.
>
> That actually sounds like
I'm using 4.4, just getting things set up, trying to transition away from
our POTS system.
That actually sounds like what I'm looking for, I've tried checking the
wiki, but I can't locate it. Is there a list of third-party
plugins/software out there? Apologies for all the noob queries.
Aaron
On
I use those all the time. I think you should ensure that you shutdown
sipxecs and do a yum update and reboot the system. At the same time it
sounds like what you probably have is a hardware incompatbility with Centos
5.x.
http://bugs.centos.org/view.php?id=2141
It's really a Linux issue and not e
Hello Trevor,
Thank You for the tips. I have ran the memtest and a few stress tests. I
didn't check the MD5 sum before the first install, but I did check through
the install and didn't receive any errors. I've just done a few fresh
downloads and checked the MD5 sum and they have all mismatched.
You need to be more specific.
In 4.4 ACD there was a 3rd party integration that had a "status board" of
sorts.
In 4.6 it uses OpenACD, so this is a good question for OpenACD group too.
What version are you asking about?
On Thu, Oct 4, 2012 at 11:47 AM, Aaron Carlson wrote:
> Is there functiona
Is there functionality for realtime monitoring of agent statuses (ie,
people being on DND, on a call, inbound/outbound, that sort of thing)?
Aaron
___
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive
James,
These type of problems generally point to hardware issues or corrupted OS
install possibly exacerbated by sipXecs starting to load up memory into Java
and eat up CPU cycles. Did you happen to check the MD5 sum of the ISO before
burning or using it for installation? Did you take the t
Finally I got the trace I need to provide you with an analysis
./Server1/sipregistrar.log-20121004:"2012-10-03T11:28:33.730099Z":367:INCOMING:INFO:sipx1.callidus.local:SipClientTcp-31:7f1f8acf5700:SipRegistrar:"Read
SIP message:
Local Host:192.168.0.46 Port: 5060
Have you tried running the system through a couple passes of Memtest86+?
Generally speaking 4.4 is a stable product.
sipxecs will consume almost all your ram from the get go, and I have had
at least 3 instances where previously working machine would crash with
sipx. Memtest showed a faulty dimm.
ok, I still recommend 4.6, 64bit
On Thu, Oct 4, 2012 at 9:53 AM, James M. Jones wrote:
> Hello,
>
> ** **
>
> The system details are:
>
> ** **
>
> Computer: Dell Dimension C521
>
> Bios Version: 1.1.11
>
> ** **
>
> Processor: AMD Athlon 64 X2 Dual Core Processor 3600+, 1.9 GHZ,
Server1:
[root@sipx1 ~]# iptables -L -n
Chain INPUT (policy DROP)
target prot opt source destination
ACCEPT all -- 192.168.0.46 0.0.0.0/0
ACCEPT all -- 192.168.0.47 0.0.0.0/0
ACCEPT tcp -- 0.0.0.0/00.0.0.0/0 tcp dpt:80
state
Hello,
The system details are:
Computer: Dell Dimension C521
Bios Version: 1.1.11
Processor: AMD Athlon 64 X2 Dual Core Processor 3600+, 1.9 GHZ, Bus Speed
1000MHZ, L2 Cache 1MB, 64 Bit Technology=yes
RAM: 3GB DDR2 SDRAM (667MHZ)
Hard Drive: 80GB SATA
Thank You for the h
On Thu, Oct 4, 2012 at 4:05 PM, darthzejdr wrote:
> So, we've discovered the problem(and a partial solution). It works as it
> should only if we're both using udp.
>
> 200(Server2, TCP) -> 201(Server1, TCP) doesn't work
> 201(Server1, TCP) -> 200(Server2, TCP) doesn't work
>
> 200(Server2, UDP) ->
On Thu, Oct 4, 2012 at 9:19 AM, James M. Jones wrote:
> Good Day,
>
> ** **
>
> I’m currently working with version 4.4.4.0. I’ve installed it on an older
> Dell Dimension C521 with an AMD Athlon Processor (64X2 Dual Core, 1.9GHZ)
> and 3GB of RAM.
>
> ** **
>
> The installation works fin
Good Day,
I'm currently working with version 4.4.4.0. I've installed it on an older
Dell Dimension C521 with an AMD Athlon Processor (64X2 Dual Core, 1.9GHZ)
and 3GB of RAM.
The installation works fine and upon completion, I can access the GUI and
start the initial configuration, but short
So, we've discovered the problem(and a partial solution). It works as it
should only if we're both using udp.
200(Server2, TCP) -> 201(Server1, TCP) doesn't work
201(Server1, TCP) -> 200(Server2, TCP) doesn't work
200(Server2, UDP) -> 201(Server1, TCP) works
201(Server1, TCP) -> 200(Server2, UDP)
On Thu, Oct 4, 2012 at 2:20 PM, darthzejdr wrote:
> Unfortunately i don't understand those logs. Is there something wrong with
> my configuration? Or any ideas what to try next? I am doing yum update now
> so will do another try then and see if anything changed.
>
There is a problem with snapshot
Unfortunately i don't understand those logs. Is there something wrong with
my configuration? Or any ideas what to try next? I am doing yum update now
so will do another try then and see if anything changed.
-Original Message-
From: sipx-users-boun...@list.sipfoundry.org
[mailto:sipx-users-
Here's what happened to the bad call. Unforutenately, there is not
enough information in the proxy what happened to the call prior to
hitting IVR.
On 10/04/2012 04:53 PM, George Niculae wrote:
On Thu, Oct 4, 2012 at 11:47 AM, darthzejdr wrote:
"201"
2472
"200"
3407
This are the curren
On Thu, Oct 4, 2012 at 11:47 AM, darthzejdr wrote:
> "201"
> nonat> 2472
> "200"
> 3407
>
> This are the current registrations, but i'm not 100% sure it was the same
> since we're constantly testing and changing.
>
Could you please yum update, there are some changes we done lately in
this a
"201"
2472
"200"
3407
This are the current registrations, but i'm not 100% sure it was the same
since we're constantly testing and changing.
-Original Message-
From: sipx-users-boun...@list.sipfoundry.org
[mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of George Nicula
On Wed, Oct 3, 2012 at 9:59 AM, darthzejdr wrote:
> Slightly different situation today(the only change i did was to send
> profiles and turn on capture database)
>
>
>
> First call was from 201(primary server) to 200(secondary server), didn't
> work. Thats probably 201@192.168.0.46 to 200@192.168.
37 matches
Mail list logo
