CRE Extensions moved to a different controller

Amethyst - Advance Call Recording Solution(Trunk,Extension, VoIP and clientside) with Agent Quality Management and 3rd party integration SDK

Moderators: Leon van Heerden, Luanda_Junzi, Belinda Frick, Lee Hendricks

CRE Extensions moved to a different controller

Postby Leon van Heerden » Tue Jul 09, 2019 4:15 pm

If you have a problem with the Controller IP not changing on the CRE recording configuration, even though the extension has been moved to another controller. The CRE might have cached the extension's initial IP and it keeps using it.
We have seen this issue at Hosted sites, where there are many different controllers recorded through a few MBGs and the extension is re-purposed from one client on one controller to another client on another controller, but staying on the same MBG.
Restarting the CRE clears the cache and then the IP is picked up properly.
Leon van Heerden
Leon van Heerden
Posts: 330
Joined: Fri Oct 29, 2010 11:21 am
Location: Cape Town

Return to Amethyst

Who is online

Users browsing this forum: No registered users and 1 guest