[asterisk-bugs] [JIRA] (ASTERISK-17523) Qualify for realtime peers does not work
Trevor Peirce (JIRA)
noreply at issues.asterisk.org
Mon Feb 10 12:09:05 CST 2014
[ https://issues.asterisk.org/jira/browse/ASTERISK-17523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=215053#comment-215053 ]
Trevor Peirce edited comment on ASTERISK-17523 at 2/10/14 12:07 PM:
--------------------------------------------------------------------
The problem I observed affects only static realtime peers with qualify enabled.
If a peer goes offline, Asterisk writes -1 as lastms. If a peer did not have qualify enabled, but is subsequently enabled, Asterisk will have 0 as lastms.
Upon a restart of Asterisk, it'll load the peer with lastms of either 0 or -1.
This prevents Asterisk from sending an initial probe to determine if the peer is online. If a call is destined to this peer, it instantly refuses as it believes the peer is perpetually offline.
The most recent patch I uploaded includes more logic to prevent peer poking on expired dynamic peers but to always initiate the poke process for static realtime peers.
was (Author: trev):
The problem I observed affects only static realtime peers with qualify enabled.
If a peer goes offline, Asterisk writes -1 as lastms. If a peer did not have qualify enabled, but is subsequently enabled, Asterisk will have 0 as lastms.
Upon a restart of Asterisk, it'll load the peer with lastms of either 0 or -1.
This prevents Asterisk from sending an initial probe to determine if the peer is online. If a call is destined to this peer, it instantly refuses as it believes the peer is perpetually offline.
The most recent patch I uploaded includes more logic to prevent peer poking on expired peers but to always initiate the poke process for static realtime peers.
> Qualify for realtime peers does not work
> ----------------------------------------
>
> Key: ASTERISK-17523
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-17523
> Project: Asterisk
> Issue Type: Bug
> Components: Channels/chan_sip/DatabaseSupport
> Affects Versions: 1.8.20.1, 11.2.1
> Reporter: Maciej Krajewski
> Assignee: Trevor Peirce
> Severity: Minor
> Attachments: full, realtime fix 11.7.0.txt, sip.conf
>
>
> Every time when I run command "sip show peers", every peer has status UNKNOWN, below is a sample output of the peer (jamicque) and friend (test001 who registers to Asterisk).
> sip show peers
> Name/username Host Dyn Nat ACL Port Status Realtime
> jamicque/jamicque 213.218.116.66 5060 UNKNOWN Cached RT
> test001/test001 10.0.0.2 D N 5060 OK (5 ms) Cached RT
> In additional info is the real-time configuration of test001 and jamicque
> ****** ADDITIONAL INFORMATION ******
> "id","name","accountcode","amaflags","callgroup","callerid","canreinvite",
> "context","defaultip","dtmfmode","fromuser","fromdomain","fullcontact","host",
> "insecure","language","mailbox","md5secret","nat","deny","permit","mask",
> "pickupgroup","port","qualify","restrictcid","rtptimeout","rtpholdtimeout",
> "secret","type","defaultuser","disallow","allow","musiconhold","regseconds",
> "ipaddr","regexten","cancallforward","t38pt_udptl","setvar","id_sip_account",
> "id_foreign_sip_account","call-limit","sendrpid","regserver","useragent",
> "lastms"
> "1","test001","test001","\N","\N","*","no ","CALLEX","\N","\N","\N","\N",
> "sip:test001 at 10.0.0.2:5060^3Brinstance=198163cbdf0a1fbf^3Btransport=UDP",
> "dynamic","\N","\N","11 at CALLEX","\N","yes","\N","\N","\N","\N","5060","yes",
> "\N","\N","\N","test001","friend","test001","all","alaw;g729","\N",
> "1299597595","10.0.0.2","\N","yes","\N","\N","1","\N","9999","no","\N",
> "Zoiper rev.11137","5"
> "14","jamicque","jamicque","\N","\N","\N","no ","CALLEX","\N","\N","\N","sip.freeconet.pl","\N","213.218.116.66",
> "invite,port","\N","\N","\N","no","\N","\N","\N","\N","5060","yes","\N","\N",
> "\N","xxxxxxx","peer","jamicque","all","g729;alaw","\N","0","213.218.116.66",
> "\N","yes","\N","\N","\N","6","9999","no","\N","\N","\N"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the asterisk-bugs
mailing list