On Mon, 2010-03-01 at 14:11 -0500, Michael Scheidell wrote:
> pwd
> /var/log/sipxpbx
> [r...@sip sipxpbx]# ls *.xml
> ls: *.xml: No such file or directory
>
>
You have to run merge-logs to make merged.xml
merge-logs is in the sipXecs /bin dir, if that's not already on your path, add
it.
Run it
On 3/1/10 2:19 PM, Tony Graziano wrote:
cd /var/log/sipxpbx
merge-logs
sipviewer merged.xml
You need to "merge-logs"
BINGO!
--
Michael Scheidell, CTO
Phone: 561-999-5000, x 1259
> *| *SECNAP Network Security Corporation
* Certified SNORT Integrator
* 2008-9 Hot Company Award Winner
cd /var/log/sipxpbx
merge-logs
sipviewer merged.xml
You need to "merge-logs"
which creates the xml file.
Don;t run sipviewer on the server since you can't, just grab the xml file,
then run sipviewer on the PC and open the merged.xml file.
On Mon, Mar 1, 2010 at 2:12 PM, Michael Scheidell wrot
stion if it was clearer what "this"
> is...
>
> If you have the merged.xml file, there is a Windows version of sipviewer
> available.
>
>
don't have one, it won't make one, not with sipx-trace
> You can get some information from:
> http://sipx-wiki.calivia.com/index.php/Backup_and_Diagnostics#
pwd
/var/log/sipxpbx
[r...@sip sipxpbx]# ls *.xml
ls: *.xml: No such file or directory
cd /var/log/sipxpbx
ls merged.xml
___
sipx-users mailing list sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscr
On Mon, 2010-03-01 at 13:41 -0500, Michael Scheidell wrote:
> how do you do this if you don't have X?
It would be easier to answer the question if it was clearer what "this"
is...
If you have the merged.xml file, there is a Windows version of sipviewer
available.
You can get some information fro
On Mon, Mar 1, 2010 at 2:06 PM, Michael Scheidell wrote:
> On 3/1/10 1:49 PM, Josh Patten wrote:
>
> sipviewer runs on windows too. Just get the merged.xml file via WinSCP.
>
> where does the merged.xml file live?
>
>
>
>
> --
> Michael Scheidell, CTO
> Phone: 561-999-5000, x 1259
> > *| *SECNAP
On 3/1/10 1:49 PM, Josh Patten wrote:
sipviewer runs on windows too. Just get the merged.xml file via WinSCP.
where does the merged.xml file live?
--
Michael Scheidell, CTO
Phone: 561-999-5000, x 1259
> *| *SECNAP Network Security Corporation
* Certified SNORT Integrator
* 2008-9 Hot C
might be a hint.. the handsets are not registered any more.
one cisco 7960 and one polycom 650
I suppose if the handset isn't registered, it won't be able to make or
receive calls :-)
timestamp on /var/log//sipregistrar.log seems to match with when it
stopped working.
--
Michael Scheidell,
Right. Create the merged.xml file, then take it to a windows PC and grab the
sipviewer installer package from the PC. Please run top and see if you have
any unusual CPU activuty before you reboot or restart services.
On Mon, Mar 1, 2010 at 1:49 PM, Josh Patten wrote:
> sipviewer runs on windows
sipviewer runs on windows too. Just get the merged.xml file via WinSCP.
Josh Patten
Assistant Network Administrator
Brazos County IT Dept.
(979) 361-4676
On 3/1/2010 12:41 PM, Michael Scheidell wrote:
how do you do this if you don't have X?
(I have a dead sipx. no inbound, no outbound, no err
how do you do this if you don't have X?
(I have a dead sipx. no inbound, no outbound, no errors, nothing
logged, just won't dial. won't even dial the VMail system anymore)
merging
Exception in thread "main" java.awt.HeadlessException:
No X11 DISPLAY variable was set, but this program performe
On Mon, 2010-03-01 at 08:42 -0500, Michael Scheidell wrote:
> no logs, no alarms, and a reboot from cli fixes it. where do I start
> diagnosing?
Take a sipx-trace of a call that fails. Determine from the trace the
component which is non-responding. Examine that component's log.
Dale
no logs, no alarms, and a reboot from cli fixes it. where do I start
diagnosing?
this started last week (no updates, no yum, no config changes, no itsp
changes)
can't make outbound calls, can't even call AA.
can't receive inbound.
(this is a call to the AA'
/usr/sbin/tshark -p udp port 5060
14 matches
Mail list logo
