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

[Bill Neely (JIRA)]

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

Bill Neely commented on ASTERISK-25944:
---------------------------------------

Sorry I cannot provide more info. The only action I took was to enter "sip show peers" The listing shows the same peer multiple times. The expected behaviour is a single entry for each peer. This morning I am getting as many as 30 listings of the same peer.

Entering sip reload clears out the multiple entries, but they appear again after a while.

So far I have not been able to assess whether having the mutilple listings has any negative impact on actaully reaching that unit.

Our peers are all RT cached peers set to "friend" in the sip conf database file.

> 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
>            Assignee: 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)