[Serusers] nathelper / rtpproxy inconsistencies

Jac Barben jbarben at claritytel.com
Tue Feb 24 17:10:01 CET 2004


Jan:

Thanks for replying! 

CISCO: The sequence below will continue until

U 63.219.127.2:48523 -> 64.47.72.12:5060
  INVITE sip:913037773456 at 64.47.72.12:5060 SIP/2.0..From: "3036797305" 
<sip:3
  
036797305 at sip2.claritycolorado.com:5060>;tag=zip4x5_866103480-5037..To: "91
  3037773456" <sip:913037773456 at 64.47.72.12:5060>..Call-ID: 
866103149-5037..C
  Seq: 1 INVITE..Via: SIP/2.0/UDP 192.168.0.86:5060..Contact: 3036797305 
<sip
  :3036797305 at 192.168.0.86:5060>..Allow: 
INVITE,BYE,CANCEL,ACK,OPTIONS,REGIST
  ER,NOTIFY,MESSAGE,REFER..User-Agent: Zultys Linux Softphone 
1.3.11..Content
  -Type: application/sdp..Content-Length: 
268....v=0..o=ZIP4x4-3036797305-1.3
  .11 0 0 IN IP4 192.168.0.86..s=zultys media..c=IN IP4 
192.168.0.86..t=0 0..
  m=audio 33000 RTP/AVP 0 8 18 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 
PCMA/800
  0..a=rtpmap:18 G729/8000..a=rtpmap:101 
telephone-event/8000..a=fmtp:101 0-1
  5..a=ptime:20..

U 64.47.72.12:5060 -> 63.219.127.2:48523
  SIP/2.0 100 trying -- your call is important to us..From: "3036797305" 
<sip
  
:3036797305 at sip2.claritycolorado.com:5060>;tag=zip4x5_866103480-5037..To: "
  913037773456" <sip:913037773456 at 64.47.72.12:5060>..Call-ID: 
866103149-5037.
  .CSeq: 1 INVITE..Via: SIP/2.0/UDP 
192.168.0.86:5060;rport=48523;received=63
  .219.127.2..Server: Sip EXpress router (0.8.12 
(i386/linux))..Content-Lengt
  h: 0..Warning: 392 64.47.72.12:5060 "Noisy feedback tells:  pid=17357 
req_s
  rc_ip=63.219.127.2 req_src_port=48523 
in_uri=sip:913037773456 at 64.47.72.12:5
  060 out_uri=sip:282713037773456 at 198.77.133.112:5060 via_cnt==1"....
                                                                                

U 64.47.72.12:5060 -> 198.77.133.112:5060
  INVITE sip:282713037773456 at 198.77.133.112:5060 SIP/2.0..Max-Forwards: 
10..R
  ecord-Route: 
<sip:913037773456 at 64.47.72.12;ftag=zip4x5_866103480-5037;lr=on
  >..From: "3036797305" 
<sip:3036797305 at sip2.claritycolorado.com:5060>;tag=zi
  p4x5_866103480-5037..To: "913037773456" 
<sip:913037773456 at 64.47.72.12:5060>
  ..Call-ID: 866103149-5037..CSeq: 1 INVITE..Via: SIP/2.0/UDP 
64.47.72.12;bra
  nch=z9hG4bK7eb1.35d4738.0..Via: SIP/2.0/UDP 
192.168.0.86:5060;rport=48523;r
  eceived=63.219.127.2..Contact: 3036797305 
<sip:3036797305 at 63.219.127.2:4852
  3>..Allow: 
INVITE,BYE,CANCEL,ACK,OPTIONS,REGISTER,NOTIFY,MESSAGE,REFER..Use
  r-Agent: Zultys Linux Softphone 1.3.11..Content-Type: 
application/sdp..Cont
  ent-Length: 288267....v=0..o=ZIP4x4-3036797305-1.3.11 0 0 IN IP4 
192.168.0.
  86..s=zultys media..c=IN IP4 64.47.72.12..t=0 0..m=audio 35440 RTP/AVP 0 8
  18 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:18 
G729/8000..

Sonus:  This is a one time deal.  One message one error.

U 63.219.127.2:48523 -> 64.47.72.12:5060
  INVITE sip:613037773456 at 64.47.72.12:5060 SIP/2.0..From: "3036797305" 
<sip:3
  
