Found the IP address of the clans being used for the SGs. Did ' list usage ip-address <x.x.x.x> ' on the clan boards that are involved in both CMs to see which SGs were being used for the clans. Also did a ' list usage signal-group <SG#> ' to verify SG was using the correct TG. In this case, one of the 3 Signal Groups (SG) was causing this failure. All SGs matched end to end but in far end CM where the Cisco Unity vm is located, the corresponding SG of the failed call was using a different Trunk Group (TG) association, thus sending the call to an invalid location which replied with the 'no cir/chan avail' error.