[asterisk-bugs] [JIRA] (ASTERISK-17523) Qualify for realtime peers does not work

[Trevor Peirce (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-17523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=202708#comment-202708 ] 

Trevor Peirce edited comment on ASTERISK-17523 at 2/7/13 2:01 PM:
------------------------------------------------------------------

I was about to create a new ticket but this looks like the same problem.

I use MySQL -> ODBC -> Asterisk Realtime for SIP peers.

Sometimes, Asterisk writes a 0 or -1 in the lastms column (presumably when a peer is offline or similar).

The next time Asterisk loads this peer it reports the status as UNKNOWN and never sends any probes to determine if the peer is up.

The workaround is to manually edit the database and replace lastms with a value of 1 or greater.  Prune the realtime peer, load it, and then Asterisk send the qualify packet and reports the peer as online once again.

This affects at least Asterisk 11.2.0 and 1.8.15.1.
                
      was (Author: trev):
    I was about to create a new ticket but this looks like the same problem.

I use MySQL -> ODBC -> Asterisk Realtime for SIP peers.

Sometimes, Asterisk writes a 0 or -1 in the lastms column (presumably when a peer is offline or similar).

The next time Asterisk loads this peer it reports the status as UNKNOWN and never sends any probes to determine if the peer is up.

The workaround is to manually edit the database and replace lastms with a value of 1 or greater.  Prune the realtime peer, load it, and then Asterisk send the qualify packet and reports the peer as online once again.
                  
> 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
>            Reporter: Maciej Krajewski
>            Severity: Minor
>         Attachments: full, 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
For more information on JIRA, see: http://www.atlassian.com/software/jira