Hi!
I just having problems cancelling forked calls.
openser forwards the incoming CANCEL to both phones. As you see, openser added 2 via headers to the last CANCEL. The via header of branch 1 and branch 2.
Maybe something got wrong when introducing branch routes?
I'm using todays CVS.
klaus
83.136.33.3:1200 -> 83.136.32.83:5060 CANCEL sip:klaus@enum.at SIP/2.0 Via: SIP/2.0/UDP 10.10.0.76:8418 Max-Forwards: 70 From: "klaus.darilion@nic.at43.at" sip:klaus.darilion@nic.at43.at;tag=b3669e387d784f1dbd080f83fdd62306;epid=9012264a99 To: sip:klaus@enum.at Call-ID: e654c424b1124ce29b93e7dd6a8ad44c CSeq: 2 CANCEL User-Agent: RTC/1.3 Content-Length: 0
# U 83.136.32.83:5060 -> 83.136.33.19:5060 CANCEL sip:klaus@83.136.33.19:5060 SIP/2.0 Record-Route: sip:83.136.32.83;ftag=b3669e387d784f1dbd080f83fdd62306;nat=yes;lr=on Via: SIP/2.0/UDP 83.136.32.83;branch=z9hG4bK131f.f3d7378.0 Via: SIP/2.0/UDP 10.10.0.76:8418;rport=1200;received=83.136.33.3 Max-Forwards: 16 From:"klaus.darilion@nic.at43.at" sip:klaus.darilion@nic.at43.at;tag=b3669e387d784f1dbd080f83fdd62306;epid=9012264a99 To: sip:klaus@enum.at Call-ID: e654c424b1124ce29b93e7dd6a8ad44c CSeq: 2 CANCEL User-Agent: RTC/1.3 Content-Length: 0 P-Behind-NAT: Yes
# U 83.136.32.83:5060 -> 83.136.33.3:8718 CANCEL sip:klaus@10.10.0.50:8718 SIP/2.0 Record-Route: sip:83.136.32.83;ftag=b3669e387d784f1dbd080f83fdd62306;nat=yes;lr=on Via: SIP/2.0/UDP 83.136.32.83;branch=z9hG4bK131f.f3d7378.0 Via: SIP/2.0/UDP 83.136.32.83;branch=z9hG4bK131f.f3d7378.1 Via: SIP/2.0/UDP 10.10.0.76:8418;rport=1200;received=83.136.33.3;rport=1200;received=83.136.33.3 Max-Forwards: 16 From: "klaus.darilion@nic.at43.at" sip:klaus.darilion@nic.at43.at;tag=b3669e387d784f1dbd080f83fdd62306;epid=9012264a99 To: sip:klaus@enum.at Call-ID: e654c424b1124ce29b93e7dd6a8ad44c CSeq:2 CANCEL User-Agent: RTC/1.3 Content-Length: 0 P-Behind-NAT: Yes
Hi Klaus,
indeed.... I'm working on it....
thanks for report, bogdan
Klaus Darilion wrote:
Hi!
I just having problems cancelling forked calls.
openser forwards the incoming CANCEL to both phones. As you see, openser added 2 via headers to the last CANCEL. The via header of branch 1 and branch 2.
Maybe something got wrong when introducing branch routes?
I'm using todays CVS.
klaus
83.136.33.3:1200 -> 83.136.32.83:5060 CANCEL sip:klaus@enum.at SIP/2.0 Via: SIP/2.0/UDP 10.10.0.76:8418 Max-Forwards: 70 From: "klaus.darilion@nic.at43.at" sip:klaus.darilion@nic.at43.at;tag=b3669e387d784f1dbd080f83fdd62306;epid=9012264a99
To: sip:klaus@enum.at Call-ID: e654c424b1124ce29b93e7dd6a8ad44c CSeq: 2 CANCEL User-Agent: RTC/1.3 Content-Length: 0
# U 83.136.32.83:5060 -> 83.136.33.19:5060 CANCEL sip:klaus@83.136.33.19:5060 SIP/2.0 Record-Route: sip:83.136.32.83;ftag=b3669e387d784f1dbd080f83fdd62306;nat=yes;lr=on Via: SIP/2.0/UDP 83.136.32.83;branch=z9hG4bK131f.f3d7378.0 Via: SIP/2.0/UDP 10.10.0.76:8418;rport=1200;received=83.136.33.3 Max-Forwards: 16 From:"klaus.darilion@nic.at43.at" sip:klaus.darilion@nic.at43.at;tag=b3669e387d784f1dbd080f83fdd62306;epid=9012264a99
To: sip:klaus@enum.at Call-ID: e654c424b1124ce29b93e7dd6a8ad44c CSeq: 2 CANCEL User-Agent: RTC/1.3 Content-Length: 0 P-Behind-NAT: Yes
# U 83.136.32.83:5060 -> 83.136.33.3:8718 CANCEL sip:klaus@10.10.0.50:8718 SIP/2.0 Record-Route: sip:83.136.32.83;ftag=b3669e387d784f1dbd080f83fdd62306;nat=yes;lr=on Via: SIP/2.0/UDP 83.136.32.83;branch=z9hG4bK131f.f3d7378.0 Via: SIP/2.0/UDP 83.136.32.83;branch=z9hG4bK131f.f3d7378.1 Via: SIP/2.0/UDP 10.10.0.76:8418;rport=1200;received=83.136.33.3;rport=1200;received=83.136.33.3
Max-Forwards: 16 From: "klaus.darilion@nic.at43.at" sip:klaus.darilion@nic.at43.at;tag=b3669e387d784f1dbd080f83fdd62306;epid=9012264a99
To: sip:klaus@enum.at Call-ID: e654c424b1124ce29b93e7dd6a8ad44c CSeq:2 CANCEL User-Agent: RTC/1.3 Content-Length: 0 P-Behind-NAT: Yes
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Hi Klaus,
the bug is fixed on CVS.
regards, bogdan
Bogdan-Andrei Iancu wrote:
Hi Klaus,
indeed.... I'm working on it....
thanks for report, bogdan
Klaus Darilion wrote:
Hi!
I just having problems cancelling forked calls.
openser forwards the incoming CANCEL to both phones. As you see, openser added 2 via headers to the last CANCEL. The via header of branch 1 and branch 2.
Maybe something got wrong when introducing branch routes?
I'm using todays CVS.
klaus
83.136.33.3:1200 -> 83.136.32.83:5060 CANCEL sip:klaus@enum.at SIP/2.0 Via: SIP/2.0/UDP 10.10.0.76:8418 Max-Forwards: 70 From: "klaus.darilion@nic.at43.at" sip:klaus.darilion@nic.at43.at;tag=b3669e387d784f1dbd080f83fdd62306;epid=9012264a99
To: sip:klaus@enum.at Call-ID: e654c424b1124ce29b93e7dd6a8ad44c CSeq: 2 CANCEL User-Agent: RTC/1.3 Content-Length: 0
# U 83.136.32.83:5060 -> 83.136.33.19:5060 CANCEL sip:klaus@83.136.33.19:5060 SIP/2.0 Record-Route: sip:83.136.32.83;ftag=b3669e387d784f1dbd080f83fdd62306;nat=yes;lr=on Via: SIP/2.0/UDP 83.136.32.83;branch=z9hG4bK131f.f3d7378.0 Via: SIP/2.0/UDP 10.10.0.76:8418;rport=1200;received=83.136.33.3 Max-Forwards: 16 From:"klaus.darilion@nic.at43.at" sip:klaus.darilion@nic.at43.at;tag=b3669e387d784f1dbd080f83fdd62306;epid=9012264a99
To: sip:klaus@enum.at Call-ID: e654c424b1124ce29b93e7dd6a8ad44c CSeq: 2 CANCEL User-Agent: RTC/1.3 Content-Length: 0 P-Behind-NAT: Yes
# U 83.136.32.83:5060 -> 83.136.33.3:8718 CANCEL sip:klaus@10.10.0.50:8718 SIP/2.0 Record-Route: sip:83.136.32.83;ftag=b3669e387d784f1dbd080f83fdd62306;nat=yes;lr=on Via: SIP/2.0/UDP 83.136.32.83;branch=z9hG4bK131f.f3d7378.0 Via: SIP/2.0/UDP 83.136.32.83;branch=z9hG4bK131f.f3d7378.1 Via: SIP/2.0/UDP 10.10.0.76:8418;rport=1200;received=83.136.33.3;rport=1200;received=83.136.33.3
Max-Forwards: 16 From: "klaus.darilion@nic.at43.at" sip:klaus.darilion@nic.at43.at;tag=b3669e387d784f1dbd080f83fdd62306;epid=9012264a99
To: sip:klaus@enum.at Call-ID: e654c424b1124ce29b93e7dd6a8ad44c CSeq:2 CANCEL User-Agent: RTC/1.3 Content-Length: 0 P-Behind-NAT: Yes
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users