06-06-2022 08:33 AM
clusters involved in call flow
US, EMEA, SME cluster with ILS
issue: there is an extn(consider ex: 109000) setup as shared line on US cluster, that extn also has an RDP with 3 destinations towards EMEA(for e.g:123456), APAC and India cluster, the call to RDP is through a trunk in SME cluster, it is through the learned DN, When someone calls 109000 and if someone from EMEA with 123456 as shared line answers the call and hangs up the call is shown as "placed on hold"(if the calling party was a VC) for 5-7s before it is actually disconnected, if the calling party was an unified app (call would just show as connected before taking few seconds to hang up). To isolate it what i did is i disabled the RDP to EMEA and applied a fwd all from extn :109000 and then tested the same call flow and this time i wasn't placed on hold, so what i isolated is RDP at fault, but i need to now understand what is wrong with the RDP call flow scenario.
call flow
to US cluster extn 109000-> RDP to EMEA extn-> SME cluster-> SIP trunk-> EMEA CuCM
Solved! Go to Solution.
06-06-2022 10:41 AM
06-06-2022 09:10 AM
06-06-2022 09:34 AM
06-06-2022 09:44 AM
06-06-2022 10:41 AM
06-06-2022 10:43 AM
With Mobile Connect, ie remote destination or mobile identity, this is expected. The reason is that you can resume the call on another associated device, such as a desk phone.
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