036797305 at sip2.claritycolorado.com:5060>;tag=zip4x5_1051715498-5037..To: "6
  13037773456" <sip:613037773456 at 64.47.72.12:5060>..Call-ID: 
1051715222-5037.
  .CSeq: 1 INVITE..Via: SIP/2.0/UDP 192.168.0.86:5060..Contact: 
3036797305 <s
  ip:3036797305 at 192.168.0.86:5060>..Allow: 
INVITE,BYE,CANCEL,ACK,OPTIONS,REGI
  STER,NOTIFY,MESSAGE,REFER..User-Agent: Zultys Linux Softphone 
1.3.11..Conte
  nt-Type: application/sdp..Content-Length: 
268....v=0..o=ZIP4x4-3036797305-1
  .3.11 0 0 IN IP4 192.168.0.86..s=zultys media..c=IN IP4 
192.168.0.86..t=0 0
  ..m=audio 33000 RTP/AVP 0 8 18 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 
PCMA/8
  000..a=rtpmap:18 G729/8000..a=rtpmap:101 
telephone-event/8000..a=fmtp:101 0
  -15..a=ptime:20..
                                                                                

U 64.47.72.12:5060 -> 63.219.127.2:48523
  SIP/2.0 100 trying -- your call is important to us..From: "3036797305" 
<sip
  :3036797305 at sip2.claritycolorado.com:5060>;tag=zip4x5_1051715498-5037..To:
  "613037773456" <sip:613037773456 at 64.47.72.12:5060>..Call-ID: 
1051715222-503
  7..CSeq: 1 INVITE..Via: SIP/2.0/UDP 
192.168.0.86:5060;rport=48523;received=
  63.219.127.2..Server: Sip EXpress router (0.8.12 
(i386/linux))..Content-Len
  gth: 0..Warning: 392 64.47.72.12:5060 "Noisy feedback tells:  
pid=17456 req
  _src_ip=63.219.127.2 req_src_port=48523 
in_uri=sip:613037773456 at 64.47.72.12
  :5060 out_uri=sip:13037773456 at 64.47.6.6:5060 via_cnt==1"....

U 64.47.72.12:5060 -> 64.47.6.6:5060
  INVITE sip:13037773456 at 64.47.6.6:5060 SIP/2.0..Max-Forwards: 
10..Record-Rou
  te: 
<sip:613037773456 at 64.47.72.12;ftag=zip4x5_1051715498-5037;lr=on>..From:
   "3036797305" 
<sip:3036797305 at sip2.claritycolorado.com:5060>;tag=zip4x5_105
  1715498-5037..To: "613037773456" 
<sip:613037773456 at 64.47.72.12:5060>..Call-
  ID: 1051715222-5037..CSeq: 1 INVITE..Via: SIP/2.0/UDP 
64.47.72.12;branch=z9
  hG4bKc368.66a8f6e2.0..Via: SIP/2.0/UDP 
192.168.0.86:5060;rport=48523;receiv
  ed=63.219.127.2..Contact: 3036797305 
<sip:3036797305 at 63.219.127.2:48523>..A
  llow: 
INVITE,BYE,CANCEL,ACK,OPTIONS,REGISTER,NOTIFY,MESSAGE,REFER..User-Age
  nt: Zultys Linux Softphone 1.3.11..Content-Type: 
application/sdp..Content-L
  ength: 288267....v=0..o=ZIP4x4-3036797305-1.3.11 0 0 IN IP4 
192.168.0.86..s
  =zultys media..c=IN IP4 64.47.72.12..t=0 0..m=audio 35442 RTP/AVP 0 8 
18 10
  1..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:18 
G729/8000..a=rtp
  map:101 telephone-event/8000..a=fmtp:101 
0-15..a=ptime:20..a=direction:acti
  ve..
                                                                                

U 64.47.6.6:5060 -> 64.47.72.12:5060
  SIP/2.0 400 Bad Request..Via: SIP/2.0/UDP 
64.47.72.12;branch=z9hG4bKc368.66
  a8f6e2.0..Via: SIP/2.0/UDP 
192.168.0.86:5060;rport=48523;received=63.219.12
  7.2..From: "3036797305" 
<sip:3036797305 at sip2.claritycolorado.com:5060>;tag=
  zip4x5_1051715498-5037..To: "613037773456" 
<sip:613037773456 at 64.47.72.12:50
  60>..Call-ID: 1051715222-5037..CSeq: 1 INVITE..Content-Length: 0....

Jan Janak wrote:

