Hi Jan,
There are 13, all of them dated of Nov 29th.
Just in case, I have the md5 of them:
bbdce9613bbb37b2374153242d4818ac
/lib64/openacd/lib/oacd_freeswitch/ebin/freeswitch.beam
1e117ece5a1aacfd48569a014f607311
/lib64/openacd/lib/oacd_freeswitch/ebin/freeswitch_dialer.beam
Hi Melcolm,
That's odd. However, this is a code path issue.
Can you get me the print-out for this one:
$ erl -name test -setcookie ClueCon -noinput -eval io:format(\~p~n\,
[rpc:call('openacd@`hostname -f`', code, get_path, [])]). -s erlang halt
You should find a line there having the value:
Still a no go. That's really odd. I just tried sipxecs-setup --reset-all so
I started all the configs from scratch and the full.log shows the following:
19:15:52.597469 [WARNING] 0.147.0@cpx_supervisor:491 No specs to load for
mediamanager_sup
19:15:52.597793 [WARNING] 0.147.0@cpx_supervisor:491
Hi Melcon,
No need to reformat, just make sure that the latest openacd is installed.
Can yo do this?
$ ls -1 /lib/openacd/lib/oacd_freeswitch/ebin/ | wc -l
(Or lib64)
There should be 13.
Jan Vincent Liwanag
jvliwa...@ezuce.com
On Dec 4, 2012, at 6:22 AM, Melcon Moraes mel...@gmail.com
Hi Jan,
What about the Crash Report on full.log? Any ideas on where else should I
be looking?
As shown by the FS_cli output, I can't connect to the openacd node then
comes the hangup.
-
MM
On Fri, Nov 30, 2012 at 5:25 AM, Jan Vincent Liwanag jvliwa...@ezuce.comwrote:
Hi Melcon,
Problem
Hi Melcon,
Cause for crash report was exactly what was fixed within the new rpm. You have
to manually restart openacd for now though. There's a problem with the restart
script that needs fixing.
$ pkill beam; sleep 10; service openacd start
Let me know if this still occurs.
Jan Vincent
I already restarted many times, rebooted the server as well. Also, if I
simply kill the process and wait a little, it will be spanwed back
automagically. The same error still occours. Didn't tried this time,
yet, to remove/re-add the call center role or even a sipxecs-setup
--reset-all.
Let me
On Fri, Nov 30, 2012 at 11:26 AM, Melcon Moraes mel...@gmail.com wrote:
I already restarted many times, rebooted the server as well. Also, if I
simply kill the process and wait a little, it will be spanwed back
automagically. The same error still occours. Didn't tried this time, yet,
to
Hi Douglas,
I always knew sipXecs restarts its dead processes. Good to know that now
you can disable it, as you said, comes really in hand in the lab.
Thanks for the info
-
MM
On Fri, Nov 30, 2012 at 3:48 PM, Douglas Hubler dhub...@ezuce.com wrote:
On Fri, Nov 30, 2012 at 11:26 AM, Melcon
Hello,
The updates as of today has fixed the issue, and call routing and
distribution is functioning as intended!
Thanks,
Alan Worstell
A1 Networks - Systems Administrator
VTSP, dCAA, LPIC-1, Linux+, CLA, DCTS
(707)570-2021 x204
For support issues please email supp...@a-1networks.com or call
Not to me. Not sure if it is related. I have attached full.log in debug.
As of now, I have the following installed:
openacd-0.9.5-742.g4c27.x86_64
sipxopenacd-4.6.0-890.ge4ca9.x86_64
FS cli shows the following:
2012-11-29 21:38:27.151069 [DEBUG] switch_ivr_play_say.c:1678 done playing
file
Hi Melcon,
Problem here basically is that openacd didnt restart right during the last
update. You might have to 'pkill beam' for now. Then do a 'service openacd
start'.
Sent from my iPhone
On Nov 30, 2012, at 7:52 AM, Melcon Moraes mel...@gmail.com wrote:
Not to me. Not sure if it is
Hi Trevor,
See inline
Jan Vincent Liwanag
jvliwa...@ezuce.com
On Nov 28, 2012, at 3:44 AM, Trevor L Benson tben...@a-1networks.com wrote:
Hello,
We have been in the process of testing openUC 4.6 with plans to migrate off
of our 4.4. The last functional test for internal use was
Jan,
Response Inline:
On Nov 28, 2012, at 2:39 AM, Jan Vincent Liwanag jvliwa...@ezuce.com wrote:
Hi Trevor,
See inline
Jan Vincent Liwanag
jvliwa...@ezuce.com
On Nov 28, 2012, at 3:44 AM, Trevor L Benson tben...@a-1networks.com wrote:
Hello,
We have been in the
Do you really have literally {SERVERNAME} on the output or you just
masked the server name? You're supposed to have your FQDN in place.
-
MM
On Wed, Nov 28, 2012 at 1:08 PM, Trevor L Benson
tben...@a-1networks.comwrote:
Jan,
Response Inline:
On Nov 28, 2012, at 2:39 AM, Jan Vincent
On 11/28/12 7:44 AM, Melcon Moraes wrote:
Do you really have literally {SERVERNAME} on the output or you just
masked the server name? You're supposed to have your FQDN in place.
-
MM
Hello,
This is just the masked FQDN of our server.
Regards,
Alan Worstell
A1 Networks - Systems
Trevor,
Found out what's causing this. Some freeswitch integration files turned out to
be missing. Fixing this on the next RPM of openacd.
Jan Vincent Liwanag
jvliwa...@ezuce.com
On Nov 29, 2012, at 12:19 AM, Alan Worstell aworst...@a-1networks.com wrote:
On 11/28/12 7:44 AM, Melcon Moraes
Hello,
We have been in the process of testing openUC 4.6 with plans to migrate off
of our 4.4. The last functional test for internal use was migrating our ACD to
a Call Center configuration.
OVERVIEW:
Our openUC server is version 4.6.0-21 with the latest updates.
OpenACD 4.6 instructions
18 matches
Mail list logo
