RE: RE: [Serusers] mediaproxy problem - sr-users

30 Sep 2004


      Kun,
Without ser.cfg and ngrep dump from the ser server, the only thing I can say
is your nat handling logic is not properly setup. SER try to forward your
INVITE request to callee on the port that was blocked by the NAT device.
Zeus
...
-----Original Message-----
From: ?￡à¤ [mailto:haoniukun@sohu.com] 
Sent: Thursday, 30 September 2004 6:38 PM
To: Zeus Ng
Subject: Re:RE: [Serusers] mediaproxy problem
Dear Zeus,
Thanks for your reply,
Yes, I make myself understand. I'm trying to call myself.
I'm using the mediaproxy. But I don't know exactly why a user 
behind a firewall can't contact a user behind another 
firewall. I can get the 404 error if the user doesn't exist. 
But when I call some user exist like myself, I always get 100 
trying message, after i get 408 error. Would you mind tell me 
how this problem would happen?
Thanks in advance.
Sincerely,
Kun
-----  原文  -----
From: Zeus Ng 
To: '?￡à¤' 
Cc: serusers@lists.iptel.org 
Subject: RE: [Serusers] mediaproxy problem
Sent: Wed Sep 29 20:38:32 CST 2004
...
Are you saying you can't call yourself? Is it the question
you want to
...
ask?
The contact address sip:8103@ipaddress1:5060 is either
wrong or you
...
have made some mistake in obfuscation. It should be 
sip:8103@ipaddress2:5060. For former case, correct that address 
first. For the second case, send in the ser.cfg and dump without 
obfuscation. BTW, your IP obfuscation is somewhat broken as
we can see
...
that the client private IP is 192.168.1.13 and the public IP is 
219.137.9.30.
Zeus
...
-----Original Message-----
From: serusers-bounces@lists.iptel.org
[mailto:serusers-bounces@lists.iptel.org] On Behalf Of ?￡à¤
Sent: Wednesday, 29 September 2004 5:55 PM
To: serusers@lists.iptel.org
Subject: [Serusers] mediaproxy problem
Dear sirusers,
The following is my log file kept by x-lite.
SEND TIME: 15466254
SEND >> ipaddress1:5060
INVITE sip:8103@ipaddress1 SIP/2.0
Via: SIP/2.0/UDP ip
address2:5060;rport;branch=z9hG4bKEA15D2B6122C11D9B04300E04CEE03A2
From: 8103 <sip:8103@ip address1>;tag=1235055289
To: <sip:8103@ip address1>
Contact: sip:8103@ipaddress1:5060
Call-ID: EA15D2B5-122C-11D9-B043-00E04CEE03A2@192.168.1.13
CSeq: 52555 INVITE
Max-Forwards: 70
Content-Type: application/sdp
User-Agent: X-Lite release 1103m
Content-Length: 137
v=0
o=8103 15466182 15466249 IN IP4 ipaddress2
s=X-Lite
c=IN IP4 ipaddress2
t=0 0
m=audio 8000 RTP/AVP 0
a=rtpmap:0 pcmu/8000
RECEIVE TIME: 15466262
RECEIVE << ipaddress1:5060
SIP/2.0 100 trying -- your call is important to us
Via: SIP/2.0/UDP
ipaddress2:5060;rport=19465;branch=z9hG4bKEA15D2B6122C11D9B043
00E04CEE03A2
From: 8103 sip:8103@ipaddress1;tag=1235055289
To: sip:8103@ipaddress1
Call-ID: EA15D2B5-122C-11D9-B043-00E04CEE03A2@192.168.1.13
CSeq: 52555 INVITE
Server: Sip EXpress router (0.8.14 (i386/linux))
Content-Length: 0
Warning: 392 ipaddress1:5060 "Noisy feedback tells:  pid=2307 
req_src_ip=219.137.9.30 req_src_port=19465 
in_uri=sip:8103@ipaddress2 out_uri=sip:8103@ipaddress2:5060 
via_cnt==1"
I use the URI to call back to myself. But it just try. I
wonder if this happens when the NAT was set improperly. If 
so,how can I make some changes?
Thanks in advance.
Sincerely,
Kun

Serusers mailing list
serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers