On Fri, 2008-08-08 at 19:52 +0400, Nikolay Kondratyev wrote:
> > Are you sure the attached log came from 13232? It indicates the
> > alarmServerUrl issue which was fixed in 13228.
>
> I stopped sipx, removed all logs, started sipx and still see the same
> problem (with the same log messages). "Yum list installed" shows 13232.
>
> > (sipxconfig.properties.in should have alarmApi.serviceUrl instead of
> > alarmApi.alarmServerUrl).
>
> I have them both :)
>
> [EMAIL PROTECTED] sipxpbx]# cat /etc/sipxpbx/sipxconfig.properties.in| grep
> alarm
> domainManagerImpl.alarmServerUrl=https://${MY_FULL_HOSTNAME}:8092
> alarmContextImpl.host=${MY_FULL_HOSTNAME}
> alarmApi.serviceUrl=https://${MY_FULL_HOSTNAME}:8092/RPC2
> alarmApi.alarmServerUrl=https://${SIPXCHANGE_DOMAIN_NAME}:8092/RPC2
>
> Looks like upgrade scripts are inaccurate...
This is the sort of disruptive change you'll get with development
builds. Certainly when we get to testing upgrades to any release
candidate we'll try to avoid this, but note this excerpt from project
policy statement on the temp distro page:
It is not a goal of the project to support upgrade from or
between development builds.
so, as troublesome as it is, that's not a bug.
--
Scott Lawrence tel:+1.781.229.0533;ext=162 or sip:[EMAIL PROTECTED]
sipXecs project coordinator - SIPfoundry http://www.sipfoundry.org/sipXecs
CTO, Voice Solutions - Bluesocket Inc. http://www.bluesocket.com/
http://www.pingtel.com/
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
