Is it reasonable to think that reports wouldn't run since the format of the
tables changed in a way that made the records unable to be parsed?
If so is this also happening is sibsequent versions?
Tony Graziano, Manager
Telephone: 434.984.8430
Fax: 434.984.8431
Email:
I mean cdr's prior to the date the update was performed (may 17), do not
exist in the cdrs db (viewing the raw data).
Where did they go? Is this normal?
Tony Graziano, Manager
Telephone: 434.984.8430
Fax: 434.984.8431
Email: tgrazi...@myitdepartment.net
LAN/Telephon
On Mon, Jun 21, 2010 at 5:22 PM, Tony Graziano
wrote:
> I did an update about 4 weeks ago to a 3.10.3 system, and brought it
> up to 4.0.4. I've noticed there are no CDR's in the database prior to
> the upgrade time.
Did you mean "prior" or "post"?
___
I figured out how to generate the digest authentication response, and
it turns out the 600v3 is using a blank password. Since the 600v3's
web interface doesn't display the password in plaintext I don't know
exactly where the problem lies. I'll try and see if Polycom knows
anything about it.
On Mo
I did an update about 4 weeks ago to a 3.10.3 system, and brought it
up to 4.0.4. I've noticed there are no CDR's in the database prior to
the upgrade time.
Is this intentional or is something else going on here?
--
==
Tony Graziano, Manager
Telephone: 434.984.8430
sip: tgraz
I would suspect if you can figure out how to get it to do static nat
outbound translations you might fix it...
From: sipx-users-boun...@list.sipfoundry.org
[mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Tim Byng
Sent: Monday, June 21, 2010 10:40 AM
To: Nathaniel Watkins
Cc:
Yes I did: Two different A records (not CNAMEs). I set a different
branch for each gateway and made sure the "shared" checkbox was not
checked. The way my system is currently set up is I have one main
"shared" Audiocodes mediant 1000 with a PRI connection to the outside
world. In the dial plan
From: sipx-users-boun...@list.sipfoundry.org
[sipx-users-boun...@list.sipfoundry.org] On Behalf Of Josh Patten
[jpat...@co.brazos.tx.us]
OK this didn't work. The hostname method simply causes sipX to see them
as the same gateway so a match on one gateway
OK this didn't work. The hostname method simply causes sipX to see them
as the same gateway so a match on one gateway will be a match on the other.
Anything else I can try?
Josh Patten
Assistant Network Administrator
Brazos County IT Dept.
(979) 361-4676
On 6/9/2010 4:08 PM, Tony Graziano wrot
there are probably several things. Why are you registering by the
hostname instead of sipdomain? Have you verified your sipx install by
running PFC? Can you register another phone (i.e. xlite) with the same
settings? Why, if the phone is local, is it registering via tcp
instead of udp (though it mi
The phone has been set to the user's password. I set it again to make
sure, but no change.
Is there nothing else it could be?
On Mon, Jun 21, 2010 at 10:24 AM, Tony Graziano
wrote:
> You need to change the sip password (not pin) to what the phone is
> using (or vice versa).
>
> Since the phone i
You need to change the sip password (not pin) to what the phone is
using (or vice versa).
Since the phone is manually configured, and it says "unauthorized", it
clearly is not sending the correct password. In the sipx user go to
the credentials screen and click "advanced" to see that sip password
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: 8bit
Organization: SipXecs Forum
In-Reply-To:
X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <48014>
Message-ID:
I'm seeing this problem with the 600v3 as well -
SipRegistrar's log says "SipNonceDB::isNonceValid nonce
signat
Thanks for the response Nathaniel. There are plans to switch to pfsense by
the end of the year. Until then, I was hoping I could get just the basics
working through ISA (if possible with ISA 2004). This is just a backup line
that hopefully we won't need to use. I'm OK if there are some limitations,
> Tony and All - Thanks for the quick and thorough reply. I
> read the Remote User config carefully and realize it might
> work for us - I had some misunderstanding about the pinholes
> before. It seems a good in-box option and easy to use. I will
> try it out in NAT environ. At this point, I a
Step through these errors, they are LINUX issues...
> /usr/bin/sipx-config: line 75: which: command not found
then
yum install which
I don;t think right now these are necessarily sipx issues, just linux
ones... read the output.
On Mon, Jun 21, 2010 at 8:35 AM, maybelater wrote:
> Thanks Tony
Thanks Tony,
after another fresh install ,
here ´s the result:
-bash-3.2# sipxecs-setup
Executing:
/sbin/service sipxecs start
ntpd is stopped
Starting ntpd: [ OK ]
/usr/bin/sipx-config: line 75: which: command not found
Version /usr/bin/sipx-conf
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: 8bit
Organization: SipXecs Forum
In-Reply-To: <4c1b8abe.40...@redhat.com>
X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <48000>
Message-ID:
The method you have described sets up a trunk between sipX
and CCM/CUCM, so the medi
18 matches
Mail list logo