Other indication : there's no database registry on the main ! theMain*CLI> database show /dundi/secret : 7onlF5yX8Rgbk+htlh0AKQ==;QRi3PP1veWV0tc8WXRGHWA== /dundi/secretexpiry : 1366370052 2 results found.
theBackup*CLI> database show /SIP/Registry/Z601-P3 : 172.16.128.174:5060:3600:Z601-P3:sip:[email protected]:5060;transport=udp /SIP/Registry/Z602-P1 : 172.16.128.167:5060:3600:Z602-P1:sip:[email protected]:5060;transport=udp /SIP/Registry/Z602-P2 : 172.16.128.116:5060:3600:Z602-P2:sip:[email protected]:5060;transport=udp /SIP/Registry/Z602-P3 : 172.16.128.170:5060:3600:Z602-P3:sip:[email protected]:5060;transport=udp /SIP/Registry/Z604-P1 : 172.16.128.175:5060:3600:Z604-P1:sip:[email protected]:5060;transport=udp /SIP/Registry/Z604-P2 : 172.16.128.157:5060:3600:Z604-P2:sip:[email protected]:5060;transport=udp /SIP/Registry/Z605-P1 : 172.16.128.158:5060:3600:Z605-P1:sip:[email protected]:5060;transport=udp /SIP/Registry/Z605-P2 : 172.16.128.176:5060:3600:Z605-P2:sip:[email protected]:5060;transport=udp /SIP/Registry/Z605-P3 : 172.16.128.190:5060:3600:Z605-P3:sip:[email protected]:5060;transport=udp /SIP/Registry/Z607-P1 : 172.16.128.172:5060:3600:Z607-P1:sip:[email protected]:5060;transport=udp /SIP/Registry/Z608-P1 : 172.16.128.117:5060:3600:Z608-P1:sip:[email protected]:5060;transport=udp /SIP/Registry/Z608-P2 : 172.16.128.153:5060:3600:Z608-P2:sip:[email protected]:5060;transport=udp /SIP/Registry/Z608-P3 : 172.16.128.165:5060:3600:Z608-P3:sip:[email protected]:5060;transport=udp /SIP/Registry/Z608-P4 : 172.16.128.161:5060:3600:Z608-P4:sip:[email protected]:5060;transport=udp /SIP/Registry/Z609-P1 : 172.16.128.156:5060:3600:Z609-P1:sip:[email protected]:5060;transport=udp /SIP/Registry/Z609-P3 : 172.16.128.171:5060:3600:Z609-P3:sip:[email protected]:5060;transport=udp /SIP/Registry/Z609-P4 : 172.16.128.162:5060:3600:Z609-P4:sip:[email protected]:5060;transport=udp /dundi/secret : 83BybhKWtGO4bqwNWdv+Tg==;mUsQNpnbfxrUfNQh8YDgdQ== /dundi/secretexpiry : 1372764840 So... why the database sip/registry is populated on the backup (that seems the normal behavior) and not on the main server? De : [email protected] [mailto:[email protected]] De la part de Grégory ESNAUD Envoyé : mardi 2 juillet 2013 10:04 À : Asterisk Users Mailing List - Non-Commercial Discussion Objet : [asterisk-users] where are stored Ip address of static sip peers Hello dear list, I came to you about a strange behavior on one of our server. The architecture is built around 2 servers: a main and a backup. The clients (Cisco's Hardphone and counterpath 's softphone Bria) get the Asterisk ip addresses trough dns-srv mechanism (_sip.tcp). The main Asterisk is located on our main site, and the backup is located on a remote site, so they are seperated through an operated WAN (Orange Business Services). The same WAN is used to connect all of our sites (4), where clients are dispatched (hardphone and softphone). The backup config files are a rsync copy of the main config files. The softphone clients are realtime peers through an ldap setup. The hardphone are static, configured through sip.conf. The "strange" behavior is the following: On the main server, we've got this (only showing the hardphone here): theMain*CLI> sip show peers Name/username Host Dyn Forcerport ACL Port Status Description Realtime Z601-P2/Z601-P2 (Unspecified) D 0 Unmonitored Z601-P3/Z601-P3 (Unspecified) D 0 Unmonitored Z602-P1/Z602-P1 (Unspecified) D 0 Unmonitored Z602-P2/Z602-P2 (Unspecified) D 0 Unmonitored Z602-P3/Z602-P3 (Unspecified) D 0 Unmonitored Z604-P1/Z604-P1 (Unspecified) D 0 Unmonitored Z604-P2/Z604-P2 (Unspecified) D 0 Unmonitored Z605-P1/Z605-P1 (Unspecified) D 0 Unmonitored Z605-P2/Z605-P2 (Unspecified) D 0 Unmonitored Z605-P3/Z605-P3 (Unspecified) D 0 Unmonitored Z607-P1/Z607-P1 (Unspecified) D 0 Unmonitored Z608-P1/Z608-P1 (Unspecified) D 0 Unmonitored Z608-P2/Z608-P2 (Unspecified) D 0 Unmonitored Z608-P3/Z608-P3 (Unspecified) D 0 Unmonitored Z608-P4/Z608-P4 (Unspecified) D 0 Unmonitored Z609-P1/Z609-P1 (Unspecified) D 0 Unmonitored Z609-P3/Z609-P3 (Unspecified) D 0 Unmonitored Z609-P4/Z609-P4 (Unspecified) D 0 Unmonitored Z609-P5/Z609-P5 (Unspecified) D 0 Unmonitored That's normal, because the clients have been unplugged for many days (about 1 week). On the backup we've got this: theBackup*CLI> sip show peers Name/username Host Dyn Forcerport ACL Port Status Description Realtime Z601-P2/Z601-P2 (Unspecified) D 0 Unmonitored Z601-P3/Z601-P3 172.16.128.174 D 5060 Unmonitored Z602-P1/Z602-P1 172.16.128.167 D 5060 Unmonitored Z602-P2/Z602-P2 172.16.128.116 D 5060 Unmonitored Z602-P3/Z602-P3 172.16.128.170 D 5060 Unmonitored Z604-P1/Z604-P1 172.16.128.175 D 5060 Unmonitored Z604-P2/Z604-P2 172.16.128.157 D 5060 Unmonitored Z605-P1/Z605-P1 172.16.128.158 D 5060 Unmonitored Z605-P2/Z605-P2 172.16.128.176 D 5060 Unmonitored Z605-P3/Z605-P3 172.16.128.190 D 5060 Unmonitored Z607-P1/Z607-P1 172.16.128.172 D 5060 Unmonitored Z608-P1/Z608-P1 172.16.128.117 D 5060 Unmonitored Z608-P2/Z608-P2 172.16.128.153 D 5060 Unmonitored Z608-P3/Z608-P3 172.16.128.165 D 5060 Unmonitored Z608-P4/Z608-P4 172.16.128.161 D 5060 Unmonitored Z609-P1/Z609-P1 172.16.128.156 D 5060 Unmonitored Z609-P3/Z609-P3 172.16.128.171 D 5060 Unmonitored Z609-P4/Z609-P4 172.16.128.162 D 5060 Unmonitored Z609-P5/Z609-P5 (Unspecified) D 0 Unmonitored Even with a sip reload or a core restart now, the ip address are cached on the backup... As they're not realtime peers, where the ip address information are stored? As the config files are exactly the same, why theMain is not storing the ip address? Some info: theBackup config and version: http://pastebin.com/f1fcgmZp theMain config and version: http://pastebin.com/FEd9MNwn Thanks! Greg
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
