[asterisk-users] Realtime vs Static Files
Leandro Dardini
ldardini at gmail.com
Fri Jan 25 08:31:10 CST 2013
2013/1/25 Dan Journo <dan at keshercommunications.com>
> >> Upgrading to the latest version didn't help. After about 30 minutes,
> Asterisk2 tries to send out OPTIONS keepalive packets to peers listed as
> Registered on Asterisk1.****
>
> > It is something really amazing... Can you run "sip show peers" on each
> one of the servers and post the response?****
>
> ** **
>
> > You said the second asterisk is completely opaque to your peers. Can
> you run a tcpdump on secondary server to see if for some obscure reason the
> phones try to contact the secondary asterisk?****
>
> ** **
>
> I'll monitor one peer using tcpdump over a few hours and then review the
> packets. However, SIP DEBUG isn't showing any REGISTER packets.****
>
> ** **
>
> Here's the sip peers output. Values and names have been hidden. Some
> appear as Unreachable the secondary server and some appear as OK.****
>
> I think some are listed as OK because the endpoint routers are performing
> some type of SIP ALG and routing packets based on port number and not
> source ip address.****
>
> However, from the SIP DEBUG output, it seems clear that the secondary
> server in this example is sending out Keepalives based on the information
> that the primary server has entered into the realtime DB.****
>
> ** **
>
> *Show peers Output from a primary server*
>
> Name/username Host Dyn
> Forcerport ACL Port Status Realtime****
>
> a201/A201 217.x.x.48 D
> N 65229 OK (88 ms) Cached RT****
>
> a202 (Unspecified) D
> N 0 UNREACHABLE Cached RT****
>
> b201/44845287 78.x.x.101 D N
> 5060 OK (26 ms) Cached RT****
>
> c201/s 193.x.x.174 D N
> 5060 OK (52 ms) Cached RT****
>
> d201/d201 94.x.x.228 D N
> 5060 OK (33 ms) Cached RT****
>
> e201/e201 94.x.x.44 D N
> 55018 OK (40 ms) Cached RT****
>
> e202/e202 94.x.x.44 D N
> 55022 OK (46 ms) Cached RT****
>
> e203/e203 94.x.x.44 D N
> 55024 OK (40 ms) Cached RT****
>
> e204/e204 94.x.x.44 D N
> 55008 OK (40 ms) Cached RT****
>
> e205/e205 94.x.x.44 D N
> 55016 OK (41 ms) Cached RT****
>
> e206/e206 94.x.x.44 D N
> 55014 OK (40 ms) Cached RT****
>
> e207/e207 94.x.x.44 D N
> 55020 OK (41 ms) Cached RT****
>
> e208/e208 94.x.x.44 D N
> 5060 OK (41 ms) Cached RT****
>
> e209/e209 94.x.x.44 D N
> 55012 OK (40 ms) Cached RT****
>
> e210/e210 94.x.x.44 D N
> 55010 OK (41 ms) Cached RT****
>
> e211/e211 94.x.x.44 D N
> 55026 OK (38 ms) Cached RT****
>
> e212/e212 81.x.x.93 D N
> 5060 OK (46 ms) Cached RT****
>
> f201 (Unspecified) D N
> 0 UNREACHABLE Cached RT****
>
> g201/g 78.x.x.207 D N 5060
> OK (29 ms) Cached RT****
>
> h201/h201 217.x.x.78 D N 38980
> OK (22 ms) Cached RT****
>
> i201 (Unspecified) D N
> 0 UNREACHABLE Cached RT****
>
> i203/ i203 109.x.x.103 D N 5060
> OK (32 ms) Cached RT****
>
> i204/ i204 109.x.x.103 D N 1025
> OK (31 ms) Cached RT****
>
> i205/ i205 81.x.x.144 D N
> 5060 OK (32 ms) Cached RT****
>
> i206/ i206 109.x.x.103 D N 1035
> OK (31 ms) Cached RT****
>
> i207/ i207 109.x.x.103 D N
> 1032 OK (32 ms) Cached RT****
>
> i208/ i208 109.x.x.103 D N 1024
> OK (31 ms) Cached RT****
>
> j201/s 94.x.x.62 D N
> 57813 OK (35 ms) Cached RT****
>
> o201/o201 92.x.x.86 D N
> 51824 OK (47 ms) Cached RT****
>
> o202/o202 92.x.x.86 D N
> 58641 OK (48 ms) Cached RT****
>
> o203/o203 92.x.x.86 D N
> 49172 OK (47 ms) Cached RT****
>
> j204/j204 176.x.x.214 D N
> 34824 OK (49 ms) Cached RT****
>
> k201/k201 2.x.x.169 D N
> 52757 OK (53 ms) Cached RT****
>
> k202/k202 (Unspecified) D N
> 0 UNKNOWN Cached RT****
>
> l201/l201 (Unspecified) D N
> 0 UNKNOWN Cached RT****
>
> m201/s 92.x.x.95 D N
> 54020 OK (32 ms) Cached RT****
>
> n201 (Unspecified) D N
> 0 UNREACHABLE Cached RT****
>
> ** **
>
> *Show peers Output from a secondary server*
>
> Name/username Host Dyn
> Forcerport ACL Port Status Realtime****
>
> d201 94.x.x.228 D N
> 5060 UNREACHABLE Cached RT****
>
> e202 94.x.x.44 D
> N 55022 UNREACHABLE Cached RT****
>
> e203 94.x.x.44 D
> N 55024 UNREACHABLE Cached RT****
>
> e204 94.x.x.44 D
> N 55008 UNREACHABLE Cached RT****
>
> e205 94.x.x.44 D
> N 55016 UNREACHABLE Cached RT****
>
> e206 94.x.x.44 D
> N 55014 UNREACHABLE Cached RT****
>
> e207 94.x.x.44 D
> N 55020 UNREACHABLE Cached RT****
>
> e209 94.x.x.44 D
> N 55012 UNREACHABLE Cached RT****
>
> e210 94.x.x.44 D
> N 55010 UNREACHABLE Cached RT****
>
> e212 81.x.x.93 D
> N 5060 UNREACHABLE Cached RT****
>
> h201 217.x.x.78 D N
> 38980 UNREACHABLE Cached RT****
>
> j201 94.x.x.62 D N
> 57813 UNREACHABLE Cached RT****
>
> o201 92.x.x.86 D
> N 51824 OK (47 ms) Cached RT****
>
> o202 92.x.x.86 D
> N 58641 OK (47 ms) Cached RT****
>
> o203 92.x.x.86 D
> N 49172 OK (48 ms) Cached RT****
>
> o204 (Unspecified) D
> N 0 UNREACHABLE Cached RT****
>
> k201 2.x.x.169 D N
> 52757 OK (52 ms) Cached RT****
>
> k202 195.x.x.5 D N
> 20569 UNREACHABLE Cached RT****
>
> ** **
>
> --
> _____________________________________________________________________
> -- 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
>
It is really unbelievable ... I was thinking: Asterisk uses an internal
database to maintain states of peers. It is usually located in
/var/lib/asterisk/astdb and it is a berkely db, but other database backends
seem available. Are you sharing also this database between the two servers?
It is the only option left...
Leandro
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20130125/dee97efb/attachment-0001.htm>
More information about the asterisk-users
mailing list