Showing results for 
Search instead for 
Did you mean: 

250 sessions limit when using LGW with Wx Contact Centre

Level 1
Level 1

newbie to WxCC ... trying to understand the 250 sessions max. limit as we are planning to use LGW with Wx Contact centre. Below is pretty much how our setup would be like .. CUBE will be using standard internet connection behind NAT.  


Now for an active agent call - I understand there will be 1 session active between CUBE to Wx CC and another session from Wx CC to the agent....I've bundled them together (2 and 3) in the picture below .. from Wx CC perspective is it considered 1 session out of the 250 limit ? or is it 2 sessions out of the 250 limit ? I understand there are two separate sessions here but trying to understand from WxCC perspective when it takes the 250 limit into account.

Note there will be 2 CUBEs (1 in each DC) so all too possible for 1st session (PSTN => CUBE => WxCC) to be on one CUBE and other session (WxCC => CUBE ==> Agent MS Teams) to be on the 2nd CUBE ... btw just realizing as I'm typing whose holding the session together if both sessions are on different CUBEs ? CUBE2 has no means of knowing CUBE1 has an active session for that same call. thanks. 

1 Accepted Solution

Accepted Solutions


Hi again,

My opinion is, that 1 "complete" call (1 inbound to WxCC and 1 outbound to the agent) counts as 2 sessions.
So if the limit is 250 sessions, you could have 125 "complete" calls.
The reason is, that the media will always be hairpinned in WxCC => the inbound session and the outbound session will never be tied together, like in a normal SIP dialog => therefore both call legs are separate sessions.

To your last paragraph:
It doesn't matter, if both CUBEs see each other or not, because as written above, both call legs are completely independent of each other. If the inbound call to WxCC is routed via CUBE 1, the call can be routed out from WxCC via CUBE 2 and vice-versa.

"whose holding the session together if both sessions are on different CUBEs ?" => WxCC, as it always hairpins the call => there will always be the loop which you have drawn: 1 --> 2 --> 3 --> 4

View solution in original post