I ran into some really strange behavior with CCA 2.2.1 this past week while adding an SA520 to an existing UC520 installation. The UC520, on it's own, was working perfectly with inbound and outbound SIP trunk calls prior to the installation of the SA520. On installation of the SA520, and by following the Technical lab to accomplish this, the "CCA_SIP_SOURCE_GROUP" was somehow recreated on the UC520. The changes that I made on the UC520 included the deletion of NAT, the deletion of the Firewall, configuring the system to automatically select G.729 instead of G.711 including reregistration of the transcoder, and changing the outbound dialing rules to select PSTN before SIP in most cases. Something in one of these commands appears to reissue the command which also recreates the CCA_SIP_SOURCE_GROUP. By the time I realized what was going on, I was unable to recreate it exactly, so I am still unaware of which command does it. Perhaps somebody else here has seen this behavior and can weigh in on the issue? This was especially troubling, and difficult to trace because it is our standard operating procedure to remove this command after creating the SIP trunk initially, and I had done this on the UC520 several times during that period. Sometimes the UC520 showed that the source group did not exist, and sometimes it did.
I have another almost identical setup in at a new site, so I will try to identify what is causing this. If anybody already knows, however, I would appreciate the heads up.