[asterisk-bugs] [JIRA] Closed: (ASTERISK-19309) [patch] DUNDi message routing bug

[Digium Subversion (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-19309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Digium Subversion closed ASTERISK-19309.
----------------------------------------

    Resolution: Fixed

> [patch] DUNDi message routing bug
> ---------------------------------
>
>                 Key: ASTERISK-19309
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-19309
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: PBX/pbx_dundi
>            Reporter: Peter Racz
>         Attachments: dundi_routing.patch
>
>
> There is a bug in the creation of the EID list in DUNDi DPDISCOVER messages. This bug breaks the message routing of DUNDi and it stops the message forwarding although not all nodes have received the message. The problem happens if a node is in the peer list but it is not reachable temporarily. The current implementation of DUNDi includes also peers into the EID list that are temporarily unreachable and therefore, these nodes (and possibly others as well) won't receive the message even if they could be reached over an indirect path.
> The following figure shows an example. The connection between PBX1 and PBX3 is temporarily broken in the example. Now, if PBX1 sends a DPDISCOVER message, the message sent to PBX2 will include the EID of PBX3 in the EID list, although PBX1 cannot send the message to PBX3. Since PBX2 sees the EID of PBX3 in the message, it assumes that PBX3 has already received this message and will stop forwarding it. Thus, PBX3 and PBX4 will not receive the message at all. 
> {noformat}
>                         +------+ 
>                         |      |
>       +-----------------| PBX2 |
>       |                 |      |
>       |                 +------+ 
>       |                    |
>       |                    |
>   +------+              +------+         +------+
>   |      |              |      |         |      |
>   | PBX1 |------X-------| PBX3 |---------| PBX4 |
>   |      |    broken    |      |         |      |
>   +------+  connection  +------+         +------+
> {noformat}
> Additionally, the current implementation includes the EID 00:00:00:00:00:00 in DPDISCOVER messages when dynamic peers with [*] are configured in dundi.conf and it also tries to send NULL messages (qualify) to the peer with EID 00:00:00:00:00:00.
> The attached patch resolves both these issues.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira