10-29-2014 04:01 PM - edited 03-20-2019 08:20 PM
Hi guys,
Workaround mentioned in above bug is to manually create media channel group. As per work around I have created
another group with required number of channels. Our license is for 100 ivr ports. Looking at the mivr logs, I can still see that it is trying to use default media group. How can I get application to use newly created media group?
Group ID ![]() | Description ![]() | Channels ![]() | Copy | Delete | Refresh | |
---|---|---|---|---|---|---|
![]() | 1 | CMT Auto#1 | 50 | ![]() | ![]() | ![]() |
![]() | 0 | Default | 0 | ![]() | ![]() | ![]() |
MIVR Logs -
114431: Oct 29 17:13:07.218 EST %MIVR-SS_TEL-5-CTIPG_ROUTE_EVENT:CTI Port Group route event: Route Session=[19008:INTERNAL:1/(P1-CCX-JTAPI_1_1) GCID=(2,1202)->INVALID]->DISCONNECTED,Route Address=19008,Failure reason=CTI accept timer expires after 4025 ms, end route connection,Exception=com.cisco.lang.InterruptedException: No idle channels available in group 'Cisco Media Channel Group #0'; nested exception is:
Workaround:
Manually create a Media Channel Group with the appropriate number of channels.
Collect MADM logs with LIB_LICENSE, ADM_CFG, and LIB_CFG debugging enabled to
determine why the default media group was created with 0 channels.
Thanks
02-25-2020 07:09 AM
Very long time ago, but did you find a solution?
JH
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide