At the moment, caller id has been working again and being inundated with work,
we've not had the chance to get back to this problem and even more difficult if
it's going to be random. The logging problem lead us down the path of trying to
figure out that, so that we could log so that we could tr
I think we had tried that, not sure now, I'll have to look at the notes. Got so
involved in troubleshooting why we aren't able to get the logs alone that we
got sidetracked. We need to get back to this test, just haven't been able to
yet.
Mike
On Mon, 14 Jun 2010 16:35:26 -0400, WORLEY, Dale
From: sipx-users-boun...@list.sipfoundry.org
[sipx-users-boun...@list.sipfoundry.org] On Behalf Of m...@grounded.net
[m...@grounded.net]
Searching in /var/log/sipxpbx for both words, in both cases and not finds
nothing. Only one result which is in the fr
>One possibility is that for some reason messages haven't been logged. IIRC,
>in version 4.0 you have to restart the affected
>components when you change their logging level. Search for the strings
>':INCOMING:" and ":OUTGOING:" in the sipXecs
>log files. If they are present, merge-logs should
From: sipx-users-boun...@list.sipfoundry.org
[sipx-users-boun...@list.sipfoundry.org] On Behalf Of m...@grounded.net
[m...@grounded.net]
Finally got back to this problem.
> logrotate -f /etc/logrotate.d/sipxchange
> open putty to /var/log/sipxpbx
> open
Is the list working again?
On Tue, 8 Jun 2010 01:05:54 -0500, m...@grounded.net wrote:
> Finally got back to this problem.
>
>> logrotate -f /etc/logrotate.d/sipxchange
>> open putty to /var/log/sipxpbx
>> open winscp to /var/log/sipxpbx
>> create a call that works
>> create a call that doesn't
Finally got back to this problem.
> logrotate -f /etc/logrotate.d/sipxchange
> open putty to /var/log/sipxpbx
> open winscp to /var/log/sipxpbx
> create a call that works
> create a call that doesn't work
> run merge-logs on putty
Every time I merge the logs, I get nothing much in the output file
On Tue, 11 May 2010 19:54:30 -0700, Todd Hodgen wrote:
> I think there have been a few people that struggled with that model in the
> past, you might want to look at the archives.
I've seen some of those posts and have also talked with many who say avoid the
phones. Thing is, we had them in use w
-boun...@list.sipfoundry.org
[mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of
m...@grounded.net
Sent: Tuesday, May 11, 2010 7:46 PM
To: sipx-users
Subject: Re: [sipx-users] Caller ID issue
Thanks Todd, this is great information. I was just looking for a 'ya, does
that for me too' or &#
.sipfoundry.org
> [mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of
> m...@grounded.net
> Sent: Tuesday, May 11, 2010 6:40 PM
> To: sipx-users
> Subject: [sipx-users] Caller ID issue
>
> Seem to have a problem with Caller ID setting but might be the phones
> thems
al Message-
From: sipx-users-boun...@list.sipfoundry.org
[mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of
m...@grounded.net
Sent: Tuesday, May 11, 2010 6:40 PM
To: sipx-users
Subject: [sipx-users] Caller ID issue
Seem to have a problem with Caller ID setting but might be the phones
Seem to have a problem with Caller ID setting but might be the phones
themselves.
X-lite client - works both with and without the Caller ID setting. Can hear
the dial tones and ringing on outbound calls on remotes.
Remote Linksys SPA-941 - caller ID setting with user's full phone number - wi
12 matches
Mail list logo
