Try changing qualify=yes to qualify=90 on your TCP peers.
From: [email protected] [mailto:[email protected]] On Behalf Of Bryant Zimmerman Sent: Friday, January 27, 2012 9:45 AM To: [email protected] Subject: Re: [asterisk-users] sip reload and TCP transport. I am running into an interesting issue with asterisk 1.8.x When I do a sip reload any peer that is using TCP as the transport protocol losses it Host entry from the reg list. and it goes to UNKNOW in the Status col. Endpoints using UDP transport do not do this. This means that for 3 to 5 min after a sip reload the TCP transport endpoints can't be called. Any ideas on what could cause this and how I could fix it. Thanks Bryant
-- _____________________________________________________________________ -- 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
