Hi, all. I started to play with 4.4.0. Today I upgraded my test system from 4.2.1 to 4.4.0 (4.4.0- 2011-01-18EST13:19:19 swift). And now sipxproxy process fails (sipxproc shows "failed" for sipxproxy). I tried to analize the problem: I found the following in the sipXproxy log: "2011-01-20T12:42:02.166892Z":39:KERNEL:ERR:sipx4.lab.nstel.ru:pid-17831:B7FC26E0:SipXProxy:"OsServerSocket: bind to port 172.23.12.104:5061 failed with error: 98 = 0x62" Ok, lets see who's there: [root@sipx4 sipxpbx]# netstat -nlp | grep 5061 tcp 0 0 172.23.12.104:5061 0.0.0.0:* LISTEN 17082/sipxacd
Then i tried to turn ACD off - unchecked ACD on the "server roles" configuration page. After that, sipXproxy works. At least sipxproc shows "running". If i turn on ACD on the "server roles" page, the problem comes back. So... my idea is that acd configuration is wrong in 4.4.0... The whole snapshot is available at ftp://sipx:[email protected]/sipxproxy-failed-sipx-configuration-sipx4.lab.nstel.ru.tar.gz Is my analisys correct? Is it known problem? At the moment i don't need ACD, so i can continue without it... but i think the problem is serious... Should i raise a jira? Is it possible to fix the problem in this release (4.4.0-46.g01752)? Or shoud i just wait a while? Thanks and reagrds, Nikolay.
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
