[tahiralmas]

No ICTCore extension could register on the ictcore SIP profile, so ATAs, fax machines and softphones never worked against a stock install. On the ICTFax 6.0 image every REGISTER got 403 Forbidden, even with the right password. There were three causes:

1. The SIP user was never written on create. DB::update stamps created_by with the session user, but Account::save never copied it back to the object. Extension::save then saw user_id 0 and deleted the user's directory file instead of writing it. The account only appeared after a second save.
2. The directory was linked outside any domain. The installers linked directory/ictcore.xml at directory/ level, where FreeSWITCH never looks up users. It now goes into directory/default/, inside the default domain.
3. Domain mismatch behind NAT. Devices register with the domain they were configured with, usually the public IP or a hostname. That never matches $${domain} on a cloud or NATed host. force-register-domain maps every registration onto the ICTCore domain.

Also:

• Demo users removed. The installers now delete the vanilla FreeSWITCH users 1000-1019. Their published password is 1234, and 1001/1234 registered on 5060.
• RTP range pinned. The Docker image now pins RTP to 16384-16484, the range it publishes. FreeSWITCH's default of 16384-32768 drops media at the Docker boundary once calls drift past 16484.

Tested on the ICTFax image, with a SIP client registering the way an ATA does:

	before	after
extension created the way the GUI does it (POST /accounts)	no SIP user written	written immediately
REGISTER, domain = server's own IP	403	200
REGISTER, domain = public IP / hostname	403	200
REGISTER, wrong password	403	403
demo user 1001 / 1234	200	403

After merging: existing installs need the directory/default link, the demo users removed and a reloadxml. Every existing extension also needs one save (or PUT /accounts/{id}) to write its user. The ICTFax and ICTDialer images pick this up via ICTCORE_REF (ictinnovations/ictfax#127, ictinnovations/ictdialer#60).