Passing Referred-By Header (SIP to SIP)
The Referred-By Header which is an optional header in the REFER request provides the recipient of the REFER message, information on the originator of the request. Currently on the IMG 2020, it depends on the call flow as to whether the Referred-By header is passed or dropped. The new functionality added in F-6443 passes the Referred-By Header from the incoming to outgoing leg on a SIP to SIP call. Prior to this feature, the Referred-By Header was dropped. The new functionality encompasses both the Referred-By header in both the SIP-URI and tel-URI and is by default always enabled and cannot be disabled. Refer to the information below.
Call Flow Diagrams
The Call Flow diagrams below display the Referred-By header being passed from SIP network on the incoming side to SIP network on the outgoing side. Both tel URI and SIP URI formats are displayed.
SIP to SIP (SIP URI)
The call flow below (SIP URI) displays the Referred-By header utilizing the SIP URI format being received in the incoming (A-Leg) INVITE message and being passed to the outgoing (B leg) INVITE message.
SIP to SIP (tel URI)
The call flow below (tel URI) displays the Referred-By header utilizing the tel URI format being received in the incoming (A-Leg) INVITE message and being passed to the outgoing (B leg) INVITE message.
Call Trace
The Call trace displays the Referred-By Header being passed from incoming SIP side to outgoing SIP network using the tel URI format.
21:35:38.257 CALL(SIP) (00:00003:00) RCVD INVITE W/SDP from 10.129.39.101:8000udp CSeq:1
21:35:38.257 CALL(SIP) (00:00003:00) with Via sent-by: 10.129.39.101
21:35:38.257 CALL(SIP) (00:00003:00) Call-id: 1-9952@10.129.39.101
21:35:38.257 CALL(SIP) (00:00003:00) and Msg Size: 718
21:35:38.257 CALL(SIP) (00:00003:00)
---> [10.129.39.101, 8000]
INVITE sip:7741111@10.129.39.51:5060 SIP/2.0\r\n
Via: SIP/2.0/UDP 10.129.39.101:8000;branch=z9hG4bK-9952-1-0\r\n
From: <sip:2222@10.129.39.101:8000>;tag=1\r\n
To: <sip:7741111@10.129.39.51:5060>\r\n
Call-ID: 1-9952@10.129.39.101\r\n
CSeq: 1 INVITE\r\n
Contact: <sip:2222@10.129.39.101:8000>,<sip:40668610656@
62.206.3.10:5060;user=phone>\r\n
Referred-By: "ABC"<tel:123456789;param=test>\r\n
Max-Forwards: 70\r\n
Subject: F6445 pass two URIs in PAID Test\r\n
Content-Type: application/sdp\r\n
Content-Length: 135\r\n
\r\n
v=0\r\n
o=user1 53655765 2353687637 IN IP4 10.129.39.101\r\n
s=-\r\n
c=IN IP4 10.129.39.101\r\n
t=0 0\r\n
m=audio 6000 RTP/AVP 0\r\n
a=rtpmap:0 PCMU/8000
21:35:38.257 CALL(SIP) (00:00003:00) SENT 100 Trying to 10.129.39.101:8000
21:35:38.257 CALL(SIP) (00:00003:00)
<--- [10.129.39.101, 8000 <- 10.129.39.51, 5060]
SIP/2.0 100 Trying\r\n
Via: SIP/2.0/UDP 10.129.39.101:8000;branch=z9hG4bK-9952-1-0;received=10.129.39.101\r\n
Call-ID: 1-9952@10.129.39.101\r\n
From: <sip:2222@10.129.39.101:8000>;tag=1\r\n
To: <sip:7741111@10.129.39.51:5060>\r\n
CSeq: 1 INVITE\r\n
Server: Dialogic-SIP/10.5.3.168 img51 0\r\n
Content-Length: 0\r\n
\r\n
21:35:38.257 CALL(SIP) (00:00003:00) SENT Route Control to L4
21:35:38.257 CALL(SIP) (00:00003:00) RCVD Route Control Ack from L4
21:35:38.257 CALL(SIP) (00:00003:00) Session Group Profile ID is 4
21:35:38.257 CALL(SIP) (00:00003:00) SENT Route Control to L4
21:35:38.257 CALL(SIP) (00:00003:00) RCVD Route Control Ack from L4
21:35:38.257 CALL(SIP) (00:00003:00) m line (audio) codec list: 0
21:35:38.257 CALL(SIP) (00:00003:00) RTP Type: 0, name: PCMU, clk: 8000
21:35:38.257 CALL(SIP) (00:00003:00) CODEC Negotiation Priority LOCAL
21:35:38.257 CALL(SIP) (00:00003:00) CPC (Default)
21:35:38.257 CALL(SIP) (00:00003:00) CPC (Default)
21:35:38.257 CALL(SIP) (00:00003:00) Leg 0 associated with hndl(4995), LTS(1028)(span 4096 chan 4)
21:35:38.257 CALL(SIP) (00:00003:00) SENT Setup to L4
21:35:38.277 CALL(SIP) (00:00003:01) RCVD Outseize Ctrl from L4
21:35:38.277 CALL(SIP) (00:00003:01) SENT Route Control to L4
21:35:38.277 CALL(SIP) (00:00003:01) RCVD Route Control Ack from L4
21:35:38.277 CALL(SIP) (00:00003:01) Session Group Profile ID is 4
21:35:38.277 CALL(SIP) (00:00003:01) SENT Route Control to L4
21:35:38.277 CALL(SIP) (00:00003:01) RCVD Route Control Ack from L4
21:35:38.277 CALL(SIP) (00:00003:01) REM TP port=5060 transport:0
21:35:38.277 CALL(SIP) (00:00003:01) SENT INVITE W/SDP to 10.129.39.31:5060 Cseq:1
21:35:38.277 CALL(SIP) (00:00003:01) with R-URI: 10.129.39.31:5060 UDP
21:35:38.277 CALL(SIP) (00:00003:01) and Call-id: 7712-405-6262012213538-img51-0-10.129.39.51
21:35:38.277 CALL(SIP) (00:00003:01)
<--- [10.129.39.31, 5060 <- 10.129.39.51, 5060]
INVITE sip:7741111@10.129.39.31:5060 SIP/2.0\r\n
Via: SIP/2.0/UDP 10.129.39.51:5060;rport;branch=z9hG4bK-
32d8-1343338538-4994-80\r\n
Call-ID: 7712-405-6262012213538-img51-0-10.129.39.51\r\n
CSeq: 1 INVITE\r\n
Max-Forwards: 70\r\n
To: <sip:7741111@10.129.39.31:5060>\r\n
From: "sip uri display"<sip:1234@10.129.39.51>;tag=95ffc
d055e0f78f7d5d397020e89288d561aeff6\r\n
User-Agent: Dialogic-SIP/10.5.3.168 img51 0\r\n
Timestamp: 07262012213538\r\n
Contact: <sip:1234@10.129.39.51:5060>\r\n
Allow: INVITE, BYE, REGISTER, ACK, OPTIONS, CANCEL, SUBS
CRIBE, NOTIFY, INFO, REFER, UPDATE\r\n
Supported: path, replaces, timer, tdialog\r\n
Session-Expires: 1800\r\n
Referred-By: "ABC"<tel:123456789;param=test>\r\n
Expires: 300\r\n
Organization: Dialogic\r\n
Content-Type: application/sdp\r\n
Content-Length: 164\r\n
\r\n
v=0\r\n
o=Dialogic_SDP 5 0 IN IP4 10.129.39.51\r\n
s=Dialogic-SIP\r\n
c=IN IP4 10.129.39.52\r\n
t=0 0\r\n
m=audio 8020 RTP/AVP 0\r\n
a=rtpmap:0 PCMU/8000\r\n
a=silenceSupp:off - - - -\r\n
Configuration
There is no configuration needed. Passing the Referred-By header is by default set to enabled and cannot be disabled.
Additional Information
Prior to feature F-6443 Passing Referred-By header in INVITE message,in a SIP to SIP call, if a Referred-By Header was received, it would be dropped and not passed.