Summary:ASTERISK-21164: Need clarification on distributed device state behavior and whether this behavior is a possible regression
Reporter:Rusty Newton (rnewton)Labels:
Date Opened:2013-02-25 16:33:57.000-0600Date Closed:2013-04-17 09:00:00
Versions:Frequency of
is caused byASTERISK-20175 Security Vulnerability: denial of service attack through exploitation of device state caching
is related toASTERISK-21069 xmpp distributed device states aggregation update fails
is related toASTERISK-21429 Distributed Device State using JABBER/XMPP not working since Secuity Advisory AST-2012-015
Environment:pbx1: SVN 11 r381835, pbx2: 11.1.0, connected to OpenFire XMPP pubsub via res_xmppAttachments:( 0) config.txt
( 1) pbx1_debug.txt
( 2) pbx2_debug.txt
( 3) state_changes.txt
Description:How should distributed device state work on a cluster of only two systems? I haven't found documentation that describes this specifically. If it doesn't exist, then it should be documented to help admins understand how to use the feature.

I've provided attached documents to show where behavior differences between an older version of 11(11.1.0 chosen because JColp thought ASTERISK-20175 may be responsible from some of the behavior differences) and a newer SVN version of 11 might indicate a regression. Or, it may just indicate behavior that was broken before and is now fixed..

The problem:

On pbx1 I don't see any reflection of device state for "Custom:mystate" when pbx2 changes the state of that device.

If pbx1 changes device state first, then on pbx2 you can see new values for device state of "Custom:mystate" by using DEVICE_STATE or looking at the associated hint. However "devstate list" doesn't show a change.

Which behavior is correct?

* see attached config.txt for xmpp.conf of the systems
* see attached state_changes.txt for a layout of the device states when either system is receiving the pubsub events.
* see attached pbx1_debug.txt for debug when pbx1 receives changes from pbx2.
* see attached pbx2_debug.txt for debug when pbx2 receive changes from pbx1

Comments:By: Alec Davis (alecdavis) 2013-04-13 16:26:29.925-0500

Didn't see this bug, but fix is on ASTERISK-21429

11.1.1 would have worked.
11.1.0 doesn't have the changes from ASTERISK-20175

By: Alec Davis (alecdavis) 2013-04-13 17:33:17.081-0500

I've related this to the issue that fixes this.

We need a link option of 'is fixed by'