_onFeatureServerTransfer Refer not handled correctly.

[Megamuch]

Scenario:

1 sip
1 rtp
2 fs

Inbound call is queued
Web api : create call is invoked to some number
outbound call is answered and call is dequeued.

This fails if the inbound call is on FS 1 and the outbound is placed on FS2.
In this scenario a REFER is triggered to move the call from FS 1 to FS2
Resulting in an RTP engine error response:

12|sbc-inbound | {"level":30, "time": "2023-08-17T09:18:55.532Z","pid":39604,"hostname":"ip-10-1-11-127","callId":"1454746014-3901252730-2052003254~o","uri":{"family":"ipv4","scheme":"sip","user":"context-53c07b68-bc4f-4c0d-9e70-ecc677f58ba0","host":"10.1.11.81","port":5060,"params":{},"headers":{}},"referTo":{"uri":"sip:context-53c07b68-bc4f-4c0d-9e70-ecc677f58ba0@10.1.11.81:5060","params":{}},"headers":{"via":"SIP/2.0/UDP 10.1.12.122;rport=5060;branch=z9hG4bKavK243tr9B25a","max-forwards":"70","from":"<sip:55555555@some.tld>;tag=NZKc15XZQS7HB","to":"<sip:4444444444@sip.public.ip:5060>;tag=9mNymm0jpj9Ne","call-id":"eb586d4c-b781-123c-3fbc-06923f54a6df","cseq":"71578174 REFER","contact":"<sip:10.1.12.122:5060>","refer-to":"<sip:context-53c07b68-bc4f-4c0d-9e70-ecc677f58ba0@10.1.11.81:5060>","referred-by":"<sip:10.1.12.122:5060>","content-length":"0","X-Retain-Call-Sid":"aa132b9c-a9d8-4f3d-972c-2d5f8f9181ec","X-Account-Sid":"account-sid"},"msg":"received REFER from feature server"}

and then
12|sbc-inbound | {"level":50, "time": "2023-08-17T09:18:55.963Z","pid":39604,"hostname":"ip-10-1-11-127","callId":"1454746014-3901252730-2052003254~o","err":{"type":"Error","message":"_onFeatureServerTransfer: rtpengine failed: {\"result\":\"error\",\"error-reason\":\"No call-id in message\"}","stack":"Error: _onFeatureServerTransfer: rtpengine failed: {\"result\":\"error\",\"error-reason\":\"No call-id in message\"}\n at CallSession._onFeatureServerTransfer (/home/admin/apps/sbc-inbound/lib/call-session.js:925:15)"},"msg":"Error handling refer from feature server"}

if both the inbound and outbound exist on the same FS the call scenario works as intended.