Jump to content

Agent group opening many calls on phones (issue with 64.0)


chrispopp
 Share

Recommended Posts

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.

Settings.png

This example says 90 seconds, but I tried with 20 seconds.

Link to comment
Share on other sites

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?

Link to comment
Share on other sites

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:ⓘ

 

1.png

Link to comment
Share on other sites

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...