>Try to make SIP message dumps using ngrep, we would like to see the
>messages which are discarded by the CISCO gateway and which get 400 Bad
>Request from the other gateway.
>
>  Jan.
>
>On 24-02 00:24, Jac Barben wrote:
>  
>
>>All:
>>
>>Please bear with me... I'm having a hard time formulating this quesiton.
>>
>>Basics:
>>ser-0.8.12  from src
>>rtpproxy = $Id: main.c,v 1.19.2.10 2003/10/18 20:14:22 sobomax Exp
>>RH 7.3  updated to: [root at sip2 rtpproxy]# uname -a
>>Linux sip2.claritycolorado.com 2.4.20-20.7 #1 Mon Aug 18 14:56:30 EDT 
>>2003 i686
>>unknown
>>
>>The problem seems to be that I cannot "always" forward calls to a given 
>>destination if I have executed the force_rtp_proxy.
>>
>>Typically I'm using a UA like a Cisco ATA, PureData, or softphone behind 
>>a firewall.  They in-turn register to SER/rtpproxy at a legal IP 
>>address; most calls are then forwarded to a Vega gateway that resides on 
>>the same network as SER/rtpproxy (in Denver).  In this instance all is 
>>well.  However, when I try to alt route calls to an "off-network" source 
>>(Cisco in LA and Sonus in Houston) I get two different and disturbing 
>>results:
>>1. Cisco will not respond to SER:  Cisco simply indicates in its own 
>>logs that the INVITE is invalid and thus "trashed" the message
>>2. Sonus will respond with a "Bad Request"
>>
>>Below are some snippets:
>>
>>Prior to calling the route I have already I identified whether or not my 
>>UA is behind a firewall and have fix_nated_contact(), force_rport(), 
>>setflag(1)
>>
>>SER/rtpproxy is running at 64.47.72.12
>>
>># Clarity Vega Evergreen CO -- this one works
>>route[1]
>>{
>>      if (uri=~"[@:](192\.168\.|10\.|172\.(1[6-9]|2[0-9]|3[0-1])\.)" &&
>>              !search("^Route:") ) {
>>              sl_send_reply("479",
>>                      "We don't forward to private IP addresses");
>>              break;
>>      };
>>                                                                              
>>
>>      record_route();
>>      if (isflagset(1)) {
>>              fix_nated_sdp("1");
>>              force_rtp_proxy();
>>              t_on_reply("2");
>>      }
>>                                                                              
>>
>>      rewritehostport("64.47.72.10:5060");
>>      t_relay();
>>}
>>
>># Clarity Cisco AS5300 LA -- this one does not
>>route[2]
>>{
>>      if (uri=~"[@:](192\.168\.|10\.|172\.(1[6-9]|2[0-9]|3[0-1])\.)" &&
>>              !search("^Route:") ) {
>>              sl_send_reply("479",
>>                      "We don't forward to private IP addresses");
>>              break;
>>      };
>>                                                                              
>>
>>      record_route();
>>      if (isflagset(1)) {
>>              fix_nated_sdp("1");
>>              force_rtp_proxy();
>>              t_on_reply("2");
>>      }
>>                                                                              
>>
>>      rewritehostport("198.77.133.30:5060");
>>      t_relay();
>>}
>>
>>
>># Clarity Sonus Houston  -- this one does not
>>route[3]
>>{
>>      if (uri=~"[@:](192\.168\.|10\.|172\.(1[6-9]|2[0-9]|3[0-1])\.)" &&
>>              !search("^Route:") ) {
>>              sl_send_reply("479",
>>                      "We don't forward to private IP addresses");
>>              break;
>>      };
>>                                                                              
>>
>>      record_route();
>>      if (isflagset(1)) {
>>              fix_nated_sdp("1");
>>              force_rtp_proxy();
>>              t_on_reply("2");
>>      }
>>                                                                              
>>
>>      rewritehostport("64.47.6.6:5060");
>>      t_relay();
>>}
>>
>>/* inbound */
>>onreply_route[2] {
>>      fix_nated_contact();
>>      fix_nated_sdp("1");
>>      force_rtp_proxy();
>>}
>>
>>
>>Please... If you have any ideas... I'm really stuck.
>>
>>Jac Barben
>>
>>_______________________________________________
>>Serusers mailing list
>>serusers at lists.iptel.org
>>http://lists.iptel.org/mailman/listinfo/serusers
>>    
>>




More information about the sr-users mailing list