Closed davehorton closed 10 months ago
when we do a REFER to a sip uri we send this out to the carrier
2023-11-30 19:39:04.108681 send 523 bytes to udp/[172.20.10.254]:5060 at 19:39:04.108644: REFER sip:172.20.10.254:5060 SIP/2.0^M Via: SIP/2.0/UDP 172.20.10.130;rport;branch=z9hG4bKeSg6Dcc8NH4Zg^M Max-Forwards: 70^M From: <sip:+14053350001@54.236.168.131>;tag=jDv5NFm67eKeQ^M To: <sip:+14252818364@54.236.168.131:5060>;tag=gSNN62tUB6DvQ^M Call-ID: f300c6c7-0a5a-123d-89a5-0e9252b57157^M CSeq: 76132778 REFER^M Contact: <sip:172.20.10.130:5060>^M Refer-To: <sip:+14086101665@mhertogs-jambonz-cloud.pstn.twilio.com:5060>^M Referred-By: <sip:+14252818364@172.20.10.254>^M Content-Length: 0^M X-Refer-To-Leave-Untouched: true^M
That custom header X-Refer-To-Leave-Untouched should be removed, it is for use only by sbc-inbound but not when we send to the outside world
X-Refer-To-Leave-Untouched
I think main branch already did that:
https://github.com/jambonz/sbc-inbound/blob/main/lib/call-session.js#L884
Closing this issue
when we do a REFER to a sip uri we send this out to the carrier
That custom header
X-Refer-To-Leave-Untouched
should be removed, it is for use only by sbc-inbound but not when we send to the outside world