 | 1 | изначальная версия редактировать | |
Всем привет. Столкнулся с такой проблемой: один member в очереди постоянно помечен как Busy. Пробовал отключать SIP клента, делал reload *. Но все равно, после того, как SIP клиент регистрируется на сервере, в статусе очереди он сразу становится Busy. Рестарт * пока не делал т.к. * работает под нагрузкой и можно только ночью это сделать.
localhost*CLI> queue show taxi-operators
taxi-operators has 5 calls (max unlimited) in 'random' strategy (39s holdtime, 41s talktime), W:0, C:16171, A:1601, SL:0.2% within 0s
Members:
SIP/110 with penalty 2 (Unavailable) has taken no calls yet
SIP/109 with penalty 2 (Unavailable) has taken no calls yet
SIP/108 with penalty 2 (Unavailable) has taken no calls yet
SIP/107 with penalty 2 (Busy) has taken 3341 calls (last was 24 secs ago)
SIP/106 with penalty 2 (Unavailable) has taken no calls yet
SIP/105 with penalty 2 (Unavailable) has taken 2930 calls (last was 16 secs ago)
SIP/104 with penalty 2 (Unavailable) has taken 2317 calls (last was 104 secs ago)
SIP/103 with penalty 2 (Unavailable) has taken no calls yet
SIP/102 with penalty 2 (Unavailable) has taken no calls yet
SIP/101 with penalty 1 (Busy) has taken 4648 calls (last was 7279 secs ago)
SIP/100 with penalty 1 (Unavailable) has taken 2935 calls (last was 513 secs ago)
Callers:
1. DAHDI/2-1 (wait: 0:47, prio: 0)
2. DAHDI/1-1 (wait: 0:44, prio: 0)
3. DAHDI/3-1 (wait: 0:36, prio: 0)
4. DAHDI/6-1 (wait: 0:10, prio: 0)
5. DAHDI/7-1 (wait: 0:05, prio: 0)
localhost*CLI> sip show peers
Name/username Host Dyn Forcerport ACL Port Status
100/100 (Unspecified) D 0 Unmonitored
101/101 10.0.0.12 D 5060 Unmonitored
102 (Unspecified) D 0 Unmonitored
103 (Unspecified) D 0 Unmonitored
104/104 (Unspecified) D 0 Unmonitored
105/105 10.0.0.108 D 5060 Unmonitored
106 (Unspecified) D 0 Unmonitored
107/107 10.0.0.110 D 5060 Unmonitored
108 (Unspecified) D 0 Unmonitored
109 (Unspecified) D 0 Unmonitored
110 (Unspecified) D 0 Unmonitored
111 (Unspecified) D N 0 UNKNOWN
1200 (Unspecified) D 0 Unmonitored
200/200 10.0.0.50 D 5060 Unmonitored
201/201 10.0.0.50 D 5062 Unmonitored
900 (Unspecified) D 0 Unmonitored
Проблемный member имеет номер 101. Как видно из статистики в очереди он занят, но последний звонок принял аж 7229 секунд назад. Может на * очередь как-то подвисла?
| | 2 | No.2 Revision редактировать |
Всем привет. Столкнулся с такой проблемой: один member в очереди постоянно помечен как Busy. Пробовал отключать SIP клента, делал reload *. Но все равно, после того, как SIP клиент регистрируется на сервере, в статусе очереди он сразу становится Busy. Рестарт * пока не делал т.к. * работает под нагрузкой и можно только ночью это сделать.
localhost*CLI> queue show taxi-operators
taxi-operators has 5 calls (max unlimited) in 'random' strategy (39s holdtime, 41s talktime), W:0, C:16171, A:1601, SL:0.2% within 0s
Members:
SIP/110 with penalty 2 (Unavailable) has taken no calls yet
SIP/109 with penalty 2 (Unavailable) has taken no calls yet
SIP/108 with penalty 2 (Unavailable) has taken no calls yet
SIP/107 with penalty 2 (Busy) has taken 3341 calls (last was 24 secs ago)
SIP/106 with penalty 2 (Unavailable) has taken no calls yet
SIP/105 with penalty 2 (Unavailable) has taken 2930 calls (last was 16 secs ago)
SIP/104 with penalty 2 (Unavailable) has taken 2317 calls (last was 104 secs ago)
SIP/103 with penalty 2 (Unavailable) has taken no calls yet
SIP/102 with penalty 2 (Unavailable) has taken no calls yet
SIP/101 with penalty 1 (Busy) has taken 4648 calls (last was 7279 secs ago)
SIP/100 with penalty 1 (Unavailable) has taken 2935 calls (last was 513 secs ago)
Callers:
1. DAHDI/2-1 (wait: 0:47, prio: 0)
2. DAHDI/1-1 (wait: 0:44, prio: 0)
3. DAHDI/3-1 (wait: 0:36, prio: 0)
4. DAHDI/6-1 (wait: 0:10, prio: 0)
5. DAHDI/7-1 (wait: 0:05, prio: 0)
localhost*CLI> sip show peers
Name/username Host Dyn Forcerport ACL Port Status
100/100 (Unspecified) D 0 Unmonitored
101/101 10.0.0.12 D 5060 Unmonitored
102 (Unspecified) D 0 Unmonitored
103 (Unspecified) D 0 Unmonitored
104/104 (Unspecified) D 0 Unmonitored
105/105 10.0.0.108 D 5060 Unmonitored
106 (Unspecified) D 0 Unmonitored
107/107 10.0.0.110 D 5060 Unmonitored
108 (Unspecified) D 0 Unmonitored
109 (Unspecified) D 0 Unmonitored
110 (Unspecified) D 0 Unmonitored
111 (Unspecified) D N 0 UNKNOWN
1200 (Unspecified) D 0 Unmonitored
200/200 10.0.0.50 D 5060 Unmonitored
201/201 10.0.0.50 D 5062 Unmonitored
900 (Unspecified) D 0 Unmonitored
Проблемный member имеет номер 101. Как видно из статистики в очереди он занят, но последний звонок принял аж 7229 секунд назад. Может на * очередь как-то подвисла?
queues.conf
[taxi-operators]
timeoutpriority = conf
; How long call to member
timeout = 15
; Time switching to another menber
retry = 5
;How often spek periodic message
periodic-announce-frequency=15
;Path to periodic message
periodic-announce = ru/queue-periodic-announce
;Music class
musicclass = mymoh
; generate events
eventwhencalled = yes
;Strategy of calls
strategy = random
; Recording
monitor-format = wav
monitor-type = MixMonitor
; Don`t send calls to busy operators
ringinuse = no
defaultrule=rule057
;Queue members
member => SIP/100,1
member => SIP/101,1
member => SIP/102,2
member => SIP/103,2
member => SIP/104,2
member => SIP/105,2
member => SIP/106,2
member => SIP/107,2
member => SIP/108,2
member => SIP/109,2
member => SIP/110,2
queuerules.conf
[rule057]
penaltychange => 30,2,+1 ; 30 seconds into the call increase the QUEUE_MAX_PENALTY by 3, no change to QUEUE_MIN_PENALTY
Проект компании "АТС Дизайн"
Asterisk® и Digium® являются зарегистрированными торговыми марками компании
Digium, Inc., США.
IP АТС Asterisk распространяется под лицензией
GNU GPL.