AMS module registration persistently fails in test bench

[wypoch]

Even though the ams-sana test suite passes, the modules never appear to successfully register. See the folllowing excerpt from the ION log:

[2026/04/21-05:08:59] [?] parseSocketSpec: Empty or NULL socketSpec: 
[2026/04/21-05:08:59] [i] Configuration server is running.
[2026/04/21-05:08:59] [i] Starting daemon's AAMS module.
[2026/04/21-05:08:59] [i] Registrar is running.
[2026/04/21-05:08:59] [?] parseSocketSpec: Empty or NULL socketSpec: 
[2026/04/21-05:08:59] [?] parseSocketSpec: Empty or NULL socketSpec: 
[2026/04/21-05:08:59] [?] parseSocketSpec: Empty or NULL socketSpec: 
[2026/04/21-05:08:59] [?] parseSocketSpec: Empty or NULL socketSpec: 
[2026/04/21-05:08:59] [?] No registrar for this cell.
[2026/04/21-05:08:59] at line 3476 of ams/library/libams.c, Can't locate registrar.
[2026/04/21-05:08:59] at line 3669 of ams/library/libams.c, Can't register module.
[2026/04/21-05:08:59] at line 4353 of ams/library/libams.c, Registration failed. (Can't register.)
[2026/04/21-05:08:59] [i] DGR access point has been closed.
[2026/04/21-05:08:59] [i] DGR access point has been closed.
[2026/04/21-05:09:13] [i] parseSocketSpec: Parsed: @:2357
[2026/04/21-05:09:13] [?] parseSocketSpec: Empty or NULL socketSpec: 
[2026/04/21-05:09:13] [?] parseSocketSpec: Empty or NULL socketSpec: 

This issue dates back to at least ION-DTN versions 4.1.4 and 4.1.3. It appears modules can send some messages back and forth without being successfully registered. When modules attempt to register, they are met with a MAMS type 3 response (REJ_CELL_FULL). This does not invalidate the tests, but it does limit the spectrum of MAMS messages sent/received by modules.