[asterisk-bugs] [JIRA] (ASTERISK-24497) Hints change to Idle from InUse after sip reload.

[Krzysztof Chmielewski (JIRA)]

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

Krzysztof Chmielewski edited comment on ASTERISK-24497 at 11/24/14 4:06 PM:
----------------------------------------------------------------------------

Hey,
I'm sorry for taking me so many time to provide feedback.

At this point I cannot reproduce this problem for non real time configuration. 

In my production environment I am using pure real time configuration. All sip.conf, pears, hints, friends and dialplan is acquiring from data base.
For backedn i am using PostgreSQL 9.1.3 and odbc connector (unixODBC 2.2.11).

My table for sippeers is in sippeers.conf attachment. 


was (Author: kristoff):
Hey,
I'm sorry for taking me so many time to provide feedback.

At this point I cannot reproduce this problem for non real time configuration. 

In my production environment I am using pure real time configuration. All sip.conf, pears, hints, friends and dialplan is acquiring from data base.
For backedn i am using PostgreSQL 9.1.3 and odbc connector (unixODBC 2.2.11)

> Hints change to Idle from InUse after sip reload.
> -------------------------------------------------
>
>                 Key: ASTERISK-24497
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24497
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 11.10.0
>            Reporter: Krzysztof Chmielewski
>            Assignee: Krzysztof Chmielewski
>         Attachments: issue_24497.txt, sippeers.sql
>
>
> Hello,
> I've got two real time SIP accounts in my Astetisk. Every time after chan_sip reload I have noticed that hint state and queue member state for thous two accounts changes from InUse to Idle. Also there is manager event (ExtensionStante) informing that thous accounts change their states.
> Is this OK? 
> Scenario
> SIP_test001 calls to SIP_test002
> Hints:
> {code}
> core show hints
>     -= Registered Asterisk Dial Plan Hints =-
>                     cc1 at PBX              : Queue:cc1             State:Unavailable     Watchers  0
>                 test003 at PBX              : SIP/test003&Custom:t  State:InUse           Watchers  0
>                 test002 at PBX              : SIP/test002&Custom:t  State:InUse           Watchers  0
>                 test001 at PBX              : SIP/test001&Custom:t  State:Idle            Watchers  0
>                 test004 at PBX              : SIP/test004&Custom:t  State:Unavailable     Watchers  0
> {code}
> Queue:
> {code}
> queue show
> cc1 has 0 calls (max unlimited) in 'random' strategy (0s holdtime, 0s talktime), W:0, C:0, A:0, SL:0.0% within 0s
>    Members:
>       LOCAL/test002 at PBX/nb (ringinuse disabled) (realtime) (In use) has taken no calls yet
>       LOCAL/test003 at PBX/nb (ringinuse disabled) (realtime) (In use) has taken no calls yet
> {code}
> After chan_sip reload (after few sec)
> {code}
> queue show
> cc1 has 0 calls (max unlimited) in 'random' strategy (0s holdtime, 0s talktime), W:0, C:0, A:0, SL:0.0% within 0s
>    Members:
>       LOCAL/test002 at PBX/nb (ringinuse disabled) (realtime) (Not in use) has taken no calls yet
>       LOCAL/test003 at PBX/nb (ringinuse disabled) (realtime) (Not in use) has taken no calls yet
>    No Callers
> {code}
> and
> {code}
> core show hints
>     -= Registered Asterisk Dial Plan Hints =-
>                     cc1 at PBX              : Queue:cc1             State:Unavailable     Watchers  0
>                 test003 at PBX              : SIP/test003&Custom:t  State:Idle            Watchers  0
>                 test002 at PBX              : SIP/test002&Custom:t  State:Idle            Watchers  0
>                 test001 at PBX              : SIP/test001&Custom:t  State:Idle            Watchers  0
>                 test004 at PBX              : SIP/test004&Custom:t  State:Unavailable     Watchers  0
> {code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)