BlockList automatically deletes User Authentication accounts

1. Brekeke Product Name and Version:
3.6.3.0/454
2. Java version:
1.8.0_111
3. OS type and the version:
Windows server 2008
4. UA (phone), gateway or other hardware/software involved:

5. Your problem:
When migrating UA's from an old BSS towards this BSS 4 old UA's IP addresses got blocked by the blocklist feature. By adding the IP range to the allowed range in the filtering policy, the UA's were able to dial out, but could not be reached and they were not shown as registered. After checking the User Authentication files I discovered the UA's were deleted from the database. Is there a fix to prevent this from happening?

How did you migrate from old SIP Server to the 3.6.3.0?
Is the old SIP Server installation still running separately?

Hi Snuyzm,
I have downloaded the user authentication files and dialplans from the old BSS and imported these in the new BSS. The old BSS virtual machine was decommissioned and the license was migrated to the new BSS.

Have you tried to add these 4 users in the 3.6.3.0's [User Authentication] page manually?

Hi Harold, yes after discovering that the 4 accounts were deleted I manually added the 4 users back to the user authentication page and all is working fine. My point is that when BSS starts blocking IP addresses of UA's, it will also delete the accounts connected to these IP addresses from the User Authentication database. This is not documented anywhere and customers should be aware of this unexpected behaviour.

Since these 4 users were not listed in User Authentication database, the SIP Server couldn't confirm their validities. So the SIP server supposed that SIP packets sent from these IP address were malicious activities.
It is the reason why the SIP Server added them in the BlockList.

@Harold - my point is that these 4 UA's actually were listed in the user authentication database. They were delisted from this database when their IP adresses were blocked when the videophones for whatever reason could not register as should and the blocklist feature was activated.

Do/did you use non-English characters in these user names?

@Harold - unfortunately no non-English characters were used. After re-entry of exactly the same UA profiles in the User Authentication database all works fine, so there is no issue with characters. Given your questions I assume that you do not see a relationship between blocking UA's and automatically deleting the UA account data from the UA database.

I've checked it with the developer and confirmed that the BlockList function doesn't remove any users from the User Authentication database. These functions are running independently.

The only way to add/remove a user is from the Admintool.