The asterisk qualify option in sip or iax sends a test packet to the remote host every minute and measures the time it takes for a response to come back. If this time frame is less than what is configured on the qualify statement or 2000ms if it is 'yes' than the host is flagged unreachable until pings succeed again. In SIP the packet is an OPTIONS request and any response is accepted. So if you're having this problem with several of your systems at the same time, it may point to a problem or interruption in your network services. Do you have any hosts or gateways on dynamic IPs that get refreshed every 8 min?
John Blackman wrote:
All,
I have an issue with IAX that I can’t comprehend. Approximately every eight minutes my servers go unreachable. They stay unreachable for exactly 10ms. I have two servers running IAX and it happens on both servers simultaneously. I have searched the archives and see similar issues, but not the exact same one. I am on the current CVS stable version of *.
Also, during IAX calls, every couple of minutes there is about a second of silence. Silence suppression is turned off on all phones (Grandstream BT101s). This issue does not occur during SIP calls.
I do have a similar registration problem with SIP. There are two phones on one site that go reachable/unreachable. (See extension 6666 in the sample below. This is a B101 that is registered to my server, but it happens to be at the same location as the second * server.)
If anyone can point me in the right direction for troubleshooting, I would appreciate it. I am pasting example error messages that I receive below.
TIA,
John
*CLI Output:*
May 23 12:50:05 NOTICE[7176]: chan_iax2.c:5616 iax2_poke_noanswer: Peer 'arlington' is now UNREACHABLE!
May 23 12:50:15 NOTICE[7176]: chan_iax2.c:5213 socket_read: Peer 'arlington' is now REACHABLE!
May 23 12:58:19 NOTICE[7176]: chan_iax2.c:5616 iax2_poke_noanswer: Peer 'arlington' is now UNREACHABLE!
May 23 12:58:29 NOTICE[7176]: chan_iax2.c:5213 socket_read: Peer 'arlington' is now REACHABLE!
May 23 13:06:07 NOTICE[5126]: chan_sip.c:6901 sip_poke_noanswer: Peer '6666' is now UNREACHABLE!
May 23 13:06:34 NOTICE[7176]: chan_iax2.c:5616 iax2_poke_noanswer: Peer 'arlington' is now UNREACHABLE!
May 23 13:06:44 NOTICE[7176]: chan_iax2.c:5213 socket_read: Peer 'arlington' is now REACHABLE!
May 23 13:14:49 NOTICE[7176]: chan_iax2.c:5616 iax2_poke_noanswer: Peer 'arlington' is now UNREACHABLE!
May 23 13:14:59 NOTICE[7176]: chan_iax2.c:5213 socket_read: Peer 'arlington' is now REACHABLE!
May 23 13:17:56 NOTICE[5126]: chan_sip.c:5860 handle_response: Peer '6666' is now REACHABLE!
*Iax.conf**:*
[general]
;port=5036 ;I commented this out because I discovered it is hard coded anyway.
bindaddr=10.20.30.10
amaflags=default
accountcode=default
bandwidth=low
disallow=all
allow=gsm
jitterbuffer=no
;dropcount=3
;maxjitterbuffer=500
;maxexcessbuffer=100
;trunkfreq=20
tos=lowdelay
authdebug=no
register => username:[EMAIL PROTECTED] ;these are real values that I changed for security reasons
[arlington]
type = friend
context = local
callerid =
auth = plaintext
secret = password
;inkeys =
;outkey =
host = dynamic
;defaultip =
;accountcode =
qualify = yes
;mailbox =
trunk = yes
_______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
