[asterisk-bugs] [JIRA] (ASTERISK-28669) chan_sip: Device states lost when sip reload
Kevin Harwell (JIRA)
noreply at issues.asterisk.org
Fri Jan 3 16:27:25 CST 2020
[ https://issues.asterisk.org/jira/browse/ASTERISK-28669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249241#comment-249241 ]
Kevin Harwell commented on ASTERISK-28669:
------------------------------------------
So I wasn't able to duplicate this exactly, but I am seeing similar type problems with device state, and _chan_sip_ with realtime. In my case after issuing the "sip reload" it still maintained the "Ring+Inuse" state. However, after terminating the second call (the one that was currently "ringing" the agent) the device state changed to "Unavailable" instead of back to "InUse".
After first call to agent (Note, only sip endpoints are configured in realtime. The queues I used the config file):
{noformat}
*CLI> core show hints
-= Registered Asterisk Dial Plan Hints =-
101 at default : SIP/101 State:InUse Presence:not_set Watchers 0
_. at default : ${TECH}/{$EXTEN} State:Unavailable Presence: Watchers 0
----------------
- 2 hints registered
*CLI> queue show queue
queue has 0 calls (max unlimited) in 'leastrecent' strategy (1s holdtime, 0s talktime), W:0, C:0, A:0, SL:0.0% within 0s
Members:
101 (SIP/101) with penalty 1 (ringinuse enabled) (in call) (In use) has taken no calls yet
No Callers
{noformat}
After second call:
{noformat}
*CLI> core show hints
-= Registered Asterisk Dial Plan Hints =-
101 at default : SIP/101 State:InUse&Ringing Presence:not_set Watchers 0
_. at default : ${TECH}/{$EXTEN} State:Unavailable Presence: Watchers 0
----------------
- 2 hints registered
*CLI> queue show queue
queue has 1 calls (max unlimited) in 'leastrecent' strategy (1s holdtime, 0s talktime), W:0, C:0, A:0, SL:0.0% within 0s
Members:
101 (SIP/101) with penalty 1 (ringinuse enabled) (in call) (Ring+Inuse) has taken no calls yet
Callers:
1. SIP/103-00000008 (wait: 0:10, prio: 0)
{noformat}
After sip reload:
{noformat}
*CLI> sip reload
*CLI>
*CLI> core show hints
-= Registered Asterisk Dial Plan Hints =-
101 at default : SIP/101 State:InUse&Ringing Presence:not_set Watchers 0
_. at default : ${TECH}/{$EXTEN} State:Unavailable Presence: Watchers 0
----------------
- 2 hints registered
*CLI> queue show queue
queue has 1 calls (max unlimited) in 'leastrecent' strategy (1s holdtime, 0s talktime), W:0, C:0, A:0, SL:0.0% within 0s
Members:
101 (SIP/101) with penalty 1 (ringinuse enabled) (in call) (Ring+Inuse) has taken no calls yet
Callers:
1. SIP/103-00000008 (wait: 0:10, prio: 0)
*CLI> core show hints
-= Registered Asterisk Dial Plan Hints =-
101 at default : SIP/101 State:InUse&Ringing Presence:not_set Watchers 0
_. at default : ${TECH}/{$EXTEN} State:Unavailable Presence: Watchers 0
----------------
- 2 hints registered
{noformat}
After second call termination:
{noformat}
*CLI> core show hints
-= Registered Asterisk Dial Plan Hints =-
101 at default : SIP/101 State:Unavailable Presence:not_set Watchers 0
_. at default : ${TECH}/{$EXTEN} State:Unavailable Presence: Watchers 0
----------------
- 2 hints registered
*CLI> Really destroying SIP dialog '19ca05ea71804746086d55eb3cc2ec6d at 10.24.20.47:5060' Method: INVITE
core squeue show queue
queue has 0 calls (max unlimited) in 'leastrecent' strategy (1s holdtime, 0s talktime), W:0, C:0, A:1, SL:0.0% within 0s
Members:
101 (SIP/101) with penalty 1 (ringinuse enabled) (in call) (Unavailable) has taken no calls yet
No Callers
{noformat}
So issuing the reload, and then hanging up caused an unwanted device state for me.
> chan_sip: Device states lost when sip reload
> --------------------------------------------
>
> Key: ASTERISK-28669
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-28669
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Channels/chan_sip/General
> Affects Versions: 13.26.0, GIT, 16.6.0
> Reporter: cagdas kopuz
> Assignee: Unassigned
> Attachments: asterisk-debuglog.txt, asterisk logs.txt, realtime.txt
>
>
> Device states of agent lost when sip reload and after second call came same agent. After that, agent status forgot first call state and turn to second call's state. But first call still same states. By the way, queues' member states also changed. Log is attached.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list