[asterisk-bugs] [JIRA] (ASTERISK-25944) chan_sip: Multiple peers with same name

[Rusty Newton (JIRA)]

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

Rusty Newton commented on ASTERISK-25944:
-----------------------------------------

Thank you for taking the time to report this bug and helping to make Asterisk better. Unfortunately, we cannot work on this bug because your description did not include enough information. Please read over the Asterisk Issue Guidelines [1] which discusses the information necessary for your issue to be resolved and the format that information needs to be in. We would be grateful if you would then provide a more complete description of the problem. At a minimum, we need:

1. The specific steps or actions you took that caused you to encounter the problem.
2. The behavior you expected and the location of documentation that led you to that expectation.
3. The behavior you actually encountered.

To demonstrate the issue in detail, please include Asterisk log files generated per the instructions on the wiki [2]. If applicable, please ensure that protocol-level trace debugging is enabled, e.g., 'sip set debug on' if the issue involves chan_sip, and configuration information such as dialplan and channel configuration.

Thanks!

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines

[2] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information



> chan_sip: Multiple peers with same name
> ---------------------------------------
>
>                 Key: ASTERISK-25944
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25944
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/Registration
>    Affects Versions: 13.8.1
>         Environment: OS- centos7
>            Reporter: Bill Neely
>            Severity: Minor
>
> sip show peers shows the same phone registered multiple times:
> 188/188           50.xx.x.xx                            D  Yes        Yes            5900     Unmonitored                                  Cached RT
> 188/188           50.xx.xx.x                            D  Yes        Yes            5900     Unmonitored                                  Cached RT
> 188/188           50.xx.xx.x                            D  Yes        Yes            5900     Unmonitored                                  Cached RT
>   
> This does not seem to affect performance, but it seems strange. We have not noticed this behaviour prior to 13.6



--
This message was sent by Atlassian JIRA
(v6.2#6252)