Summary: | ASTERISK-21007: Remove Non Real time SIP Peers Automatically | ||
Reporter: | manish thakor (manish) | Labels: | |
Date Opened: | 2013-01-29 00:53:17.000-0600 | Date Closed: | 2013-03-15 22:06:37 |
Priority: | Major | Regression? | |
Status: | Closed/Complete | Components: | Channels/chan_sip/General |
Versions: | 11.2.0 | Frequency of Occurrence | |
Related Issues: | |||
Environment: | Cents OS 6.2 | Attachments: | |
Description: | I have Non real time sip peers after some times sip peers automatically remove.when i restart asterisk sip peers are display in sip show peers list. | ||
Comments: | By: Walter Doekes (wdoekes) 2013-01-31 13:25:26.509-0600 I'm sorry. I don't understand the problem. Could you be a little more verbose? How can we reproduce the problem? What do you expect? What happens instead? By: manish thakor (manish) 2013-02-01 01:38:22.923-0600 I have sip peers like this: {noformat} [1111] type=friend defaultuser=1111 secret=1234 host=dynamic disallow=all allow=alaw allow=ulaw canreinvite=yes context=loginagi {noformat} now sip show peers display : {noformat} IVR-Server*CLI> sip show peers Name/username Host Dyn Forcerport ACL Port Status Description 1111/1111 192.168.21.211 D a 5060 Unmonitored 1112/1112 192.168.21.224 D a 5060 Unmonitored 1113/1113 192.168.21.203 D a 5060 Unmonitored 1114/1114 192.168.16.167 D a 5060 Unmonitored 1115/1115 192.168.21.205 D a 5060 Unmonitored 1116/1116 192.168.21.206 D a 5060 Unmonitored 1117/1117 192.168.16.207 D a 5060 Unmonitored {noformat} After some times all sip peers automatically disappears and display empty like this: {noformat} sip show peers Name/username Host Dyn Forcerport ACL Port Status Description {noformat} By: Walter Doekes (wdoekes) 2013-02-01 04:17:30.758-0600 Ok. If that is true, then you'd be looking at a severe bug. Could you trim your config down to 4 files -- asterisk.conf, modules.conf, sip.conf and extensions.conf -- and then reproduce it? * If you can reproduce: please attach the (sanitized!) conf's. * If you cannot: re-add the configurations until the problem occurs. You will have found useful information that points to where the problem is. By: Rusty Newton (rnewton) 2013-02-07 17:41:58.497-0600 And if you can reliably reproduce it, then provide an Asterisk log with VERBOSE and DEBUG turned up to level 5 ,so we can see if anything strange pops up when it happens. By: Matt Jordan (mjordan) 2013-03-15 22:06:28.806-0500 Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested. Further information can be found at http://www.asterisk.org/developers/bug-guidelines |