Michael Scheidell
2012-08-11 20:45:17 UTC
I had a sipx crash, while I was on a call.
The CDR still shows the call active.
I went to services->servers->[myserver], CDR and did a restart. didn't help
I logged on to console (root) and typed 'reboot' to reboot.
nothing, still shows call active.
(4.4 installed from i386 cd rom, data restored from a 4.2.1 cd rom
install, that was upgraded to 4.4 and then backed up)
yes, I did a yum upgrade (two weeks ago), and am just doing another one
now, but its only upgrading bind, dhcp initscripts and sudo.
Updated:
bind.i386 30:9.3.6-20.P1.el5_8.2 bind-libs.i386
30:9.3.6-20.P1.el5_8.2 bind-utils.i386 30:9.3.6-20.P1.el5_8.2
caching-nameserver.i386 30:9.3.6-20.P1.el5_8.2 dhclient.i386
12:3.0.5-31.el5_8.1 dhcp.i386 12:3.0.5-31.el5_8.1
initscripts.i386 0:8.45.42-1.el5.centos.1 sudo.i386
0:1.7.2p1-14.el5_8.2
I just restarted CDR again, after yum upgrade, and it said 'CDR [Failed]'
(I did a refresh, and restarted CDR), it restarted and the active call
entry that survived one crash, one CDR restart and one reboot, finally
went away.
--
Michael Scheidell, CTO
o: 561-999-5000
d: 561-948-2259
* Best Intrusion Prevention Product
* Hot Company Finalist 2011
* Best Email Security Product
* Certified SNORT Integrator
______________________________________________________________________
This email has been scanned and certified safe by SpammerTrap(r).
For Information please see http://www.spammertrap.com/
______________________________________________________________________
The CDR still shows the call active.
I went to services->servers->[myserver], CDR and did a restart. didn't help
I logged on to console (root) and typed 'reboot' to reboot.
nothing, still shows call active.
(4.4 installed from i386 cd rom, data restored from a 4.2.1 cd rom
install, that was upgraded to 4.4 and then backed up)
yes, I did a yum upgrade (two weeks ago), and am just doing another one
now, but its only upgrading bind, dhcp initscripts and sudo.
Updated:
bind.i386 30:9.3.6-20.P1.el5_8.2 bind-libs.i386
30:9.3.6-20.P1.el5_8.2 bind-utils.i386 30:9.3.6-20.P1.el5_8.2
caching-nameserver.i386 30:9.3.6-20.P1.el5_8.2 dhclient.i386
12:3.0.5-31.el5_8.1 dhcp.i386 12:3.0.5-31.el5_8.1
initscripts.i386 0:8.45.42-1.el5.centos.1 sudo.i386
0:1.7.2p1-14.el5_8.2
I just restarted CDR again, after yum upgrade, and it said 'CDR [Failed]'
(I did a refresh, and restarted CDR), it restarted and the active call
entry that survived one crash, one CDR restart and one reboot, finally
went away.
--
Michael Scheidell, CTO
o: 561-999-5000
d: 561-948-2259
*| *SECNAP Network Security Corporation
* Best Mobile Solutions Product of 2011* Best Intrusion Prevention Product
* Hot Company Finalist 2011
* Best Email Security Product
* Certified SNORT Integrator
______________________________________________________________________
This email has been scanned and certified safe by SpammerTrap(r).
For Information please see http://www.spammertrap.com/
______________________________________________________________________