On 25/07/2012, at 7:54 AM, Alejandro Imass wrote: > On Tue, Jun 12, 2012 at 4:04 PM, Alejandro Imass <a...@p2ee.org> wrote: >> This has come up before on the list and archives but I don't seem to >> find a solution for this. On just a few nodes we have this situation >> where we see the IP disappear from the CLI iax2 show peers list but >> the status shows OK: >> >> 3012/3012 (Unspecified) (D) 255.255.255.255 0 OK (89 >> ms) >> Not sure how relevant it is but IAX can appear to be working on one links available in only one direction. If a firewall is blocking one end then one end may appear fine, and the other disconnected.
It might be a NAT issue causing the blocking where registering opens the NAT tables but they time out - this used to happen on older home firewalls Or it could be something else quite odd - can you confirm you have network connectivity to the end devices? - does it happen to devices on the local lan or just via firewall I doubt very much its the quality settings, they are just reflecting whats being seen rather than the cause of the issue. When you turn on IAX debug do you see the qualify packets and replies (pings and pongs) in asterisk or are they missing? If so then also use tcpdump to see if you are actually getting the packets you would expect at your network card to figure out if its internal to the server or related to the network Good luck >> How can the status be OK a few milliseconds ago and have no IP ?? The >> strange thing is that the IP does show up once in a while and then >> disappears once again but the OK is always there. >> >> Asterisk 1.4.29 running on FreeBSD 7.0-RELEASE > > OK, so I guess nobody answered because we had an old version. Well, we > upgraded to 1.8.13.1 and we have much the same problem although after > the upgrade I don't seem to find any cases where the qualify value is > OK (xx ms) and the IP is gone (like we had in 1.4.29) but the effect > is the same: the extension becomes non-reachable pretty quickly. > > IMHO this is indicating that the qualify settings are being ignored, > and the only workaround has been lowering the re-register time to > sometimes as low as 3 seconds. Even though several docs say that the > qualify values can also act as a keep alive, it's not working for us > and I still have to reduce the register time to very low values > because qualifyfreqok and qualifyfreqnotok don't see to be doing > anything... > > Any clues?? > > -- > _____________________________________________________________________ > -- 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 -- _____________________________________________________________________ -- 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
