[Home]

Summary:ASTERISK-25944: chan_sip: Multiple peers with same name
Reporter:Bill Neely (ceo_xantek)Labels:
Date Opened:2016-04-19 16:44:13Date Closed:2020-01-14 11:14:10.000-0600
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Channels/chan_sip/Registration
Versions:13.8.1 Frequency of
Occurrence		Frequent
Related
Issues:
Environment:OS- centos7Attachments:
Description: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
Comments:By: Asterisk Team (asteriskteam) 2016-04-19 16:44:14.014-0500

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].
By: Rusty Newton (rnewton) 2016-04-20 12:53:25.568-0500

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


By: Bill Neely (ceo_xantek) 2016-04-21 12:08:09.787-0500

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.
By: Bill Neely (ceo_xantek) 2016-04-21 12:17:51.575-0500

Some additional info:
When executing sip reload, I get the follwoing errors:

[2016-04-21 17:15:22] ERROR[23238]: stasis_cache.c:845 caching_topic_exec: Attempting to remove an item from the SIP/xxxx188-cached cache that isn't there: ast_endpoint_snapshot_type SIP/xxxx188
[2016-04-21 17:15:22] ERROR[23238]: stasis_cache.c:845 caching_topic_exec: Attempting to remove an item from the SIP/xxxx188-cached cache that isn't there: ast_endpoint_snapshot_type SIP/xxxx188
[2016-04-21 17:15:22] ERROR[23238]: stasis_cache.c:845 caching_topic_exec: Attempting to remove an item from the SIP/xxxx188-cached cache that isn't there: ast_endpoint_snapshot_type SIP/xxxx188
[2016-04-21 17:15:22] ERROR[23238]: stasis_cache.c:845 caching_topic_exec: Attempting to remove an item from the SIP/xxxx188-cached cache that isn't there: ast_endpoint_snapshot_type SIP/xxxx188
[2016-04-21 17:15:23] ERROR[23238]: stasis_cache.c:845 caching_topic_exec: Attempting to remove an item from the SIP/xxxx188-cached cache that isn't there: ast_endpoint_snapshot_type SIP/xxxx188

By: Bill Neely (ceo_xantek) 2016-04-21 14:31:29.517-0500

not sure3 if this is helpful or not, BUT

Setting rtautoclear to yes or to 60 in sip.conf seems to make the issue go away
By: Rusty Newton (rnewton) 2016-04-25 16:30:18.740-0500

{quote}
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.
{quote}

This isn't a forum for technical support. We need you to describe exactly how to reproduce the issue. That is, describe the steps taken to reproduce the issue from scratch. Including:

* What configuration is needed?
* What is the database schema used?
* What does a dump of your current config look like?
* What modules are in use? What database backend (with exact versions)?

Then, in addition, a debug log captured during an observation of the issue following the instructions that were previously linked.

chan_sip is now under extended support in 13, meaning that it is up to the community (outside the core development team) to support it. For an issue like this - it may not get any attention unless it is extremely clear what the issue is and how to reproduce it step by step.

If we can't nail that information down then we'll close out the issue as "Cannot reproduce".
By: Asterisk Team (asteriskteam) 2016-05-10 12:00:01.860-0500

Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].

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