[Serusers] Bad ports in a Messenger Client comunication
RAQUEL LOPEZ DIAZ
raquell at tid.es
Fri Nov 5 14:42:18 CET 2004
Hi!!
I have one promblem in a comunication with two Client. I use sip
express router 0.8.14 with Nat and rtpproxy. I captured packets:
U 81.35.36.166:19168 -> 194.179.25.52:5060
INVITE sip:raquel at wmserver.hi.inet SIP/2.0..Via: SIP/2.0/UDP
81.35.36.166:19124..From: "chano"
<sip:chano at wmserver.hi.inet>;tag=fe05c1ce-52
c4-4814-9689-c635dcf48e35..To: <sip:raquel at wmserver.hi.inet>..Call-
ID: 0bfff467-3c8c-4be1-ba2b-eba9b1106cff at 81.35.36.166..CSeq: 1
INVITE..C
ontact: <sip:81.35.36.166:19124>..User-Agent: Windows
RTC/1.0..Content-Type: application/sdp..Content-Length:
531....v=0..o=sayuritra 0 0 I
N IP4 81.35.36.166..s=session..c=IN IP4 81.35.36.166..b=CT:1000..t=0
0..m=audio 19183 RTP/AVP 97 111 112 6 0 8 4 5 3 101..a=rtpmap:97 red/8
000..a=rtpmap:111 SIREN/16000..a=fmtp:111
bitrate=16000..a=rtpmap:112 G7221/16000..a=fmtp:112
bitrate=24000..a=rtpmap:6 DVI4/16000..a=rtpma
p:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:4
G723/8000..a=rtpmap:5 DVI4/8000..a=rtpmap:3 GSM/8000..a=rtpmap:101
telephone-event/8000..a=
fmtp:101 0-16..m=video 52292 RTP/AVP 34 31..a=rtpmap:34
H263/90000..a=rtpmap:31 H261/90000..
#
U 194.179.25.52:5060 -> 81.35.36.166:19124
SIP/2.0 100 trying -- your call is important to us..Via: SIP/2.0/UDP
81.35.36.166:19124..From: "chano" <sip:chano at wmserver.hi.inet>;tag=fe0
5c1ce-52c4-4814-9689-c635dcf48e35..To:
<sip:raquel at wmserver.hi.inet>..Call-ID: 0bfff467-3c8c-4be1-ba2b-
eba9b1106cff at 81.35.36.166..CSeq: 1 I
NVITE..Server: Sip EXpress router (0.8.14 (i386/linux))..Content-
Length: 0..Warning: 392 194.179.25.52:5060 "Noisy feedback tells:
pid=884
8 req_src_ip=81.35.36.166 req_src_port=19168
in_uri=sip:raquel at wmserver.hi.inet out_uri=sip:80.32.97.245:24761
via_cnt==1"....
#
U 194.179.25.52:5060 -> 80.32.97.245:24761
INVITE sip:80.32.97.245:24761 SIP/2.0..Max-Forwards: 10..Record-
Route: <sip:raquel at 194.179.25.52;ftag=fe05c1ce-52c4-4814-9689-
c635dcf48e35;
lr=on>..Via: SIP/2.0/UDP
194.179.25.52;branch=z9hG4bKd76e.f9f1d9c2.0..Via: SIP/2.0/UDP
81.35.36.166:19124..From: "chano" <sip:chano at wmserve
r.hi.inet>;tag=fe05c1ce-52c4-4814-9689-c635dcf48e35..To:
<sip:raquel at wmserver.hi.inet>..Call-ID: 0bfff467-3c8c-4be1-ba2b-
eba9b1106cff at 81.35
.36.166..CSeq: 1 INVITE..Contact: <sip:81.35.36.166:19124>..User-
Agent: Windows RTC/1.0..Content-Type: application/sdp..Content-Length:
550
..P-Behind-NAT: Yes....v=0..o=sayuritra 0 0 IN IP4
81.35.36.166..s=session..c=IN IP4 194.179.25.52..b=CT:1000..t=0
0..m=audio 35016 RTP/AVP
97 111 112 6 0 8 4 5 3 101..a=rtpmap:97 red/8000..a=rtpmap:111
SIREN/16000..a=fmtp:111 bitrate=16000..a=rtpmap:112
G7221/16000..a=fmtp:112
bitrate=24000..a=rtpmap:6 DVI4/16000..a=rtpmap:0
PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:4 G723/8000..a=rtpmap:5
DVI4/8000..a=rtpmap:3 G
SM/8000..a=rtpmap:101 telephone-event/8000..a=fmtp:101 0-16..m=video
52292 RTP/AVP 34 31..a=rtpmap:34 H263/90000..a=rtpmap:31 H261/90000..a
=nortpproxy:yes..
#
U 80.32.97.245:24761 -> 194.179.25.52:5060
SIP/2.0 100 Trying..Via: SIP/2.0/UDP
194.179.25.52;branch=z9hG4bKd76e.f9f1d9c2.0..Via: SIP/2.0/UDP
81.35.36.166:19124..From: "chano" <sip:c
hano at wmserver.hi.inet>;tag=fe05c1ce-52c4-4814-9689-c635dcf48e35..To:
<sip:raquel at wmserver.hi.inet>;tag=183dfa8b-0a7b-43b4-9fd4-01dfd3d6dbf3
..Call-ID: 0bfff467-3c8c-4be1-ba2b-eba9b1106cff at 81.35.36.166..CSeq:
1 INVITE..User-Agent: Windows RTC/1.0..Content-Length: 0....
#
U 80.32.97.245:24761 -> 194.179.25.52:5060
SIP/2.0 180 Ringing..Via: SIP/2.0/UDP
194.179.25.52;branch=z9hG4bKd76e.f9f1d9c2.0..Via: SIP/2.0/UDP
81.35.36.166:19124..From: "chano" <sip:
chano at wmserver.hi.inet>;tag=fe05c1ce-52c4-4814-9689-
c635dcf48e35..To: <sip:raquel at wmserver.hi.inet>;tag=183dfa8b-0a7b-43b4-
9fd4-01dfd3d6dbf
3..Call-ID: 0bfff467-3c8c-4be1-ba2b-eba9b1106cff at 81.35.36.166..CSeq:
1 INVITE..Record-Route: <sip:raquel at 194.179.25.52;ftag=fe05c1ce-52c4-4
814-9689-c635dcf48e35;lr=on>..User-Agent: Windows RTC/1.0..Content-
Length: 0....
#
U 194.179.25.52:5060 -> 81.35.36.166:19124
SIP/2.0 180 Ringing..Via: SIP/2.0/UDP
81.35.36.166:19124..From: "chano"
<sip:chano at wmserver.hi.inet>;tag=fe05c1ce-52c4-4814-9689-c635dcf48e
35..To: <sip:raquel at wmserver.hi.inet>;tag=183dfa8b-0a7b-43b4-9fd4-
01dfd3d6dbf3..Call-ID: 0bfff467-3c8c-4be1-ba2b-
eba9b1106cff at 81.35.36.166.
.CSeq: 1 INVITE..Record-Route:
<sip:raquel at 194.179.25.52;ftag=fe05c1ce-52c4-4814-9689-
c635dcf48e35;lr=on>..User-Agent: Windows RTC/1.0..Con
tent-Length: 0....
#
U 80.32.97.245:24761 -> 194.179.25.52:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP
194.179.25.52;branch=z9hG4bKd76e.f9f1d9c2.0..Via: SIP/2.0/UDP
81.35.36.166:19124..From: "chano" <sip:chano
@wmserver.hi.inet>;tag=fe05c1ce-52c4-4814-9689-c635dcf48e35..To:
<sip:raquel at wmserver.hi.inet>;tag=183dfa8b-0a7b-43b4-9fd4-
01dfd3d6dbf3..Ca
ll-ID: 0bfff467-3c8c-4be1-ba2b-eba9b1106cff at 81.35.36.166..CSeq: 1
INVITE..Record-Route: <sip:raquel at 194.179.25.52;ftag=fe05c1ce-52c4-
4814-9
689-c635dcf48e35;lr=on>..Contact: <sip:192.168.1.34:9466>..User-
Agent: Windows RTC/1.0..Content-Type: application/sdp..Content-Length:
528.
...v=0..o=hobbes 0 0 IN IP4 192.168.1.34..s=session..c=IN IP4
192.168.1.34..b=CT:1000..t=0 0..m=audio 17318 RTP/AVP 97 111 112 6 0 8
4 5 3
101..a=rtpmap:97 red/8000..a=rtpmap:111 SIREN/16000..a=fmtp:111
bitrate=16000..a=rtpmap:112 G7221/16000..a=fmtp:112
bitrate=24000..a=rtpmap
:6 DVI4/16000..a=rtpmap:0 PCMU/8000..a=rtpmap:8
PCMA/8000..a=rtpmap:4 G723/8000..a=rtpmap:5 DVI4/8000..a=rtpmap:3
GSM/8000..a=rtpmap:101 te
lephone-event/8000..a=fmtp:101 0-16..m=video 20872 RTP/AVP 34
31..a=rtpmap:34 H263/90000..a=rtpmap:31 H261/90000..
#
U 194.179.25.52:5060 -> 81.35.36.166:19124
SIP/2.0 200 OK..Via: SIP/2.0/UDP 81.35.36.166:19124..From: "chano"
<sip:chano at wmserver.hi.inet>;tag=fe05c1ce-52c4-4814-9689-
c635dcf48e35..T
o: <sip:raquel at wmserver.hi.inet>;tag=183dfa8b-0a7b-43b4-9fd4-
01dfd3d6dbf3..Call-ID: 0bfff467-3c8c-4be1-ba2b-
eba9b1106cff at 81.35.36.166..CSeq
: 1 INVITE..Record-Route: <sip:raquel at 194.179.25.52;ftag=fe05c1ce-
52c4-4814-9689-c635dcf48e35;lr=on>..Contact:
<sip:80.32.97.245:24761>..Us
er-Agent: Windows RTC/1.0..Content-Type: application/sdp..Content-
Length: 547....v=0..o=hobbes 0 0 IN IP4 192.168.1.34..s=session..c=IN
IP4
194.179.25.52..b=CT:1000..t=0 0..m=audio 35018 RTP/AVP 97 111 112 6
0 8 4 5 3 101..a=rtpmap:97 red/8000..a=rtpmap:111 SIREN/16000..a=fmtp:
111 bitrate=16000..a=rtpmap:112 G7221/16000..a=fmtp:112
bitrate=24000..a=rtpmap:6 DVI4/16000..a=rtpmap:0 PCMU/8000..a=rtpmap:8
PCMA/8000..a
=rtpmap:4 G723/8000..a=rtpmap:5 DVI4/8000..a=rtpmap:3
GSM/8000..a=rtpmap:101 telephone-event/8000..a=fmtp:101 0-16..m=video
20872 RTP/AVP 3
4 31..a=rtpmap:34 H263/90000..a=rtpmap:31
H261/90000..a=nortpproxy:yes..
#
U 81.35.36.166:19168 -> 194.179.25.52:5060
ACK sip:raquel at 194.179.25.52;ftag=fe05c1ce-52c4-4814-9689-
c635dcf48e35;lr=on SIP/2.0..Via: SIP/2.0/UDP
81.35.36.166:19124..From: "chano" <s
ip:chano at wmserver.hi.inet>;tag=fe05c1ce-52c4-4814-9689-
c635dcf48e35..To: <sip:raquel at wmserver.hi.inet>;tag=183dfa8b-0a7b-43b4-
9fd4-01dfd3d6
dbf3..Call-ID: 0bfff467-3c8c-4be1-ba2b-
eba9b1106cff at 81.35.36.166..CSeq: 1 ACK..Route:
<sip:80.32.97.245:24761>..Contact: <sip:81.35.36.166:
19124>..User-Agent: Windows RTC/1.0..Content-Length: 0....
#
U 194.179.25.52:5060 -> 80.32.97.245:24761
ACK sip:80.32.97.245:24761 SIP/2.0..Max-Forwards: 10..Record-Route:
<sip:raquel at 194.179.25.52;ftag=fe05c1ce-52c4-4814-9689-c635dcf48e35;lr=
on>..Via: SIP/2.0/UDP 194.179.25.52;branch=0..Via: SIP/2.0/UDP
81.35.36.166:19124..From: "chano"
<sip:chano at wmserver.hi.inet>;tag=fe05c1ce-
52c4-4814-9689-c635dcf48e35..To:
<sip:raquel at wmserver.hi.inet>;tag=183dfa8b-0a7b-43b4-9fd4-
01dfd3d6dbf3..Call-ID: 0bfff467-3c8c-4be1-ba2b-e
ba9b1106cff at 81.35.36.166..CSeq: 1 ACK..Contact:
<sip:81.35.36.166:19124>..User-Agent: Windows RTC/1.0..Content-Length:
0..P-hint: rr-enforc
ed....
For video, the ports used are:
Client 1 : IP 81.35.36.166 port 52292
SER: IP 194.179.25.52 ports 20872 52292
Client 2: IP 80.32.97.245 port 20872
But, rtpproxy use:
For client 1 port 20872
For client 2 port 52292
what´s happened??
I`m sorry my bad english.
Thanks
Raquel
More information about the sr-users
mailing list