[asterisk-bugs] [JIRA] (ASTERISK-21069) xmpp distributed device states aggregation update fails

[Richard Mudgett (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-21069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=205328#comment-205328 ] 

Richard Mudgett edited comment on ASTERISK-21069 at 4/15/13 5:57 PM:
---------------------------------------------------------------------

When using res_xmpp or res_jabber, distrbuted device states became broken since changes related to ASTERISK-20175 were applied.

                
      was (Author: alecdavis):
    When using res_xmpp or res_jabber, distrbuted device states became broken since changes related to https://issues.asterisk.org/jira/browse/ASTERISK-20175 were applied.

                  
> xmpp distributed device states aggregation update fails
> -------------------------------------------------------
>
>                 Key: ASTERISK-21069
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21069
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_xmpp
>    Affects Versions: 11.1.2
>         Environment: raspbx with Asterisk 11.1.2 on Debian7 / Wheezy
>            Reporter: Marco Paland
>         Attachments: 21069_desc.txt
>
>
> I'm having a real hard time and no clue why the following happens.
> The custom device stats can't be updated on remote boxes. I file this as a bug.
> [Edit - per the issue guidelines, removed excessive inline debug and conf files and attached whole description as a file.  Essentially in a distributed device state setup with res_xmpp, the state of a custom device on one system is set to RINGING, the other system receives the proper XMPP, processes it, and then does not update the device state until the current state is re-set to the current state (NOT_INUSE). At that point the state shows as RINGING. .. ]
> Is this a bug or do miss something?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira