EU SBC leaks IP

[ajukes]

The following SBC leaks internal IP

INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 63.33.24.29;rport;branch=z9hG4bKg0v0NZ5gUH0jN
Max-Forwards: 70
From: <sip:[email protected]:5060>;tag=r5Smay7NDmF1D
To: <sip:[email protected]:5060>
Call-ID: d6a30094-0031-1239-87b8-02ebb6fea23c
CSeq: 19279198 INVITE
Contact: <sip:172.31.50.150:5060>
Content-Type: application/sdp
Content-Length: 481
X-CID: 406b38c9-2e4daae7-646920-7fb2f4b2d268-de641fac-13e2-7225

Should look like following

INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 34.241.251.115;rport;branch=z9hG4bKXe4c7mDemQ5ec
Max-Forwards: 70
From: <sip:[email protected]:5060>;tag=QDXS22pye7Q5K
To: <sip:[email protected]:5060>
Call-ID: b95b229d-0031-1239-cca4-02b574cefade
CSeq: 19279173 INVITE
Contact: <sip:34.241.251.115:5060>
Content-Type: application/sdp
Content-Length: 483
X-CID: e0792c9-1a2f241e-6468ef-7fb2f4af8c10-de641fac-13e2-7225

[ajukes]

Strange as only seems to happen to certain destinations. Here is another call from same SBC

INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 63.33.24.29;rport;branch=z9hG4bKFZBjtjDmtHHjF
Max-Forwards: 70
From: <sip:[email protected]:5060>;tag=pZKjgXaSXZD7p
To: <sip:[email protected]:5060>
Call-ID: e63f25e4-0032-1239-87b8-02ebb6fea23c
CSeq: 19279425 INVITE
Contact: <sip:63.33.24.29:5060>
Content-Type: application/sdp
Content-Length: 481
X-CID: 5a3d29d8-5a10781-646b02-7fb2f4d2bec0-de641fac-13e2-7225