[asterisk-users] where are stored Ip address of static sip peers

[Grégory ESNAUD]

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20130702/b32fd836/attachment.htm>