-
Well, since the time of the original post I've seen it on SU 311 and 317. As to 327 - I don't think I've seen it but there haven't been enough trigger events to know for sure. Coring appears to be associated with disruptions on the circuit due to maintenance or fail-over in upstream systems which are, fortunately, rare. And even when
-
Bump... Been over a year. Anyone with an idea? Are Dialogic people watching? We still see this periodically - generally if there an interruption in the phone signal like a hit when the telco is doing maintenance. My questions remain as listed above.
-
Additional information. Here is the backtrace from the core file: #0 0x0804ae6c in CAgent::SetAgentConfig () #1 0x08051448 in CFallbackHandler::RaiseFaultPLLBad () #2 0x0805069b in CFallbackHandler::RaiseFault () #3 0x0805019c in CClockFaultsHandler::ProcessClockFault () #4 0x007d273b in start_thread () from /lib/libpthread.so.0 #5 0x002cccfe in clone
-
We discovered that the dlgclockdaemon process cored on one of our servers a couple days ago but just noted today. The system seems to be operating normally, otherwise. I searched every PDF supplied with our SR 6.1 Linux for references to that process and found none. Questions: 1. What is that process? 2. Is it necessary? 3. Can I just restart that single
-
SR 6.1 Linux. 2-DMV1200BTEPW per server. CentOS 5.4 I searched all documentation for advice on Linux kernel parameter recommendations to no avail. Are as-installed OS defaults fine for all Dialogic installs? If not, what are the recommended changes to sysctl.conf and are they documented somewhere?
-
Specifically, Service Release 6.1/Linux. We have a couple stacks of servers plus dev and test machines. No Dialogic libraries are statically linked. We have a variety of different programs we deploy on the machines. Is it safe to deploy a program compiled on a machine with service-update X on a machine with service-update Y or safe as long as X >
-
I did look there hence the statement "I am aware of the Services & Support News forum" in my original post. Perhaps I need reading glasses but I was unable to locate any postings alerting users to quite a number of updates - in fact probably more than half over the period I checked - which makes it a useless way to determine the most up
-
I'm sorry but that is not very useful. First, there is no "default". There is what gets created when you run CFG. And what CFG puts in there is hard to predict. If I could run CFG top-to-bottom at any time and get the same result I would be relatively comfortable. But the result I get depends on whether I decided to enter the config for
-
[quote user="sam@glenwoodmicro.net"] ...Do you know if dialogic is planning to release one for 64 bit linux in near future?... [/quote] I do not - you would have to ask them. While it would be nice, my feeling is that they have no interest in *ever* supporting 64-bit Linux in this software release so we just dumb-down our telephony servers
-
Sorry, just noticed in your title that you said 2.19.2
