Calling Enterprise Ring Group Locks Gateway When Channels Set To 0

[GoogleCodeExporter]

What steps will reproduce the problem?

0. Create a gateway and outbound route, set channels to "0" in the gateway 
setup.
1. Create an extension that has an external phone (that uses the above outbound 
route) set to ring at the same time as a desk-phone via follow me.
2. Add the user to a ring-group with an Enterprise strategy and call the 
ring-group extension.
3. Hang up the call and then attempt to make an outbound call (any number) from 
the same tenant, it will not go through and will time out. You must press 
"reload XML" in order to place outbound calls via that gateway again. Internal 
calls work, and calls out of another Gateway also work.

What is the expected output? What do you see instead?

Should be able to make an outbound call out of the same gateway after calling a 
ring group. Instead, after calling the ring-group and it hitting the external 
phone (which works fine the first time) and hanging up, all subsequent calls 
sent to the gateway get stuck with this error in the log: "Locked, Waiting on 
external entities", eventually the INVITE from the phone will time-out. I 
checked my SBC logs which handle the trunking, it doesn't see any invites being 
sent from Fusion after it locks up.

What version of the product are you using? On what operating system?

I have tested this on both 3.7.1 and 3.6.3 on Ubuntu 12.04 (both were fresh 
installs, installed via the script), exact same issue on both. 

Please provide any additional information below.

Setting the "channels" variable in the gateway to anything other than 0 
resolves the issue. I set it to 10 and everything worked fine. I was thinking 
having it set to 0 was OK.

Original issue reported on code.google.com by blake.d....@gmail.com on 29 Jan 2015 at 2:20

[GoogleCodeExporter]

I resolved this issue, it was an issue with how I set up the SIP profile with 
my SBC. Using the "Aggressive NAT detection" parameter on the profile my SBC 
(which is internal and not behind NAT) was connected to would cause calls to 
fail periodically. 

Original comment by blake.d....@gmail.com on 19 Mar 2015 at 6:53

[GoogleCodeExporter]

Glad you were able to resolve the problem and thanks for reporting what you did 
to fix it.

Original comment by markjcrane@gmail.com on 21 Apr 2015 at 6:44

• Changed state: Done