gdixon Posted January 5, 2015 #1 Share Posted January 5, 2015 Hi, I have noticed that when two calls enter the queue at exactly the same time all calls get stuck and do not deliver to any agents. Is this a known issue? Thanks Regards Graham Link to comment Share on other sites More sharing options...
Tom Wellige Posted January 5, 2015 #2 Share Posted January 5, 2015 Hi Graham, no, I hear this problem the first time. Are you on the latest version of the queue (v2.1 Beta 2)? If you are able to reproduce the problem you could help me fixing it by providing me with the server trace file that includes this situation. Tom. Link to comment Share on other sites More sharing options...
gdixon Posted January 5, 2015 Author #3 Share Posted January 5, 2015 Hi Tom, Yes I am on the latest version, I will replicate this issue tomorrow morning and send you the traces. Cheers Link to comment Share on other sites More sharing options...
Tom Wellige Posted January 5, 2015 #4 Share Posted January 5, 2015 Please zip them and attach the file to your answer here. By clicking on "More Reply Options" you will get the extended reply editor which comes with an "Attach Files" option. Link to comment Share on other sites More sharing options...
gdixon Posted January 5, 2015 Author #5 Share Posted January 5, 2015 8:00:32Call ID: 4244742448 8:13:40 Call ID44102 44101 I cannot upload the traces as they are 2mb and the limit on here is 1mb Is there another way I can upload the traces? Thanks Regards Graham Link to comment Share on other sites More sharing options...
Tom Wellige Posted January 5, 2015 #6 Share Posted January 5, 2015 Even after you zipped them? Just open the trace in a text editor and delete everything before the relevant time stamp. Save it and zip it again. That should do the trick. Link to comment Share on other sites More sharing options...
Tom Wellige Posted January 5, 2015 #7 Share Posted January 5, 2015 As I have increased the storage for the forum the other day I have just increased the upload quota from 1 to 3 MB per registered user. So your original zip file should work now :-) Link to comment Share on other sites More sharing options...
gdixon Posted January 5, 2015 Author #8 Share Posted January 5, 2015 8:00:32Call ID: 4244742448 Link to comment Share on other sites More sharing options...
gdixon Posted January 5, 2015 Author #9 Share Posted January 5, 2015 8:13:40 Call ID44102 44101 Link to comment Share on other sites More sharing options...
Tom Wellige Posted January 5, 2015 #10 Share Posted January 5, 2015 Hi Graham, for me this looks like it has nothing to do with the Open Queue but with your setup. From 08:00:23 on all new incoming calls are rejected because there are not free channels available. Is it possible that you simply reached the maximum amount of configured/licensed voice channels? Link to comment Share on other sites More sharing options...
gdixon Posted January 5, 2015 Author #11 Share Posted January 5, 2015 Hi Tom, Nope these calls have already been delivered to the System and I can see them in the open queue webpage. They get stuck on waiting and nothing in the queue goes to alerting. This is a very busy queue. Thanks Regards Graham Link to comment Share on other sites More sharing options...
Tom Wellige Posted January 5, 2015 #12 Share Posted January 5, 2015 I don't know what happens on your system, but it definitely can't be the queue.As I wrote, from 08:00:23 on 99% of all newly incoming calls (3889!!!) are rejected with "no channel available". This doesn't happen before.ALL scripts of all current calls in the queue stop doing anything from 08:01:31 till 08:13:34. So for 12 minutes there is complete silence in the traces for these calls. After that some timers get fired and the server disconnects all the calls. What ever happens at eight o'clock on your system, it completely blocks your SwyxWare!!! This has nothing to do with two calls coming in more or less simultaneously. In fact they are 500 ms separated from each other and for both the queue gets properly initiated. The first call ends up at position 19 in the queue, the second call at position 20. A minute later they reached positions 16 and 17 and then the entire system gets blocked for 12 minutes. But as new calls get already blocked before the cause of the problem must be located also before. So, this is not an OQ problem, but something else that messes up your SwyxWare. For further analysis you should take a look into the event logs if you find anything in there that happens at the same time. Tom. Link to comment Share on other sites More sharing options...
Tom Wellige Posted January 6, 2015 #13 Share Posted January 6, 2015 Graham, I thought a little bit about this situation and is it by any chance possible that you have an open SIP port into the internet and facing a DOS attack? Actually nearly 4000 calls within a few minutes seems a little bit "much". And that's just the number of calls that made it to the server. As it got stuck the number might be even higher. Link to comment Share on other sites More sharing options...
gdixon Posted January 6, 2015 Author #14 Share Posted January 6, 2015 Hi Tom, No, I have ran a wireshark and the only SIP traffic hitting the server is from the correct SIP provider. This has happened again this morning. When these two calls come in at exactly the same time. these calls and the calls after it get stuck until I manually press the up arrow button to push them through - they then go to the alerting status and the queue continues to flow as normal. Thanks Regards Graham Link to comment Share on other sites More sharing options...
Tom Wellige Posted January 6, 2015 #15 Share Posted January 6, 2015 Well, that doesn't change what I saw in the traces. Especially point number 2 is a clear sign that there is something else happening on your machine at that time. I have never seen a server trace before where the call routing literally halts for 12 minutes without doing anything in between. I see no chance that this is connected to the OQ at all. So I am afraid I can't help in this case. Do you have a routing configuration problem in your SwyxWare? All those numerous calls come from and go to the same number actually... Regards, Tom Link to comment Share on other sites More sharing options...
gdixon Posted January 6, 2015 Author #16 Share Posted January 6, 2015 Just happened again. Please see attached print screen - this is how they get stuck. Thanks Regards Graham Link to comment Share on other sites More sharing options...
gdixon Posted January 6, 2015 Author #17 Share Posted January 6, 2015 Tom, Just to add to this - I can replicate this issue at will by calling in to the queue from two phones at exactly the same time. I have looked at the open queue database - the calls are in there and they are stuck on status ID 1(Waiting). If we manually change one of my stuck calls to status ID 2(Alerting) all calls continue to flow as normal. Thanks Link to comment Share on other sites More sharing options...
Tom Wellige Posted January 6, 2015 #18 Share Posted January 6, 2015 I just added this problem to the bug tracker: Bug #000009: Two Simultaneously Incoming Calls Stuck The Queue http://www.swyx-forum.com/index.php/tracker/issue-9-two-simultaneously-incoming-calls-stuck-the-queue/ Link to comment Share on other sites More sharing options...
gdixon Posted March 11, 2015 Author #19 Share Posted March 11, 2015 Hi Tom, Just been having a think on how we can get round it. At present there is an DTMF Chart that answers the call then it is forwarded into the queue based on what option then press through a connect to with proceed with destination call routing ticked. Is there anyway we can delay the call forwarding into the connect to with the use of persistent variables? Would it be possible to hold the call before it enters the queue for a random amount of time? Cheers Link to comment Share on other sites More sharing options...
Tom Wellige Posted March 12, 2015 #20 Share Posted March 12, 2015 Something like would be possible (some how), but you could still end up in the same situation. You would just make your script more complicated... The problem is really in the structure OQ currently stores/handle the current position in the queue. This needs to be changed. I am quite busy in my spare time these days so I can't promise anything when it will be fixed. Sorry. Link to comment Share on other sites More sharing options...
Most Valued User Remco Posted May 21, 2015 Most Valued User #21 Share Posted May 21, 2015 Just install iQueue ;o)iQueue can handle 2 incommimng calls at the same time. Both calls will be handled simultaniously to the members. Technically there is always one call earlier. This call locks one member and dilivers the call and the second call will be delivered to an other member, according the distribution type set. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.