Hi guys,
Google does not give me much additional info about this problem. Also i dont
really understand why this should be the problem of Postgres since the queries
are initiated by the CDR service?
Anyway, there are more errors. These:
ERROR: duplicate key violates unique constraint
Why don't you have headsets that use the electronic hook switch? Then the
user can just push a button on the headset to pickup the call...
On Wed, Jan 9, 2013 at 1:52 AM, Joegen Baclor jbac...@ezuce.com wrote:
Configure the polycom as an intercom and dial *76(number)
Elwin,
Did you try to re-index the database?
There's a trick to do this... in the search box in the upper right, just
enter some junk. On submit of the search a button will appear to re-index
the database.
Mike
On Wed, Jan 9, 2013 at 4:21 AM, Elwin Formsma e.form...@telecats.nl wrote:
Hi
On Wed, Jan 9, 2013 at 6:09 AM, Michael Picher mpic...@ezuce.com wrote:
Elwin,
Did you try to re-index the database?
There's a trick to do this... in the search box in the upper right, just
enter some junk. On submit of the search a button will appear to re-index
the database.
Mike, i
sorry, my bad... saw the errors about the duplicate key in the database.
On Wed, Jan 9, 2013 at 6:14 AM, Douglas Hubler dhub...@ezuce.com wrote:
On Wed, Jan 9, 2013 at 6:09 AM, Michael Picher mpic...@ezuce.com wrote:
Elwin,
Did you try to re-index the database?
There's a trick to do
Hi, Elwin
2 - Not that easy way. All the ruby that does the job are placed
in /usr/lib/ruby/gems/1.8/gems/sipxcallresolver-2.0.0/lib
I believe you can edit any of the scripts and simply sipxproc -r
CallResover to see your changes. Maybe the db/cdr_writer.rb can be of some
help.
In a quick and
Do you show any ongoing calls in CDR history (active calls)? Have
you restarted ONLY CDR service yet? There were issues with this in 4.4
and these were fixed but this was before patch #16. I think you might
be in store for an update. It would be helpful to know if these errors
show on successful
On Sat, Dec 29, 2012 at 9:13 PM, George Niculae geo...@ezuce.com wrote:
On Saturday, December 29, 2012, De Soca des...@smbdocs.com wrote:
Hello,
upgraded to 4.7 and it appears that Call Rate Limit functionality is not
accessible.
In 4.6 it was found under System - SIP Proxy _ Advanced
Example: Outside caller calls in to sipx. Call is answered by Bria 3.4.4 user.
Bria user performs a Call first (attended) transfer to sales person's cell
phone. This places the outside caller on hold and they hear hold music. The
Bria user speaks to the sales person and then chooses Transfer
Update:
Testing with the ITSP proved to be fairly uneventful from a lets break this to
get it fixed standpoint. All our tests with them worked flawlessly. I also
tested with an echo test line, 909393, and that worked as expected.
Unfortunately, the problem still exists but apparently only
Does this affect SIPXECS 4.4 or 4.6?
https://groups.google.com/forum/?fromgroups=#!topic/rubyonrails-security
/61bkgvnSGTQ
Multiple vulnerabilities in parameter parsing in Action Pack
There are multiple weaknesses in the parameter parsing code for Ruby on
Rails which allows attackers to
no
(rails was once a dep, but had a very short life in sipxecs)
On Wed, Jan 9, 2013 at 12:38 PM, Burleigh, Matt
matt.burle...@eiisolutions.net wrote:
Does this affect SIPXECS 4.4 or 4.6?
https://groups.google.com/forum/?fromgroups=#!topic/rubyonrails-security/61bkgvnSGTQ
Multiple
Hello,
Since it appears the feature to have the sipXbridge accept ITSP
signaling on port 5060 didn't make it in to this release, I am looking
in to setting up a Freeswitch SBC to handle the ITSP traffic. Since I
also require the remote worker functionality, would I then have to have
two
The short answer is, since FreeSWITCH is authoritative (A registrar by
itself), It will not pass through the registrations to sipx nor would it
passthrough challenge responses (401 and 407). This would limit you to
use FreeSWITCH only as a sip trunk (unmanaged) gateway.
On 01/10/2013 07:01
14 matches
Mail list logo
