Genesys CTI User Forum
Genesys CTI User Forum => Genesys CTI Technical Discussion => Topic started by: eduardosaito on January 19, 2015, 07:54:21 PM
-
Hi there,
Iīve faced some issues in our environment recently outbound on sip.
During day the OCS doesnīt dial anymore showing the "Unable to initiate outbound dialing" in the log.
And I see a message "SIPDialer::TrunkGroup[Resources (DBID=XXXX)]::Total ports 6000, available ports 0"
When talking to our Genesys team here, he said that in Sip log shows "X-Genesys-gvp-tenant-ports: Resources/5982/6000" and they say that the OCS should keep dialing cause they didnīt see the OCS log before.
My doubt is how does this SIPDialer ports work? Is there any addition configuration we should implement so the OCS should free the ports after using them?
thanks in advance.
-
OCS should dial as long as your SIP Trunk allows. So on SIP server which is the capacity parameter value?
Then on the Trunk Group also, any special value? Check in Tserver guide the chapter for Trunk Capacity Control
Also somewhere SIP server must have a limit, maybe you need to load balance
-
Genesys is installing all new environment solution (we were still working with TServer 7.x and all other products on 7.x releases plus Alcatel pbx tdm solution) , so now we are migrating to a whole new "world" to us so i am still kinda lost here ...
We are now going with Audiocodes + Genesys + Verint.
The Genesys guy told me that the port limitation is from Media Server (15 media servers with 400 ports each) and that the RM asks the media servers about ports availability.
Now that you answered me, i tried to set the "capacity" option on the trunk group to 6000.
And now it works smoothly =)
I donīt know if there can be any drawback by changing this but i can see clearly in the ocs logs that the ports now are being managed correctly.
Thanks for the help (once and once again) !
-
Outbound shouldn't be affected by RM. If you are using gvp for proactive contact that is another history but with enough servers it should work
-
Cav,
I believe that Eduardo is having the new dialler architecture (OCS + Media Server, previously called proactive contact only) rolled out.
In this case OCS 'sees' a resource group of type 'outbound' , made of N+1 Media Servers, via a trunk group, hence the need to set the capacity equal to the overall number of ports available across all Media Servers dedicated to the outbound solution.
Fra
-
just to close the topic, answer from Genesys US said that it was caused due an issue in our sip server version where there was a mismatch from sip and he didnīt receive the ports available after outbound used it, so it became a countdown after ocs application started.
Now we got sip server ver 8.1.101.54 and itīs fixed.
Thanks for the help guys =)
-
Eduardo, We have the same setup here; AudioCodes as GW (m3k), SIP Server, OCS and Verint v11 for recording. We have 36 MCPs with 2 pair of HA RM. If you or I have questions/concerns it could be interesting to exchange on some topics.
We have an annex on our Switches for OCS (and some other campaign options at tenant level), but only to limit the rate (dialing_rate_limit). I don't think there's any other options to limit port utilization on Trunk DN.
Do you know what was the fix ? (it intrigues me)
-
Trunk has Capacity Control
What is your issue?