chrispopp Posted November 20, 2019 Report Share Posted November 20, 2019 We are testing on 64.0 and it seems there's something wrong with the agent group. The agent group now opens a new call after every call duration. For example. Say someone calls into the agent group, and the stage duration is 20 seconds. It will ring for 20 seconds, add a new agent, and then it will show up as 2 calls the phone. After another 20 seconds, 3 calls are active, 20 seconds later, 4 calls, and so on... When picking up, it doesn't do anything. You just need to pick up the latest call in order for it to hear the person. So you need to go through all, and hangup until you reach the last call. The Active Calls list shows 1 call only. Was working fine in the older versions. This example says 90 seconds, but I tried with 20 seconds. Quote Link to comment Share on other sites More sharing options...
Support Posted November 21, 2019 Report Share Posted November 21, 2019 Can you tell us where exactly are you seeing the number of calls being increased? Because we tried with your setup and ours too, but we couldn't reproduce the issue on 64.0. The number of calls was always 1 on both the agents and in active calls list. And when we picked up either of the phones up, it stopped ringing. Maybe there's a redirection involved in your scenario? Quote Link to comment Share on other sites More sharing options...
chrispopp Posted November 21, 2019 Author Report Share Posted November 21, 2019 Did you let the phones ring over several ring durations? For example, let it ring 361 seconds in the above example, it will show 4 calls on my phones. I tried with a Snom and a Yealink. In the active calls lists it only shows 1... I checked that too. Quote Link to comment Share on other sites More sharing options...
Support Posted November 21, 2019 Report Share Posted November 21, 2019 You mentioned that you saw this happen every 20 secs to we let it ring for 40 something secs. Fine, we'll make it ring longer this time. And then try to pick the call. We have both Snom's here. Quote Link to comment Share on other sites More sharing options...
chrispopp Posted November 21, 2019 Author Report Share Posted November 21, 2019 My apologies, it doesn't seem to follow the ring durations. It's at exactly 30 seconds intervals. See attached screenshots. Here are some logs that look off: [8] 11:14:08.889 Hangup: Call 668 not foundⓘ [7] 11:14:08.889 lookup_index error: Call port index is 668ⓘ [8] 11:14:08.889 Last message repeated 3 timesⓘ [9] 11:14:08.889 Using outbound proxy sip:xx.xx.xxx.xxx:55714;transport=tls because of flow-labelⓘ [7] 11:14:08.889 47 callids pendingⓘ or [9] 11:13:32.800 Traffic from 163.172.207.104 ignored because of user-agentⓘ [9] 11:13:33.652 Resolve 121803: aaaa udp 110.111.111.111 49737ⓘ [9] 11:13:33.652 Resolve 121803: a udp 110.111.111.111 49737ⓘ [9] 11:13:33.652 Resolve 121803: udp 110.111.111.111 49737ⓘ [9] 11:13:34.662 Message repetition, packet droppedⓘ [9] 11:13:39.833 Last message repeated 2 timesⓘ [9] 11:13:39.833 Resolve 121806: udp 159.65.251.173 49789ⓘ [9] 11:13:41.326 Resolve 121808: aaaa udp 110.111.111.111 43083ⓘ [9] 11:13:41.326 Resolve 121808: a udp 110.111.111.111 43083ⓘ [9] 11:13:41.326 Resolve 121808: udp 110.111.111.111 43083ⓘ [9] 11:13:42.663 Message repetition, packet droppedⓘ [9] 11:13:46.674 Last message repeated 2 timesⓘ [7] 11:13:46.674 31 callids pendingⓘ [9] 11:13:46.674 Resolve 121809: aaaa udp 110.111.111.111 49737ⓘ [9] 11:13:46.674 Resolve 121809: a udp 110.111.111.111 49737ⓘ [9] 11:13:46.674 Resolve 121809: udp 110.111.111.111 49737ⓘ [9] 11:13:46.675 Resolve 121810: url sip:555@110.111.111.111:49737;line=eogked7iⓘ [9] 11:13:46.675 Resolve 121810: udp 110.111.111.111 49737ⓘ [9] 11:13:50.666 Message repetition, packet droppedⓘ [9] 11:13:54.948 Last message repeated 2 timesⓘ [9] 11:13:54.948 Resolve 121814: udp 159.65.251.173 29261ⓘ [8] 11:13:55.119 Last message repeated 8 timesⓘ [7] 11:13:55.119 Port 670: Clear last INVITEⓘ [5] 11:13:55.119 INVITE Response 408 Request Timeout: Terminate cc620b26@pbxⓘ [7] 11:13:55.119 lookup_index error: Call port index is 670ⓘ [8] 11:13:55.119 Hangup: Call 670 not foundⓘ [9] 11:13:55.120 Using outbound proxy sip:12.12.12.12:55714;transport=tls because of flow-labelⓘ [9] 11:13:55.120 Resolve 121816: url sip:555@110.111.111.111:49737;line=eogked7iⓘ [9] 11:13:55.120 Resolve 121816: udp 110.111.111.111 49737ⓘ [9] 11:13:55.121 Resolve 121818: url sip:555@110.111.111.111:49737;line=eogked7iⓘ [9] 11:13:55.121 Resolve 121818: udp 110.111.111.111 49737ⓘ [9] 11:13:55.121 Last message repeated 2 timesⓘ [7] 11:13:55.121 Port 672: Clear last INVITEⓘ [5] 11:13:55.121 INVITE Response 408 Request Timeout: Terminate 8ee95a84@pbxⓘ [7] 11:13:55.122 Port 673: Clear last INVITEⓘ [5] 11:13:55.122 INVITE Response 408 Request Timeout: Terminate be778a5a@pbxⓘ [7] 11:13:55.123 lookup_index error: Call port index is 672ⓘ [8] 11:13:55.123 Hangup: Call 672 not foundⓘ [9] 11:13:55.123 Using outbound proxy sip:159.65.251.173:49789;transport=udp because of flow-labelⓘ [9] 11:13:55.123 Resolve 121819: url sip:159.65.251.173:49789;transport=udpⓘ [9] 11:13:55.123 Resolve 121819: udp 159.65.251.173 49789ⓘ [5] 11:13:55.124 SIP Tx 159.65.251.173:49789:ⓘ Quote Link to comment Share on other sites More sharing options...
chrispopp Posted November 21, 2019 Author Report Share Posted November 21, 2019 Quote Link to comment Share on other sites More sharing options...
Support Posted November 21, 2019 Report Share Posted November 21, 2019 37 minutes ago, chrispopp said: it doesn't seem to follow the ring durations. It's at exactly 30 seconds intervals. So we retry this at every 30 secs now ? Instead of 20 or 361 secs that you mentioned earlier? Quote Link to comment Share on other sites More sharing options...
chrispopp Posted November 21, 2019 Author Report Share Posted November 21, 2019 Exactly. I had it set to 20, and it seemed that it was close enough. But i used a stop watch and it's every 30 seconds. Quote Link to comment Share on other sites More sharing options...
Support Posted November 21, 2019 Report Share Posted November 21, 2019 We replicated your agent group's setting here and everything is still the same. It works for us. We tried both 20 and 30 secs. You're sure you're not redirecting any of your extensions right? Quote Link to comment Share on other sites More sharing options...
chrispopp Posted November 21, 2019 Author Report Share Posted November 21, 2019 No redirections. Just checked. Are you testing on a Win64? Quote Link to comment Share on other sites More sharing options...
Support Posted November 21, 2019 Report Share Posted November 21, 2019 It's Debian64, but shouldn't make a difference though. Quote Link to comment Share on other sites More sharing options...
chrispopp Posted November 22, 2019 Author Report Share Posted November 22, 2019 I erased everything on the test machine and a fresh new install worked fine. Recovered a backup from 63.0.x (i dont remember) and it doesn't work. Maybe the update? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.