25 May
2010
25 May
'10
1:25 p.m.
Hi all,
I'm trying to implement a Click2Dial service by using the dlg_bridge command
from the dialog module. Although it works in this case, I found two problems
in the scenario and I would like to read your opinion about them.
1) Fisrt problem: the REFER generated by Kamailio doesn't contain a contact
header. As per RFC 3515, this request should have a Contact header. This
REFER is not being accepted by a proprietary device. This is can be worked
around with the append_hf() command from the textops module, but I don know
if it is a good solution.
2) The second one arises when the ACK generated by Kamailio, goes through
Kamailio (caller and calle involved in click2dial are registered on the
Kamailio server): the branch of the second via header is not correctly
populated. Its content is '0' when it must be tha same as in the INVITE.
Below you can find the traces of the whole scenario. Could you take a look
at them and give me your feedback?
Thanks in advance,
best regards
Antón Román
T +8.969957 127.0.0.1:44785 -> 127.0.0.1:5060 [AP]
POST HTTP/1.0
User-Agent: PEAR XML_RPC
Host: 127.0.0.1
Content-Type: text/xml
Content-Length: 331
<?xml version="1.0" encoding="UTF-8"?>
<methodCall>
<methodName>mi_fifo</methodName>
<params>
<param>
<value><string>dlg_bridge</string></value>
</param>
<param>
<value><string>sip:111@10.1.20.103
<sip%3A111(a)10.1.20.103></string></value>
</param>
<param>
<value><string>sip:112@10.1.20.103
<sip%3A112(a)10.1.20.103></string></value>
</param>
</params>
</methodCall>
##
U +0.001779 10.1.20.103:5060 -> 10.1.20.103:5060
INVITE sip:111@10.1.20.103 <sip%3A111(a)10.1.20.103> SIP/2.0
Via: SIP/2.0/UDP 10.1.20.103;branch=z9hG4bKe8d6.21dbafc4.0
To: sip:111@10.1.20.103 <sip%3A111(a)10.1.20.103>
From: sip:controller@kamailio.org <sip%3Acontroller(a)kamailio.org>
;tag=533cb9e91f4b999cf76861cbb9ed54ed-2abd
CSeq: 10 INVITE
Call-ID: 3d3d4ede-7172(a)127.0.0.1
Content-Length: 147
User-Agent: kamailio (3.0.0 (i386/linux))
Contact: <sip:kamailio.org:5060>
Content-Type: application/sdp
v=0
o=kamailio-bridge 0 0 IN IP4 0.0.0.0
s=kamailio
c=IN IP4 0.0.0.0
t=0 0
m=audio 9 RTP/AVP 8 0
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
#
U +0.001330 10.1.20.103:5060 -> 10.1.20.103:5060
SIP/2.0 100 trying -- your call is important to us
Via: SIP/2.0/UDP 10.1.20.103;branch=z9hG4bKe8d6.21dbafc4.0
To: sip:111@10.1.20.103 <sip%3A111(a)10.1.20.103>
From: sip:controller@kamailio.org <sip%3Acontroller(a)kamailio.org>
;tag=533cb9e91f4b999cf76861cbb9ed54ed-2abd
CSeq: 10 INVITE
Call-ID: 3d3d4ede-7172(a)127.0.0.1
Server: kamailio (3.0.0 (i386/linux))
Content-Length: 0
Warning: 392 10.1.20.103:5060 "Noisy feedback tells: pid=7160
req_src_ip=10.1.20.103 req_src_port=5060
in_uri=sip:111@10.1.20.103<sip%3A111@10.1.20.103>out_uri=
sip:111@10.1.3.15:5061 via_cnt==1"
#
U +0.000727 10.1.20.103:5060 -> 10.1.3.15:5061
INVITE sip:111@10.1.3.15:5061 SIP/2.0
Max-Forwards: 10
Record-Route: <sip:10.1.20.103;lr=on;did=768.90707151>
Via: SIP/2.0/UDP 10.1.20.103;branch=z9hG4bKe8d6.31dbafc4.0
Via: SIP/2.0/UDP 10.1.20.103;branch=z9hG4bKe8d6.21dbafc4.0
To: sip:111@10.1.20.103 <sip%3A111(a)10.1.20.103>
From: sip:controller@kamailio.org <sip%3Acontroller(a)kamailio.org>
;tag=533cb9e91f4b999cf76861cbb9ed54ed-2abd
CSeq: 10 INVITE
Call-ID: 3d3d4ede-7172(a)127.0.0.1
Content-Length: 147
User-Agent: kamailio (3.0.0 (i386/linux))
Contact: <sip:kamailio.org:5060>
Content-Type: application/sdp
v=0
o=kamailio-bridge 0 0 IN IP4 0.0.0.0
s=kamailio
c=IN IP4 0.0.0.0
t=0 0
m=audio 9 RTP/AVP 8 0
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
#
T +0.000442 127.0.0.1:5060 -> 127.0.0.1:44785 [AP]
HTTP/1.0 200 OK
Via: SIP/2.0/TCP 127.0.0.1:44785
Server: kamailio (3.0.0 (i386/linux))
Content-Length: 211
Warning: 392 127.0.0.1:5060 "Noisy feedback tells: pid=7172
req_src_ip=127.0.0.1 req_src_port=44785 in_uri=sip:127.0.0.1:9 out_uri=sip:
127.0.0.1:9 via_cnt==1"
<?xml version="1.0"?>
<methodResponse>
<params>
<param>
<value><array><data>
<value><string>200 OK
</string></value>
<value><string>
</string></value>
</data></array></value>
</param>
</params>
</methodResponse>
#####
U +0.021063 10.1.3.15:5061 -> 10.1.20.103:5060
SIP/2.0 100 Trying
To: sip:111@10.1.20.103 <sip%3A111(a)10.1.20.103>
From: sip:controller@kamailio.org <sip%3Acontroller(a)kamailio.org>
;tag=533cb9e91f4b999cf76861cbb9ed54ed-2abd
Call-ID: 3d3d4ede-7172(a)127.0.0.1
CSeq: 10 INVITE
Via: SIP/2.0/UDP 10.1.20.103;branch=z9hG4bKe8d6.31dbafc4.0
Via: SIP/2.0/UDP 10.1.20.103;branch=z9hG4bKe8d6.21dbafc4.0
Record-Route: <sip:10.1.20.103;lr=on;did=768.90707151>
Server: Linksys/SPA941-5.1.5
Content-Length: 0
#
U +0.030585 10.1.3.15:5061 -> 10.1.20.103:5060
SIP/2.0 180 Ringing
To: sip:111@10.1.20.103 <sip%3A111(a)10.1.20.103>;tag=d45e4a92cc93b70fi1
From: sip:controller@kamailio.org <sip%3Acontroller(a)kamailio.org>
;tag=533cb9e91f4b999cf76861cbb9ed54ed-2abd
Call-ID: 3d3d4ede-7172(a)127.0.0.1
CSeq: 10 INVITE
Via: SIP/2.0/UDP 10.1.20.103;branch=z9hG4bKe8d6.31dbafc4.0
Via: SIP/2.0/UDP 10.1.20.103;branch=z9hG4bKe8d6.21dbafc4.0
Record-Route: <sip:10.1.20.103;lr=on;did=768.90707151>
Server: Linksys/SPA941-5.1.5
Content-Length: 0
#
U +0.000384 10.1.20.103:5060 -> 10.1.20.103:5060
SIP/2.0 180 Ringing
To: sip:111@10.1.20.103 <sip%3A111(a)10.1.20.103>;tag=d45e4a92cc93b70fi1
From: sip:controller@kamailio.org <sip%3Acontroller(a)kamailio.org>
;tag=533cb9e91f4b999cf76861cbb9ed54ed-2abd
Call-ID: 3d3d4ede-7172(a)127.0.0.1
CSeq: 10 INVITE
Via: SIP/2.0/UDP 10.1.20.103;branch=z9hG4bKe8d6.21dbafc4.0
Record-Route: <sip:10.1.20.103;lr=on;did=768.90707151>
Server: Linksys/SPA941-5.1.5
Content-Length: 0
#
U +2.440228 10.1.3.15:5061 -> 10.1.20.103:5060
SIP/2.0 200 OK
To: sip:111@10.1.20.103 <sip%3A111(a)10.1.20.103>;tag=d45e4a92cc93b70fi1
From: sip:controller@kamailio.org <sip%3Acontroller(a)kamailio.org>
;tag=533cb9e91f4b999cf76861cbb9ed54ed-2abd
Call-ID: 3d3d4ede-7172(a)127.0.0.1
CSeq: 10 INVITE
Via: SIP/2.0/UDP 10.1.20.103;branch=z9hG4bKe8d6.31dbafc4.0
Via: SIP/2.0/UDP 10.1.20.103;branch=z9hG4bKe8d6.21dbafc4.0
Record-Route: <sip:10.1.20.103;lr=on;did=768.90707151>
Contact: "111" <sip:111@10.1.3.15:5061>
Server: Linksys/SPA941-5.1.5
Content-Length: 200
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
Supported: replaces
Content-Type: application/sdp
v=0
o=- 761338 761338 IN IP4 10.1.3.15
s=-
c=IN IP4 10.1.3.15
t=0 0
m=audio 16434 RTP/AVP 8 101
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:30
a=sendrecv
#
U +0.000315 10.1.20.103:5060 -> 10.1.20.103:5060
SIP/2.0 200 OK
To: sip:111@10.1.20.103 <sip%3A111(a)10.1.20.103>;tag=d45e4a92cc93b70fi1
From: sip:controller@kamailio.org <sip%3Acontroller(a)kamailio.org>
;tag=533cb9e91f4b999cf76861cbb9ed54ed-2abd
Call-ID: 3d3d4ede-7172(a)127.0.0.1
CSeq: 10 INVITE
Via: SIP/2.0/UDP 10.1.20.103;branch=z9hG4bKe8d6.21dbafc4.0
Record-Route: <sip:10.1.20.103;lr=on;did=768.90707151>
Contact: "111" <sip:111@10.1.3.15:5061>
Server: Linksys/SPA941-5.1.5
Content-Length: 200
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
Supported: replaces
Content-Type: application/sdp
v=0
o=- 761338 761338 IN IP4 10.1.3.15
s=-
c=IN IP4 10.1.3.15
t=0 0
m=audio 16434 RTP/AVP 8 101
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:30
a=sendrecv
#
U +0.001190 10.1.20.103:5060 -> 10.1.20.103:5060
ACK sip:111@10.1.3.15:5061 SIP/2.0
Via: SIP/2.0/UDP 10.1.20.103;branch=z9hG4bKe8d6.21dbafc4.0
From: sip:controller@kamailio.org <sip%3Acontroller(a)kamailio.org>
;tag=533cb9e91f4b999cf76861cbb9ed54ed-2abd
Call-ID: 3d3d4ede-7172(a)127.0.0.1
To: sip:111@10.1.20.103 <sip%3A111(a)10.1.20.103>;tag=d45e4a92cc93b70fi1
CSeq: 10 ACK
Route: <sip:10.1.20.103;lr=on;did=768.90707151>
User-Agent: kamailio (3.0.0 (i386/linux))
Content-Length: 0
#
U +0.001249 10.1.20.103:5060 -> 10.1.3.15:5061
ACK sip:111@10.1.3.15:5061 SIP/2.0
Max-Forwards: 10
*Via: SIP/2.0/UDP 10.1.20.103;branch=0*
Via: SIP/2.0/UDP 10.1.20.103;branch=z9hG4bKe8d6.21dbafc4.0
From: sip:controller@kamailio.org <sip%3Acontroller(a)kamailio.org>
;tag=533cb9e91f4b999cf76861cbb9ed54ed-2abd
Call-ID: 3d3d4ede-7172(a)127.0.0.1
To: sip:111@10.1.20.103 <sip%3A111(a)10.1.20.103>;tag=d45e4a92cc93b70fi1
CSeq: 10 ACK
User-Agent: kamailio (3.0.0 (i386/linux))
Content-Length: 0
#
U +0.000418 10.1.20.103:5060 -> 10.1.20.103:5060
REFER sip:111@10.1.3.15:5061 SIP/2.0
Via: SIP/2.0/UDP 10.1.20.103;branch=z9hG4bKf8d6.0e0719e2.0
To: sip:111@10.1.20.103 <sip%3A111(a)10.1.20.103>;tag=d45e4a92cc93b70fi1
From: sip:controller@kamailio.org <sip%3Acontroller(a)kamailio.org>
;tag=533cb9e91f4b999cf76861cbb9ed54ed-2abd
CSeq: 11 REFER
Call-ID: 3d3d4ede-7172(a)127.0.0.1
Route: <sip:10.1.20.103;lr=on;did=768.90707151>
Content-Length: 0
User-Agent: kamailio (3.0.0 (i386/linux))
Referred-By: sip:controller@kamailio.org <sip%3Acontroller(a)kamailio.org>
Refer-To: sip:112@10.1.20.103 <sip%3A112(a)10.1.20.103>
*
No Contact!*!
#
U +0.005133 10.1.20.103:5060 -> 10.1.3.15:5061
REFER sip:111@10.1.3.15:5061 SIP/2.0
Max-Forwards: 10
Via: SIP/2.0/UDP 10.1.20.103;branch=z9hG4bKf8d6.1e0719e2.0
Via: SIP/2.0/UDP 10.1.20.103;branch=z9hG4bKf8d6.0e0719e2.0
To: sip:111@10.1.20.103 <sip%3A111(a)10.1.20.103>;tag=d45e4a92cc93b70fi1
From: sip:controller@kamailio.org <sip%3Acontroller(a)kamailio.org>
;tag=533cb9e91f4b999cf76861cbb9ed54ed-2abd
CSeq: 11 REFER
Call-ID: 3d3d4ede-7172(a)127.0.0.1
Content-Length: 0
User-Agent: kamailio (3.0.0 (i386/linux))
Referred-By: sip:controller@kamailio.org <sip%3Acontroller(a)kamailio.org>
Refer-To: sip:112@10.1.20.103 <sip%3A112(a)10.1.20.103>
#
U +0.046925 10.1.3.15:5061 -> 10.1.20.103:5060
INVITE sip:112@10.1.20.103 <sip%3A112(a)10.1.20.103> SIP/2.0
Via: SIP/2.0/UDP 10.1.3.15:5061;branch=z9hG4bK-9ea2814a
From: "111" <sip:111@10.1.20.103 <sip%3A111(a)10.1.20.103>
;tag=58af654bc0e634a2o1
To:
<sip:112@10.1.20.103 <sip%3A112(a)10.1.20.103>>
Call-ID: f4177d3f-86d1dd3e(a)10.1.3.15
CSeq: 101 INVITE
Max-Forwards: 70
Contact: "111" <sip:111@10.1.3.15:5061>
Expires: 240
Referred-By: sip:controller@kamailio.org <sip%3Acontroller(a)kamailio.org>
User-Agent: Linksys/SPA941-5.1.5
Content-Length: 389
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
Supported: replaces
Content-Type: application/sdp
v=0
o=- 761586 761586 IN IP4 10.1.3.15
s=-
c=IN IP4 10.1.3.15
t=0 0
m=audio 16434 RTP/AVP 8 0 2 4 18 96 97 98 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:2 G726-32/8000
a=rtpmap:4 G723/8000
a=rtpmap:18 G729a/8000
a=rtpmap:96 G726-40/8000
a=rtpmap:97 G726-24/8000
a=rtpmap:98 G726-16/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:30
a=sendrecv
#
U +0.000520 10.1.20.103:5060 -> 10.1.3.15:5061
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 10.1.3.15:5061;branch=z9hG4bK-9ea2814a
From: "111" <sip:111@10.1.20.103 <sip%3A111(a)10.1.20.103>
;tag=58af654bc0e634a2o1
To:
<sip:112@10.1.20.103 <sip%3A112(a)10.1.20.103>
;tag=f8f2ab2c1295e90ed7dbb499b30f44b2.d44b
Call-ID: f4177d3f-86d1dd3e(a)10.1.3.15
CSeq: 101 INVITE
Proxy-Authenticate: Digest realm="10.1.20.103",
nonce="4b7179d300000000c65419875a5dfc25067a1fc4b173b813"
Server: kamailio (3.0.0 (i386/linux))
Content-Length: 0
Warning: 392 10.1.20.103:5060 "Noisy feedback tells: pid=7162
req_src_ip=10.1.3.15 req_src_port=5061
in_uri=sip:112@10.1.20.103<sip%3A112@10.1.20.103>out_uri=
sip:112@10.1.20.103 <sip%3A112(a)10.1.20.103> via_cnt==1"
#
U +0.004377 10.1.3.15:5061 -> 10.1.20.103:5060
SIP/2.0 202 Accepted
To: sip:111@10.1.20.103 <sip%3A111(a)10.1.20.103>;tag=d45e4a92cc93b70fi1
From: sip:controller@kamailio.org <sip%3Acontroller(a)kamailio.org>
;tag=533cb9e91f4b999cf76861cbb9ed54ed-2abd
Call-ID: 3d3d4ede-7172(a)127.0.0.1
CSeq: 11 REFER
Via: SIP/2.0/UDP 10.1.20.103;branch=z9hG4bKf8d6.1e0719e2.0
Via: SIP/2.0/UDP 10.1.20.103;branch=z9hG4bKf8d6.0e0719e2.0
Contact: "111" <sip:111@10.1.3.15:5061>
Server: Linksys/SPA941-5.1.5
Content-Length: 0
#
U +0.000193 10.1.20.103:5060 -> 10.1.20.103:5060
SIP/2.0 202 Accepted
To: sip:111@10.1.20.103 <sip%3A111(a)10.1.20.103>;tag=d45e4a92cc93b70fi1
From: sip:controller@kamailio.org <sip%3Acontroller(a)kamailio.org>
;tag=533cb9e91f4b999cf76861cbb9ed54ed-2abd
Call-ID: 3d3d4ede-7172(a)127.0.0.1
CSeq: 11 REFER
Via: SIP/2.0/UDP 10.1.20.103;branch=z9hG4bKf8d6.0e0719e2.0
Contact: "111" <sip:111@10.1.3.15:5061>
Server: Linksys/SPA941-5.1.5
Content-Length: 0
#
U +0.000286 10.1.20.103:5060 -> 10.1.20.103:5060
BYE sip:111@10.1.3.15:5061 SIP/2.0
Via: SIP/2.0/UDP 10.1.20.103;branch=z9hG4bKf8d6.2e0719e2.0
To: sip:111@10.1.20.103 <sip%3A111(a)10.1.20.103>;tag=d45e4a92cc93b70fi1
From: sip:controller@kamailio.org <sip%3Acontroller(a)kamailio.org>
;tag=533cb9e91f4b999cf76861cbb9ed54ed-2abd
CSeq: 11 BYE
Call-ID: 3d3d4ede-7172(a)127.0.0.1
Route: <sip:10.1.20.103;lr=on;did=768.90707151>
Content-Length: 0
User-Agent: kamailio (3.0.0 (i386/linux))
#
U +0.003618 10.1.20.103:5060 -> 10.1.3.15:5061
BYE sip:111@10.1.3.15:5061 SIP/2.0
Max-Forwards: 10
Via: SIP/2.0/UDP 10.1.20.103;branch=z9hG4bKf8d6.3e0719e2.0
Via: SIP/2.0/UDP 10.1.20.103;branch=z9hG4bKf8d6.2e0719e2.0
To: sip:111@10.1.20.103 <sip%3A111(a)10.1.20.103>;tag=d45e4a92cc93b70fi1
From: sip:controller@kamailio.org <sip%3Acontroller(a)kamailio.org>
;tag=533cb9e91f4b999cf76861cbb9ed54ed-2abd
CSeq: 11 BYE
Call-ID: 3d3d4ede-7172(a)127.0.0.1
Content-Length: 0
User-Agent: kamailio (3.0.0 (i386/linux))
#
U +0.005223 10.1.3.15:5061 -> 10.1.20.103:5060
ACK sip:112@10.1.20.103 <sip%3A112(a)10.1.20.103> SIP/2.0
Via: SIP/2.0/UDP 10.1.3.15:5061;branch=z9hG4bK-9ea2814a
From: "111" <sip:111@10.1.20.103 <sip%3A111(a)10.1.20.103>
;tag=58af654bc0e634a2o1
To:
<sip:112@10.1.20.103 <sip%3A112(a)10.1.20.103>
;tag=f8f2ab2c1295e90ed7dbb499b30f44b2.d44b
Call-ID: f4177d3f-86d1dd3e(a)10.1.3.15
CSeq: 101 ACK
Max-Forwards: 70
Contact: "111" <sip:111@10.1.3.15:5061>
User-Agent: Linksys/SPA941-5.1.5
Content-Length: 0
#
U +0.010954 10.1.3.15:5061 -> 10.1.20.103:5060
INVITE sip:112@10.1.20.103 <sip%3A112(a)10.1.20.103> SIP/2.0
Via: SIP/2.0/UDP 10.1.3.15:5061;branch=z9hG4bK-ee6fa05e
From: "111" <sip:111@10.1.20.103 <sip%3A111(a)10.1.20.103>
;tag=58af654bc0e634a2o1
To:
<sip:112@10.1.20.103 <sip%3A112(a)10.1.20.103>>
Call-ID: f4177d3f-86d1dd3e(a)10.1.3.15
CSeq: 102 INVITE
Max-Forwards: 70
Proxy-Authorization: Digest
username="111",realm="10.1.20.103",nonce="4b7179d300000000c65419875a5dfc25067a1fc4b173b813",uri="
sip:112@10.1.20.103 <sip%3A112(a)10.1.20.103>
",algorithm=MD5,response="2baeb40875c0cc7040857daa6e8192fa"
Contact: "111" <sip:111@10.1.3.15:5061>
Expires: 240
Referred-By: sip:controller@kamailio.org <sip%3Acontroller(a)kamailio.org>
User-Agent: Linksys/SPA941-5.1.5
Content-Length: 389
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
Supported: replaces
Content-Type: application/sdp
v=0
o=- 761586 761586 IN IP4 10.1.3.15
s=-
c=IN IP4 10.1.3.15
t=0 0
m=audio 16434 RTP/AVP 8 0 2 4 18 96 97 98 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:2 G726-32/8000
a=rtpmap:4 G723/8000
a=rtpmap:18 G729a/8000
a=rtpmap:96 G726-40/8000
a=rtpmap:97 G726-24/8000
a=rtpmap:98 G726-16/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:30
a=sendrecv
#
U +0.001353 10.1.20.103:5060 -> 10.1.3.15:5061
SIP/2.0 100 trying -- your call is important to us
Via: SIP/2.0/UDP 10.1.3.15:5061;branch=z9hG4bK-ee6fa05e
From: "111" <sip:111@10.1.20.103 <sip%3A111(a)10.1.20.103>
;tag=58af654bc0e634a2o1
To:
<sip:112@10.1.20.103 <sip%3A112(a)10.1.20.103>>
Call-ID: f4177d3f-86d1dd3e(a)10.1.3.15
CSeq: 102 INVITE
Server: kamailio (3.0.0 (i386/linux))
Content-Length: 0
Warning: 392 10.1.20.103:5060 "Noisy feedback tells: pid=7159
req_src_ip=10.1.3.15 req_src_port=5061
in_uri=sip:112@10.1.20.103<sip%3A112@10.1.20.103>out_uri=
sip:112@10.1.3.18:5061 via_cnt==1"
#
U +0.000226 10.1.20.103:5060 -> 10.1.3.18:5061
INVITE sip:112@10.1.3.18:5061 SIP/2.0
Record-Route: <sip:10.1.20.103;lr=on;did=a4d.ef1941a3>
Via: SIP/2.0/UDP 10.1.20.103;branch=z9hG4bK7d0c.d071633.0
Via: SIP/2.0/UDP 10.1.3.15:5061;branch=z9hG4bK-ee6fa05e
From: "111" <sip:111@10.1.20.103 <sip%3A111(a)10.1.20.103>
;tag=58af654bc0e634a2o1
To:
<sip:112@10.1.20.103 <sip%3A112(a)10.1.20.103>>
Call-ID: f4177d3f-86d1dd3e(a)10.1.3.15
CSeq: 102 INVITE
Max-Forwards: 69
Contact: "111" <sip:111@10.1.3.15:5061>
Expires: 240
Referred-By: sip:controller@kamailio.org <sip%3Acontroller(a)kamailio.org>
User-Agent: Linksys/SPA941-5.1.5
Content-Length: 389
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
Supported: replaces
Content-Type: application/sdp
v=0
o=- 761586 761586 IN IP4 10.1.3.15
s=-
c=IN IP4 10.1.3.15
t=0 0
m=audio 16434 RTP/AVP 8 0 2 4 18 96 97 98 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:2 G726-32/8000
a=rtpmap:4 G723/8000
a=rtpmap:18 G729a/8000
a=rtpmap:96 G726-40/8000
a=rtpmap:97 G726-24/8000
a=rtpmap:98 G726-16/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:30
a=sendrecv
#
U +0.007697 10.1.3.15:5061 -> 10.1.20.103:5060
SIP/2.0 500 Internal Server Error
To: sip:111@10.1.20.103 <sip%3A111(a)10.1.20.103>;tag=d45e4a92cc93b70fi1
From: sip:controller@kamailio.org <sip%3Acontroller(a)kamailio.org>
;tag=533cb9e91f4b999cf76861cbb9ed54ed-2abd
Call-ID: 3d3d4ede-7172(a)127.0.0.1
CSeq: 11 BYE
Via: SIP/2.0/UDP 10.1.20.103;branch=z9hG4bKf8d6.3e0719e2.0
Via: SIP/2.0/UDP 10.1.20.103;branch=z9hG4bKf8d6.2e0719e2.0
Server: Linksys/SPA941-5.1.5
Content-Length: 0
#
U +0.000280 10.1.20.103:5060 -> 10.1.20.103:5060
SIP/2.0 500 Internal Server Error
To: sip:111@10.1.20.103 <sip%3A111(a)10.1.20.103>;tag=d45e4a92cc93b70fi1
From: sip:controller@kamailio.org <sip%3Acontroller(a)kamailio.org>
;tag=533cb9e91f4b999cf76861cbb9ed54ed-2abd
Call-ID: 3d3d4ede-7172(a)127.0.0.1
CSeq: 11 BYE
Via: SIP/2.0/UDP 10.1.20.103;branch=z9hG4bKf8d6.2e0719e2.0
Server: Linksys/SPA941-5.1.5
Content-Length: 0
#
U +0.012355 10.1.3.18:5061 -> 10.1.20.103:5060
SIP/2.0 100 Trying
To: <sip:112@10.1.20.103 <sip%3A112(a)10.1.20.103>>
From: "111" <sip:111@10.1.20.103 <sip%3A111(a)10.1.20.103>
;tag=58af654bc0e634a2o1
Call-ID:
f4177d3f-86d1dd3e(a)10.1.3.15
CSeq: 102 INVITE
Via: SIP/2.0/UDP 10.1.20.103;branch=z9hG4bK7d0c.d071633.0
Via: SIP/2.0/UDP 10.1.3.15:5061;branch=z9hG4bK-ee6fa05e
Record-Route: <sip:10.1.20.103;lr=on;did=a4d.ef1941a3>
Server: Linksys/SPA941-5.1.5
Content-Length: 0
#
U +0.034919 10.1.3.18:5061 -> 10.1.20.103:5060
SIP/2.0 180 Ringing
To: <sip:112@10.1.20.103 <sip%3A112(a)10.1.20.103>>;tag=d091cd3cd91903c5i1
From: "111" <sip:111@10.1.20.103 <sip%3A111(a)10.1.20.103>
;tag=58af654bc0e634a2o1
Call-ID:
f4177d3f-86d1dd3e(a)10.1.3.15
CSeq: 102 INVITE
Via: SIP/2.0/UDP 10.1.20.103;branch=z9hG4bK7d0c.d071633.0
Via: SIP/2.0/UDP 10.1.3.15:5061;branch=z9hG4bK-ee6fa05e
Record-Route: <sip:10.1.20.103;lr=on;did=a4d.ef1941a3>
Server: Linksys/SPA941-5.1.5
Content-Length: 0
#
U +0.000260 10.1.20.103:5060 -> 10.1.3.15:5061
SIP/2.0 180 Ringing
To: <sip:112@10.1.20.103 <sip%3A112(a)10.1.20.103>>;tag=d091cd3cd91903c5i1
From: "111" <sip:111@10.1.20.103 <sip%3A111(a)10.1.20.103>
;tag=58af654bc0e634a2o1
Call-ID:
f4177d3f-86d1dd3e(a)10.1.3.15
CSeq: 102 INVITE
Via: SIP/2.0/UDP 10.1.3.15:5061;branch=z9hG4bK-ee6fa05e
Record-Route: <sip:10.1.20.103;lr=on;did=a4d.ef1941a3>
Server: Linksys/SPA941-5.1.5
Content-Length: 0
#
U +0.032160 10.1.3.15:5061 -> 10.1.20.103:5060
NOTIFY sip:kamailio.org:5060 SIP/2.0
Via: SIP/2.0/UDP 10.1.3.15:5061;branch=z9hG4bK-77e77cb8
From: <sip:111@10.1.20.103 <sip%3A111(a)10.1.20.103>>;tag=d45e4a92cc93b70fi1
To: <sip:controller@kamailio.org <sip%3Acontroller(a)kamailio.org>
;tag=533cb9e91f4b999cf76861cbb9ed54ed-2abd
Call-ID: 3d3d4ede-7172(a)127.0.0.1
CSeq: 101 NOTIFY
Max-Forwards: 70
Route: <sip:10.1.20.103;lr=on;did=768.90707151>
Event: refer
User-Agent: Linksys/SPA941-5.1.5
Subscription-State: active
Content-Length: 21
Content-Type: message/sipfrag;version=2.0
SIP/2.0 180 Ringing
#
U +0.002343 10.1.20.103:5060 -> 193.22.119.66:5060
NOTIFY sip:kamailio.org:5060 SIP/2.0
Via: SIP/2.0/UDP 10.1.20.103;branch=z9hG4bK2455.f8178c15.0
Via: SIP/2.0/UDP 10.1.3.15:5061;branch=z9hG4bK-77e77cb8
From: <sip:111@10.1.20.103 <sip%3A111(a)10.1.20.103>>;tag=d45e4a92cc93b70fi1
To: <sip:controller@kamailio.org <sip%3Acontroller(a)kamailio.org>
;tag=533cb9e91f4b999cf76861cbb9ed54ed-2abd
Call-ID: 3d3d4ede-7172(a)127.0.0.1
CSeq: 101 NOTIFY
Max-Forwards: 69
Event: refer
User-Agent: Linksys/SPA941-5.1.5
Subscription-State: active
Content-Length: 21
Content-Type: message/sipfrag;version=2.0
SIP/2.0 180 Ringing
#
U +0.461009 10.1.20.103:5060 -> 193.22.119.66:5060
NOTIFY sip:kamailio.org:5060 SIP/2.0
Via: SIP/2.0/UDP 10.1.20.103;branch=z9hG4bK2455.f8178c15.0
Via: SIP/2.0/UDP 10.1.3.15:5061;branch=z9hG4bK-77e77cb8
From: <sip:111@10.1.20.103 <sip%3A111(a)10.1.20.103>>;tag=d45e4a92cc93b70fi1
To: <sip:controller@kamailio.org <sip%3Acontroller(a)kamailio.org>
;tag=533cb9e91f4b999cf76861cbb9ed54ed-2abd
Call-ID: 3d3d4ede-7172(a)127.0.0.1
CSeq: 101 NOTIFY
Max-Forwards: 69
Event: refer
User-Agent: Linksys/SPA941-5.1.5
Subscription-State: active
Content-Length: 21
Content-Type: message/sipfrag;version=2.0
SIP/2.0 180 Ringing
#
U +0.028104 10.1.3.15:5061 -> 10.1.20.103:5060
NOTIFY sip:kamailio.org:5060 SIP/2.0
Via: SIP/2.0/UDP 10.1.3.15:5061;branch=z9hG4bK-77e77cb8
From: <sip:111@10.1.20.103 <sip%3A111(a)10.1.20.103>>;tag=d45e4a92cc93b70fi1
To: <sip:controller@kamailio.org <sip%3Acontroller(a)kamailio.org>
;tag=533cb9e91f4b999cf76861cbb9ed54ed-2abd
Call-ID: 3d3d4ede-7172(a)127.0.0.1
CSeq: 101 NOTIFY
Max-Forwards: 70
Route: <sip:10.1.20.103;lr=on;did=768.90707151>
Event: refer
User-Agent: Linksys/SPA941-5.1.5
Subscription-State: active
Content-Length: 21
Content-Type: message/sipfrag;version=2.0
SIP/2.0 180 Ringing
#
U +0.760273 10.1.3.18:5061 -> 10.1.20.103:5060
SIP/2.0 200 OK
To: <sip:112@10.1.20.103 <sip%3A112(a)10.1.20.103>>;tag=d091cd3cd91903c5i1
From: "111" <sip:111@10.1.20.103 <sip%3A111(a)10.1.20.103>
;tag=58af654bc0e634a2o1
Call-ID:
f4177d3f-86d1dd3e(a)10.1.3.15
CSeq: 102 INVITE
Via: SIP/2.0/UDP 10.1.20.103;branch=z9hG4bK7d0c.d071633.0
Via: SIP/2.0/UDP 10.1.3.15:5061;branch=z9hG4bK-ee6fa05e
Record-Route: <sip:10.1.20.103;lr=on;did=a4d.ef1941a3>
Contact: "112" <sip:112@10.1.3.18:5061>
Server: Linksys/SPA941-5.1.5
Content-Length: 200
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
Supported: replaces
Content-Type: application/sdp
v=0
o=- 761170 761170 IN IP4 10.1.3.18
s=-
c=IN IP4 10.1.3.18
t=0 0
m=audio 16464 RTP/AVP 8 101
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:30
a=sendrecv
#
U +0.000246 10.1.20.103:5060 -> 10.1.3.15:5061
SIP/2.0 200 OK
To: <sip:112@10.1.20.103 <sip%3A112(a)10.1.20.103>>;tag=d091cd3cd91903c5i1
From: "111" <sip:111@10.1.20.103 <sip%3A111(a)10.1.20.103>
;tag=58af654bc0e634a2o1
Call-ID:
f4177d3f-86d1dd3e(a)10.1.3.15
CSeq: 102 INVITE
Via: SIP/2.0/UDP 10.1.3.15:5061;branch=z9hG4bK-ee6fa05e
Record-Route: <sip:10.1.20.103;lr=on;did=a4d.ef1941a3>
Contact: "112" <sip:112@10.1.3.18:5061>
Server: Linksys/SPA941-5.1.5
Content-Length: 200
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
Supported: replaces
Content-Type: application/sdp
v=0
o=- 761170 761170 IN IP4 10.1.3.18
s=-
c=IN IP4 10.1.3.18
t=0 0
m=audio 16464 RTP/AVP 8 101
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:30
a=sendrecv
#
U +0.022157 10.1.3.15:5061 -> 10.1.20.103:5060
ACK sip:112@10.1.3.18:5061 SIP/2.0
Via: SIP/2.0/UDP 10.1.3.15:5061;branch=z9hG4bK-a8e0a92a
From: "111" <sip:111@10.1.20.103 <sip%3A111(a)10.1.20.103>
;tag=58af654bc0e634a2o1
To:
<sip:112@10.1.20.103 <sip%3A112(a)10.1.20.103>>;tag=d091cd3cd91903c5i1
Call-ID: f4177d3f-86d1dd3e(a)10.1.3.15
CSeq: 102 ACK
Max-Forwards: 70
Route: <sip:10.1.20.103;lr=on;did=a4d.ef1941a3>
Proxy-Authorization: Digest
username="111",realm="10.1.20.103",nonce="4b7179d300000000c65419875a5dfc25067a1fc4b173b813",uri="
sip:112@10.1.3.18:5061
",algorithm=MD5,response="3d72eeb2b6b5b2c161685ac3435b657c"
Contact: "111" <sip:111@10.1.3.15:5061>
User-Agent: Linksys/SPA941-5.1.5
Content-Length: 0
#
U +0.009321 10.1.20.103:5060 -> 10.1.3.18:5061
ACK sip:112@10.1.3.18:5061 SIP/2.0
Via: SIP/2.0/UDP 10.1.20.103;branch=0
Via: SIP/2.0/UDP 10.1.3.15:5061;branch=z9hG4bK-a8e0a92a
From: "111" <sip:111@10.1.20.103 <sip%3A111(a)10.1.20.103>
;tag=58af654bc0e634a2o1
To:
<sip:112@10.1.20.103 <sip%3A112(a)10.1.20.103>>;tag=d091cd3cd91903c5i1
Call-ID: f4177d3f-86d1dd3e(a)10.1.3.15
CSeq: 102 ACK
Max-Forwards: 69
Proxy-Authorization: Digest
username="111",realm="10.1.20.103",nonce="4b7179d300000000c65419875a5dfc25067a1fc4b173b813",uri="
sip:112@10.1.3.18:5061
",algorithm=MD5,response="3d72eeb2b6b5b2c161685ac3435b657c"
Contact: "111" <sip:111@10.1.3.15:5061>
User-Agent: Linksys/SPA941-5.1.5
Content-Length: 0
#
U +0.447617 10.1.3.18:5061 -> 10.1.20.103:5060
BYE sip:111@10.1.3.15:5061 SIP/2.0
Via: SIP/2.0/UDP 10.1.3.18:5061;branch=z9hG4bK-73a35564
From: <sip:112@10.1.20.103 <sip%3A112(a)10.1.20.103>>;tag=d091cd3cd91903c5i1
To: "111" <sip:111@10.1.20.103 <sip%3A111(a)10.1.20.103>
;tag=58af654bc0e634a2o1
Call-ID:
f4177d3f-86d1dd3e(a)10.1.3.15
CSeq: 101 BYE
Max-Forwards: 70
Route: <sip:10.1.20.103;lr=on;did=a4d.ef1941a3>
User-Agent: Linksys/SPA941-5.1.5
Content-Length: 0
#
U +0.007101 10.1.20.103:5060 -> 10.1.3.15:5061
BYE sip:111@10.1.3.15:5061 SIP/2.0
Via: SIP/2.0/UDP 10.1.20.103;branch=z9hG4bKad0c.d0bfffc.0
Via: SIP/2.0/UDP 10.1.3.18:5061;branch=z9hG4bK-73a35564
From: <sip:112@10.1.20.103 <sip%3A112(a)10.1.20.103>>;tag=d091cd3cd91903c5i1
To: "111" <sip:111@10.1.20.103 <sip%3A111(a)10.1.20.103>
;tag=58af654bc0e634a2o1
Call-ID:
f4177d3f-86d1dd3e(a)10.1.3.15
CSeq: 101 BYE
Max-Forwards: 69
User-Agent: Linksys/SPA941-5.1.5
Content-Length: 0
#
U +0.014754 10.1.3.15:5061 -> 10.1.20.103:5060
SIP/2.0 200 OK
To: "111" <sip:111@10.1.20.103 <sip%3A111(a)10.1.20.103>
;tag=58af654bc0e634a2o1
From:
<sip:112@10.1.20.103 <sip%3A112(a)10.1.20.103>>;tag=d091cd3cd91903c5i1
Call-ID: f4177d3f-86d1dd3e(a)10.1.3.15
CSeq: 101 BYE
Via: SIP/2.0/UDP 10.1.20.103;branch=z9hG4bKad0c.d0bfffc.0
Via: SIP/2.0/UDP 10.1.3.18:5061;branch=z9hG4bK-73a35564
Server: Linksys/SPA941-5.1.5
Content-Length: 0
#
U +0.000198 10.1.20.103:5060 -> 10.1.3.18:5061
SIP/2.0 200 OK
To: "111" <sip:111@10.1.20.103 <sip%3A111(a)10.1.20.103>
;tag=58af654bc0e634a2o1
From:
<sip:112@10.1.20.103 <sip%3A112(a)10.1.20.103>>;tag=d091cd3cd91903c5i1
Call-ID: f4177d3f-86d1dd3e(a)10.1.3.15
CSeq: 101 BYE
Via: SIP/2.0/UDP 10.1.3.18:5061;branch=z9hG4bK-73a35564
Server: Linksys/SPA941-5.1.5
Content-Length: 0
25 May
25 May
2:44 p.m.
Am 25.05.2010 12:25, schrieb Anton Roman:
Hi all,
I'm trying to implement a Click2Dial service by using the dlg_bridge
command from the dialog module. Although it works in this case, I found
two problems in the scenario and I would like to read your opinion about
them.
1) Fisrt problem: the REFER generated by Kamailio doesn't contain a
contact header. As per RFC 3515, this request should have a Contact
header. This REFER is not being accepted by a proprietary device. This
is can be worked around with the append_hf() command from the textops
module, but I don know if it is a good solution.
2) The second one arises when the ACK generated by Kamailio, goes
through Kamailio (caller and calle involved in click2dial are registered
on the Kamailio server): the branch of the second via header is not
correctly populated. Its content is '0' when it must be tha same as in
the INVITE.
AFAIK if the ACK is an ACK to a 2xx response, then the ACK is a new
transaction and should have a new branch id.
If 0 is a proper branch id is another question (IIRC it is valid with
RFC2543 but not with 3261).
This is an often raised topic which you can find discussed in the archive.
regards
Klaus
4:46 p.m.
Hi,
you are right, it has to be the same in the original request only when the
final response is a non-2xx (RFC3261, 17.1.1.3). The magic cookie is missing
so '0' can not be a valid RFC3261 branch, anyway a '0' value populating a
param when it should be a random value looks like a buggy situation. This
happens in both 3.0.0 and 3.0.1.
Regarding the traces I attached in the previous mail, please, omit the
NOTIFY which are being sent to kamailio.org :-), to work this around I
replied this NOTIFY (which indicates the state of the REFER processing) from
the Kamailio configuration with a 200OK, it works for me.
Thanks,
feedbacks are welcome
Anton
2010/5/25 Klaus Darilion <klaus.mailinglists(a)pernau.at>
Am 25.05.2010 12:25, schrieb Anton Roman:
Hi all,
I'm trying to implement a Click2Dial service by using the dlg_bridge
command from the dialog module. Although it works in this case, I found
two problems in the scenario and I would like to read your opinion about
them.
1) Fisrt problem: the REFER generated by Kamailio doesn't contain a
contact header. As per RFC 3515, this request should have a Contact
header. This REFER is not being accepted by a proprietary device. This
is can be worked around with the append_hf() command from the textops
module, but I don know if it is a good solution.
2) The second one arises when the ACK generated by Kamailio, goes
through Kamailio (caller and calle involved in click2dial are registered
on the Kamailio server): the branch of the second via header is not
correctly populated. Its content is '0' when it must be tha same as in
the INVITE.
AFAIK if the ACK is an ACK to a 2xx response, then the ACK is a new
transaction and should have a new branch id.
If 0 is a proper branch id is another question (IIRC it is valid with
RFC2543 but not with 3261).
This is an often raised topic which you can find discussed in the archive.
regards
Klaus
4:57 p.m.
Am 25.05.2010 15:46, schrieb Anton Roman:
Regarding the traces I attached in the previous mail,
please, omit the
NOTIFY which are being sent to kamailio.org <http://kamailio.org> :-),
to work this around I replied this NOTIFY (which indicates the state of
the REFER processing) from the Kamailio configuration with a 200OK, it
works for me.
I think this is a fine workaround. Done.
regards
Klaus
PS: IIRC there is also an extensions to REFER to omit the implicit
subscription (something like "Refer-light"). In this case the transfered
target should not even send NOTIFY - but I do not know if any clients
support that.
Refer-To: http://tools.ietf.org/html/rfc4488 :-)
regards
Klaus
4:04 p.m.
Klaus Darilion writes:
PS: IIRC there is also an extensions to REFER to omit
the implicit
subscription (something like "Refer-light"). In this case the transfered
target should not even send NOTIFY - but I do not know if any clients
support that.
if you mean norefersub, i have seen it supported in some UAs.
-- juha
5298
days inactive
5298
days old
4 comments
3 participants
participants (3)
-
Anton Roman -
Juha Heinanen -
Klaus Darilion