On Sun, Aug 1, 2010 at 12:01 AM, Norman Branitsky
wrote:
> It seems the openfire.jar is missing:
>> [r...@cssip1 ~]# md5sum /opt/openfire/lib/openfire.jar
>> md5sum: /opt/openfire/lib/openfire.jar: No such file or directory
Somehow this file disappeared. To force a reinstall of that one
package,
You might try Asterisk 1.8 beta to see if it fixes the issue. They've
fixed a lot of stuff from what I hear.
On 07/31/2010 10:29 PM, Rene Pankratz wrote:
That sounds really bad. Freeswitch has been my 2nd choice a gateway...
I really liked the idea of combining the interoperability of Asterisk
That sounds really bad. Freeswitch has been my 2nd choice a gateway...
I really liked the idea of combining the interoperability of Asterisk with
SIP-Providers with all those great features of sipX as local PBX.
René
2010/7/26 Josh Patten
> It's not an Asterisk configuration problem, it's an
On Sat, Jul 31, 2010 at 9:11 AM, Norman Branitsky
wrote:
> sipXecs installed from CentOS 5 ISO (32-bit) 1 month ago.
> Successful upgrade to 4.2.1 on Monday.
> Last night I saw the message saying an update was available.
> The release number was lower than what I was already running
> but the modu
On Sat, Jul 31, 2010 at 8:17 PM, Norman Branitsky
wrote:
> After the July 31 update and sipxcs restart to restore the Admin GUI,
> I find that Instant Messaging server won't start.
> /var/log/sipxpbx/openfire/error.log has messages like this for each of
> my users:
> Error storing offline presenc
On Sat, Jul 31, 2010 at 12:13 PM, Ali Nebi wrote:
> Yep, i will go this way. I thought that there is a fast way editing some
> property files.
I think we need to research a more flexible way to enable features in
openfire. Playing catchup with each feature one by one seems like a
silly way to ap
After the July 31 update and sipxcs restart to restore the Admin GUI,
I find that Instant Messaging server won't start.
/var/log/sipxpbx/openfire/error.log has messages like this for each of
my users:
Error storing offline presence of user: dennis
org.postgresql.util.PSQLException:
ERROR: duplicat
On 7/31/2010 9:11 AM, Norman Branitsky wrote:
Replying to my own message.
After July 31 update I got the following error:
>>
>>
>> HTTP ERROR: 500
>>
>> Unable to construct service sipxconfig.ExceptionPresenter:
>> Error building service sipxconfig.ExceptionPresenter:
>> Unable to convert type
Nope. The config files will be overwritten unless the template has it. If
tyou manually edit the template which will get overwritten with updates.
Additionally, wiring the chats to a database indicate extending the DB
schema, so really getting that done in sipxconfig as part of the way the
system m
Yep, i will go this way. I thought that there is a fast way editing some
property files.
On Sat, 2010-07-31 at 12:10 -0400, Tony Graziano wrote:
> Perhaps you can open a JIRA to expose that setting from sipxconfig?
>
> On Sat, Jul 31, 2010 at 12:07 PM, Ali Nebi wrote:
> Hi,
>
>
Perhaps you can open a JIRA to expose that setting from sipxconfig?
On Sat, Jul 31, 2010 at 12:07 PM, Ali Nebi wrote:
> Hi,
>
> we want to enable Chat Room logging in database (db table
> mucconversionlg) setting for all our chat rooms.
>
> Right now system saves the chat conversation in file, b
Hi,
we want to enable Chat Room logging in database (db table
mucconversionlg) setting for all our chat rooms.
Right now system saves the chat conversation in file, but we want to
have option to keep the conversations in chat room in database too. So
how can we do that?
I can enable this from op
sipXecs installed from CentOS 5 ISO (32-bit) 1 month ago.
Successful upgrade to 4.2.1 on Monday.
Last night I saw the message saying an update was available.
The release number was lower than what I was already running
but the modules all had suffixes that were one higher.
The update produced the
Matt,
The provider may very well be fine but maybe something in THEIR upstream
provider. I've seen this before with routing problems and they don't think
to look past their stuff.
The hard part is finding somebody at the provider who cares enough to really
dig in and find the problem.
Mike
On
I think the trick with the Aastras was to set the SIP port in them to '0'
and not 5060. This forces them to use SRV records.
I don't think a lot of work has been done on the configuration templates for
those phones so if you become proficient you may want to look to that that
up if their phone in
15 matches
Mail list logo
