Duplicate peers in cache after using sip prune

Get help with installing, upgrading and running Asterisk.

Moderators: muppetmaster, Moderator, Support

Duplicate peers in cache after using sip prune

Postby excendia » Tue Dec 01, 2015 5:11 pm

Hi everyone,
We are using Asterisk 13.6.0 with Realtime Architecture on CentOS 6 and MySQL 5.6. For some reason, whenever we do a sip prune we start to see duplicates of the peer that was pruned from the cache. And the more we used sip prune the more duplicates we have.

Code: Select all
LAB*CLI> sip prune realtime peer EXCE02_2238
Peer 'EXCE02_2238' pruned.

LAB*CLI> sip show peers
Name/username             Host                                    Dyn Forcerport Comedia    ACL Port     Status      Description                      Realtime
EXCE02_2183/EXCE02_2183   234.x.x.185                          D  Yes        Yes            1047     OK (48 ms)                                   Cached RT
EXCE02_2185/EXCE02_2185   234.x.x.185                          D  Yes        Yes            1052     OK (53 ms)                                   Cached RT
EXCE02_2186/EXCE02_2186   234.x.x.185                          D  Yes        Yes            1046     OK (55 ms)                                   Cached RT
EXCE02_2189/EXCE02_2189   234.x.x.185                          D  Yes        Yes            1048     OK (44 ms)                                   Cached RT
EXCE02_2192/EXCE02_2192   234.x.x.185                          D  Yes        Yes            1049     OK (49 ms)                                   Cached RT
EXCE02_2238/EXCE02_2238   234.x.x.185                          D  Yes        Yes            1050     OK (55 ms)                                   Cached RT
EXCE02_2238/EXCE02_2238   234.x.x.185                          D  Yes        Yes            1050     OK (1077 ms)                                  Cached RT
EXCE02_2238/EXCE02_2238   234.x.x.185                          D  Yes        Yes            1050     OK (1081 ms)                                  Cached RT
Peer-A                    192.x.x.12                              Yes        Yes            5060     Unmonitored                                  Cached RT


At that point we need to restart Asterisk to remove correctly the duplicates from the cache. We did not have that issue with Realtime caching and sip prune when we were using Asterisk 1.8.x. Does anyone have any idea on this problem or have encountered the same behavior? Could anyone give some help for this?

Thanks a lot.
excendia
Newsterisk
 
Posts: 1
Joined: Tue Dec 01, 2015 4:48 pm

Return to Asterisk Support

Who is online

Users browsing this forum: Exabot [Bot] and 1 guest