on PostgreSQL speed with btree index so 1
> should be no problem.
>
> No idea how sipxconfig will handle it :( But You can provision our ACD via
> SQL directly without any need of reloading/restarting.
>
> Pawel,
>
> On 2010-01-18, at 22:16, James R wrote:
>
> On Mo
On Mon, Jan 18, 2010 at 4:12 PM, Scott Lawrence wrote:
>
> Not even close.
>
> The limit is in the tens of agents - you're off by a few orders of
> magnitude.
>
>
Agent Limitation I'm aware of.. and that I understand... I'm interested in
the "Line" limitation.
___
On Mon, Jan 18, 2010 at 3:26 PM, Josh Patten wrote:
> Something tells me the current ACD engine would die on you if you did that
> to it. I don't even know that the ACD engine that will be released in 5.0
> would be able to handle that kind of load. I'll let the developers chime in
> on this one.
Has anyone built a large number of lines on the ACD with success? I'm
talking like more than a thousand.. upwards of 10,000.
If this has been done before, what is the performance / resource impact? is
it mainly memory or CPU?
Also does anyone see any problems populating this data via postress/
On Thu, Oct 1, 2009 at 3:13 PM, Daniel Yu wrote:
> I followed your instruction, here is what I experience. It works for the
> first call, after it, it stopped working again, unless I repeat the whole
> step. Very frustrated with the queue..:<
>
One additional step you can try... while the agent
When you are experiencing the problem, can you click on FEATURES --> CALL
CENTER -->click on your ACD --> then select Agent Statistics
If your agent doesn't show up in that list then you are probably hitting
this bug:
http://track.sipfoundry.org/browse/XX-4869
We have this problem pretty ofte
I'm using Pawel's ACD wallboard, and now that more people here are looking
at the board we are getting more questions about it.
is the following correct?
AWT - average wait time = greeting .wav audio + in queue time
AAT - average answer time = in queue time (clock starts right after
greeting f
On Wed, Sep 30, 2009 at 1:40 PM, Dale Worley wrote:
>
> They result from a process that crashed, as you know. Sometimes
> processes crash when sipXecs is shut down, which isn't so important.
> But all other crashes are bugs that we'd like to see eliminated. So if
> these don't correlate with re
On Tue, Sep 29, 2009 at 11:49 PM, Tony Graziano <
tgrazi...@myitdepartment.net> wrote:
> Ah. details. Thanks. Running ACD server? Are you making changes to the ACD
> system? Is the agent on the same local segment as the acd server?
>
Yes we running the ACD server... we are only using sipX for it
Hello all,
I've been spending most of my days looking through the log files in
/var/log/sipxpbx and usually I end up having more questions than I get
answers. Are there any developer guides, documentation, details etc on the
log files?
We're having some one-way audio issues, and I'm wondering if
Our agents pass through a box that has 2 physical Ethernet interfaces before
getting to sipX. 1 DMZ and 1 inside interface. When a sip Registration
shows up at sipX, the registration looks like this:
The 192.168. address is the DMZ address. the 10.103. address is the inside
LAN address.
When
is there any chance someone can point me to the 4.0.0 64-bit CentOS ISO
download? I need to quickly build 2 test servers 64-bit, and I can't find
my original ISO that I used before. (I downloaded it before they were taken
off of the download page). I had great success with that ISO, and I will
be
on the 2950 we only have a few VM's.. sipX with some windows 2003 servers.
Our plan is to add additional ACD servers in the sipX cluster (once we get
that working). We do have a large Dell R900 where I have about 15 VM's
running with multiple sipX servers, Windows servers, linux servers etc.. I
sipX virtualized is working well for us right now. We initially used it for
lab testing, but we are now doing a production trial in a virtualized
configuration. We are using good hardware (Dell 2950 with 32 GB RAM, 2 quad
core processors etc..). I can't speak to the NAT issue since we are not a
Scott Lawrence nortel.com> writes:
> This is a limitation of the ACD - it does not support transferring the
> call out (either to internal or to external destinations).
>
> Even aside from this limitation, few ITSPs support REFER the way you'd
> want it to work - at the very least your SBC will
> Take a look at Gateway.java. There is a switch for this behavior.
> Enable that switch (make the boolean true). Recompile the source code,
> replace sipxbridge.jar in your install and see if it works for you.
> Let us know how it goes.
>
> Regards
>
> Ranga
> --
> M. Ranganathan
>
Actually to sa
> Take a look at Gateway.java. There is a switch for this behavior.
> Enable that switch (make the boolean true). Recompile the source code,
> replace sipxbridge.jar in your install and see if it works for you.
> Let us know how it goes.
>
> Regards
>
> Ranga
> --
> M. Ranganathan
>
Awesome! We a
We have a call flow where the agent needs to transfer the call back to
the PSTN. We have an agent application that sends the REFER to the
sipX server, but instead of the sipX server forwarding that REFER to
our SBC, it is generates an INVITE and sends it to our SBC.
The call completion works sinc
On Thu, May 7, 2009 at 4:56 PM, Charles wrote:
>
>
>
> I had the same issue using VMWare. I ended up creating my virtual disk in
> Parallels and then converting that disk to VMWare. I am uncertain why this
> issue would persist in one product and not the other. Eventually I had to
> reinstall
>On Wed, May 6, 2009 at 11:19 AM, Daniel Orcutt wrote:
> >Can anyone confirm Pawel’s statement? If I am unable to transfer calls
> to a >Queue, this would be detrimental for me.
>
We could not get this to work with 3.10. We are in the process of testing
this on 4.0. We need this feature as w
Damian Krzeminski nortel.com> writes:
>
> You set the number of ACDs that sipXconfig will let you to create in the
> cluster by adding the following line to sipxconfig.properties
>
> callCenterBundle.max=4
>
> But if you do that you have to use phones (and not WEB UI) to log in the
> agents.
>
I was really excited about the 4.x cluster idea... ... until I tried to
add my second ACD server (I got the error in the subject above). Is a
cluster really limited to one physical ACD server? I want to scale this
cluster beyond the agent capacity of one server.
Do I have to build multiple clu
library/rpm file by:
>
> yum install sipxcommons
>
> Once that has installed then go back to the other screen and complete the
> setup.
>
> Hope that helps
>
>
>
> Cheers
>
> Grant
>
>
>
>
>
>
>
> *From:* sipx-users-boun...@list.sipfoun
Scott Lawrence nortel.com> writes:
>
> Possibly you're hitting the problem Grant described, which we're working
> on, but more importantly - if you want to try 4.0, load 4.0 - NOT 4.1
> (that is the development branch that will eventually lead to 4.2; even
> numbers in the second place are stabl
David Saint nortel.com> writes:
> Does your secondary server status show "Registered"?
>
> Also you will have to re-run sipxecs-setup on the secondary server
> if the certificates have been changed on the primary server.
>
> Dave.
>
I have the exact same problem except my secondary server is
anebi iguanait.com iguanait.com> writes:
>
> Ah yes, this explain the things. Provider's dns server are updating
> slowly and this explain the things.
>
> Dig returns this result in one of our server in germany:
>
> sipxecs.sipfoundry.org. 82616 IN A 216.142.118.34
I had the s
I have a successful 3.10.x system running and I want to get a feel for the
4.x system. I tried installing two different versions of 4.1 from the
ISO's, and everything seemed to be a success according to the build, but
when I try to reach the admin interface via the IP address, it converts my
URL t
27 matches
Mail list logo
