On Tue, Jul 17, 2012 at 11:09 PM, Todd Hodgen wrote:
> It's not a bad idea. Many voicemails will have a default of or
> or
> something similar. I have a default that I apply to all installations when
> I import my file just so there is something there that I can convey to
> everyone e
That may need to be greater than or equal to ( >= ) instead of just greater
than, it's 1:30 and there's not much call volume at the moment. :)
From: sipx-users-boun...@list.sipfoundry.org
[mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of m...@mattkeys.net
Sent: Wednesday, July 18, 201
#!/bin/sh
today=$(date +%Y-%m-%d)
email="b...@example.com"
subject="Abandoned calls for $today"
# insert a header line into the csv.
/bin/echo "FROM,TO,START_TIME,END_TIME" > /tmp/abandoned.csv
/usr/bin/psql -At -F ',' SIPXCDR -U postgres -c "SELECT * FROM view_cdrs WHERE
failure_status = '487' a
Thanks for the lead Nathaniel. I found some older documentation on how to do it
using psql here : http://wiki.sipfoundry.org/display/~rgdans/CDR+Extras . The
example command, "psql -At -F "," SIPXCDR -U postgres -c "select * from
view_cdrs", seems to work for what I need. I can work with this da
Matt - we are accessing the cdr database via an odbc connection in windows - a
scheduled task launches an access app that exports the prior days data to a csv
for input into our billing software - it's a bit bloated, but works well
enough. This will need re-worked if/when cdrs are ported to mon
Is there a way to dump all CDRs via the CLI? Specifically I'm looking to write
a script and cronjob it for 23:59 to dump all abandoned calls for the day as
CSV and email them to someone. I consulted the wiki
(http://wiki.sipfoundry.org/display/sipXecs/Call+Detail+Records+Web+Service)
but it onl
On Jul 17, 2012, at 18:44 , Kurt Albershardt wrote:
> While sipXproxy.log (which appears to use UCT rather than localtime) has:
> "2012-07-18T00:35:02.725196Z":482:SIP:WARNING:sipx.murray-hotel.com:SipRouter-15:41C15940:SipXProxy:"SipTransaction::recurseDnsSrvChildren
> no valid DNS records found
On Jul 15, 2012, at 3:08 , Tony Graziano wrote:
> I'd suggest putting the proxy and registrar log levels to debug and
> inspecting them when you try to register.
>
Debug was pretty noisy last time I tried it, so I started with setting both at
info.
sipregistrar.log had no events generated cor
On the fresh 4.6 install I just started up, the System / Date and Time menu
still produces:
An internal error has occurred. Click here to continue.
The ntp package is installed on the system, but ntpd will not start due to the
OpenVZ restrictions I mentioned a few days back.
_
4.6 install was done on a clean OS build and only ran the setup script once. I
answered questions with sipx.domain.com only, other than the main domain.
Just re-ran the setup script on a clean install of today's package release and
it only created one (sipx.domain.com) zonefile.
On Jul 17, 20
Just an FYI -- after installing today's package updates on a 4.6 system which
has NTP configured as an unmanaged service, I get:
Running rpm_check_debug
ERROR with rpm_check_debug vs depsolve:
ntp is needed by sipxsupervisor-4.6.0-104.g90aeb.x86_64
** Found 1 pre-existing rpmdb problem(s), 'yum c
On Jul 17, 2012, at 14:17 , Kurt Albershardt wrote:
> On Jul 14, 2012, at 11:22 , Kurt Albershardt wrote:
>
>> On Jul 13, 2012, at 19:53 , Tony Graziano wrote:
>>
>>> ensure you have the repo pointed to the correct location and do an
>>> update to make sure you have the latest.
>>
>> Ran an up
if the default sipdomain is: sipx.domain.com then there should be no
zone file for "domain.com". Normally you would create a forward zone
for "domain.com" and point it to its authoritative server.
On Tue, Jul 17, 2012 at 4:13 PM, Kurt Albershardt wrote:
> On Jul 15, 2012, at 17:06 , Tony Graziano
On Jul 14, 2012, at 11:22 , Kurt Albershardt wrote:
> On Jul 13, 2012, at 19:53 , Tony Graziano wrote:
>
>> ensure you have the repo pointed to the correct location and do an
>> update to make sure you have the latest.
>
> Ran an update yesterday PM and got nothing new - has the repo location
>
On Jul 15, 2012, at 17:06 , Tony Graziano wrote:
> I would install sipx as a subdomain (I.e. uc.sipdomain.TLD). I would point
> the firewall DNS forwarder for both the host and subdomain to sipx and let
> sipx run its own DNS.
>
Working towards that now, and I have been using sipx.domain.com as
It's not a bad idea. Many voicemails will have a default of or or
something similar. I have a default that I apply to all installations when
I import my file just so there is something there that I can convey to
everyone easily during training.
-Original Message-
From: sipx-u
funny you say that, i saw that and I don't think it was intentional.
if another developer doesn't respond tomorrow i'll investigate.
On Tue, Jul 17, 2012 at 3:42 PM, Todd Hodgen wrote:
> In 4.6, installation provides a default pin, and password for xmpp. Anyone
> know what those defaults are.
In 4.6, installation provides a default pin, and password for xmpp. Anyone
know what those defaults are. I'm thinking a nice Jira would be an option
to set what the default is for new users. Any thoughts?
___
sipx-users mailing list
sipx-users@list
18 matches
Mail list logo
