Thanks Harald,
I spent some more time on this today, it looks like you can initiate the connection from the BSC to the CBC or the other way around,
I worked out a basic config on OsmoCBC and OsmoBSC (going for BSC initiating the connection to CBC):
OsmoCBC Config:
cbc
unknown-peers accept
And the config on OsmoBSC:
cbc
remote-ip 10.0.1.252
remote-port 48049
no listen-port
Unfortunately when the BSC connects to the CBC (abridged):
<0000> cbsp_server.c:140 r=10.0.1.201:36667<->l=10.0.1.252:48049: Accepting unknown CBSP peer 10.0.1.201:36667
<0000> cbsp_server.c:153 r=10.0.1.201:36667<->l=10.0.1.252:48049: New CBSP client connection
<0000> cbsp_server.c:154 CBSP-SERVER[0x55e569d983c0]{INIT}: Received Event RESET.cmd
<0000> cbsp_server_fsm.c:203 CBSP-SERVER[0x55e569d983c0]{RESET_PENDING}: Event Rx Restart not permitted
<0000> cbsp_server_fsm.c:206 r=10.0.1.201:36667<->l=10.0.1.252:48049: unknown/unhandled RESET COMPLETE
Segmentation fault (core dumped)
After that the connection is dropped and the CBC halts,
So I tried it in reverse, on the CBC I set it up to connect to a remote BSC and plugged in the details of the BSC, and on the BSC I setup a CBC listener IP/port, but wasn't seeing any traffic originating from the CBC; I'm not sure if the CBC needs a REST request before it'll establish the connection, I got some way towards working out what the JSON encoding should be from the source code but I'm no good with C.
Any pointers would be greatly appreciated,
Cheers,
Nick