[Serusers] Re: [Serdev] nathelper updated to support RTP proxy

Younger Wang wygmail at yeah.net
Wed Jul 9 23:48:59 CEST 2003


It compiled and functioned to relay media stream. It's great.   However,
there is some error message from Ser:

WARNING: no fork mode
Maxfwd module- initializing
textops - initializing
stateless - initializing
 0(0) INFO: udp_init: SO_RCVBUF is initially 65535
 0(0) INFO: udp_init: SO_RCVBUF is finally 131070
 2(0) INFO: fifo process starting: 12285
 2(12285) SER: open_uac_fifo: fifo server up at /tmp/ser_fifo...
 0(12282) ERROR: extract_mediaip: no `c=' in SDP
 0(12282) WARNING: get_body_len: Content-TYPE header absent!let's assume the
con
tent is text/plain ;-)
 0(12282) ERROR: on_reply processing failed
 0(12282) WARNING: get_body_len: Content-TYPE header absent!let's assume the
con
tent is text/plain ;-)
 0(12282) ERROR: on_reply processing failed
 0(12282) ERROR: extract_mediaip: no `c=' in SDP


Corresponding output of rtpproxy is:

rtpproxy: new session on a port 35000
rtpproxy: lookup on a port 35000
rtpproxy: addr1 filled in
rtpproxy: addr2 filled in
rtpproxy: session on port 35000 is cleaned up


I am making the test on Linux 7.3. Both of the SIP UA is ata186. The network
structure is:
ATA 1------------NAT 1 (Microsoft ICS)-------NAT 2 (Cisco 2600)--------SER
       (192.168.0.1)                               (192.17.1.0)

ATA 2------------------------------------------NAT2(Cisco
2600)--------------SER
                                     (192.17.1.0)

I'll make further test through Cisco 53 to PSTN.


Younger Wang


----- Original Message ----- 
From: "Younger Wang" <wygmail at yeah.net>
To: "Maxim Sobolev" <sobomax at portaone.com>
Cc: <serdev at lists.iptel.org>; <serusers at lists.iptel.org>
Sent: Wednesday, July 09, 2003 2:21 PM
Subject: Re: [Serusers] Re: [Serdev] nathelper updated to support RTP proxy


> It compiled and functioned to relay media stream. It's great.   However,
> there is some error message from Ser:
>
> WARNING: no fork mode
> Maxfwd module- initializing
> textops - initializing
> stateless - initializing
>  0(0) INFO: udp_init: SO_RCVBUF is initially 65535
>  0(0) INFO: udp_init: SO_RCVBUF is finally 131070
>  2(0) INFO: fifo process starting: 12285
>  2(12285) SER: open_uac_fifo: fifo server up at /tmp/ser_fifo...
>  0(12282) ERROR: extract_mediaip: no `c=' in SDP
>  0(12282) WARNING: get_body_len: Content-TYPE header absent!let's assume
the
> con
> tent is text/plain ;-)
>  0(12282) ERROR: on_reply processing failed
>  0(12282) WARNING: get_body_len: Content-TYPE header absent!let's assume
the
> con
> tent is text/plain ;-)
>  0(12282) ERROR: on_reply processing failed
>  0(12282) ERROR: extract_mediaip: no `c=' in SDP
>
>
> Corresponding output of rtpproxy is:
>
> rtpproxy: new session on a port 35000
> rtpproxy: lookup on a port 35000
> rtpproxy: addr1 filled in
> rtpproxy: addr2 filled in
> rtpproxy: session on port 35000 is cleaned up
>
>
> I am making the test on Linux 7.3. Both of the SIP UA is ata186. The
network
> structure is:
> ATA 1------------NAT 1 (Microsoft ICS)-------NAT 2 (Cisco 2600)--------SER
>        (192.168.0.1)                               (192.17.1.0)
>
> ATA 2------------------------------------------NAT2(Cisco
> 2600)--------------SER
>                                      (192.17.1.0)
>
> I'll make further test through Cisco 53 to PSTN.
>
>
> Younger Wang
>
>
>
> ----- Original Message ----- 
> From: "Maxim Sobolev" <sobomax at portaone.com>
> To: "Younger Wang" <wygmail at yeah.net>
> Cc: <serdev at lists.iptel.org>; <serusers at lists.iptel.org>
> Sent: Tuesday, July 08, 2003 12:33 PM
> Subject: Re: [Serusers] Re: [Serdev] nathelper updated to support RTP
proxy
>
>
> > I've applied a fix. Please update and let me know if it helps or not.
> >
> > Thanks!
> >
> > Sincerely,
> >
> > Maxim
> >
> > Younger Wang wrote:
> >
> > > The permission tribute of /var/run/rtpproxy.sock is srwxr-xr-x.
> > >
> > > ----- Original Message ----- 
> > > From: "Younger Wang" <wygmail at yeah.net>
> > > To: "Maxim Sobolev" <sobomax at portaone.com>
> > > Cc: <serdev at lists.iptel.org>; <serusers at lists.iptel.org>
> > > Sent: Tuesday, July 08, 2003 11:35 AM
> > > Subject: Re: [Serusers] Re: [Serdev] nathelper updated to support RTP
> proxy
> > >
> > >
> > >
> > >>The call is made from a Nated ata186. I got the message from rtpproxy:
> > >>
> > >>rtpproxy: can't accept connection on control socket: Invalid argument
> > >>rtpproxy: can't accept connection on control socket: Invalid argument
> > >>
> > >>
> > >>The corresponding Ser output:
> > >>
> > >>[root at sip-iptel ser]# ser -f rtpproxy.cfg
> > >> 0(29376) WARNING: could not rev. resolve 192.17.1.173
> > >>Listening on
> > >>              192.17.1.173 [192.17.1.173]:5060
> > >>Aliases:
> > >>WARNING: no fork mode
> > >>textops - initializing
> > >>stateless - initializing
> > >> 0(0) INFO: udp_init: SO_RCVBUF is initially 65535
> > >> 0(0) INFO: udp_init: SO_RCVBUF is finally 131070
> > >> 0(29376) ERROR: extract_mediaip: no `c=' in SDP
> > >> 0(29376) ERROR: get_rtpp_port: can't read reply from a RTP proxy
> > >> 0(29376) WARNING: get_body_len: Content-TYPE header absent!let's
assume
> > >
> > > the
> > >
> > >>content is text/plain ;-)
> > >> 0(29376) ERROR: on_reply processing failed
> > >> 0(29376) WARNING: get_body_len: Content-TYPE header absent!let's
assume
> > >
> > > the
> > >
> > >>content is text/plain ;-)
> > >> 0(29376) ERROR: on_reply processing failed
> > >> 0(29376) ERROR: extract_mediaip: no `c=' in SDP
> > >> 0(29376) ERROR: get_rtpp_port: can't read reply from a RTP proxy
> > >> 0(29376) ERROR: on_reply processing failed
> > >>
> > >>
> > >>Younger Wang
> > >>
> > >>
> > >>
> > >>----- Original Message ----- 
> > >>From: "Maxim Sobolev" <sobomax at portaone.com>
> > >>To: "Younger Wang" <wygmail at yeah.net>
> > >>Cc: <serdev at lists.iptel.org>; <serusers at lists.iptel.org>
> > >>Sent: Monday, July 07, 2003 12:54 PM
> > >>Subject: Re: [Serusers] Re: [Serdev] nathelper updated to support RTP
> > >
> > > proxy
> > >
> > >>
> > >>>Start rtpproxy with `-f' flag which will prevent it from going into
the
> > >>>daemon mode, make a test call and send me rtpproxy's output.
> > >>>
> > >>>-Maxim
> > >>>
> > >>>Younger Wang wrote:
> > >>>
> > >>>
> > >>>>Hi Maxim,
> > >>>>
> > >>>>I made the test. There is some problems:
> > >>>>1.   The source of RTP proxy did not compile. I replaced Makefile
with
> > >>>>      Makefile.linux. The following error message is given:
> > >>>>      cc  -o main.o -c main.c
> > >>>>      main.c: In function `setbindhost':
> > >>>>      main.c:83: structure has no member named `sin_len'
> > >>>>      make: *** [main.o] Error 1
> > >>>>
> > >>>>      I commented line 83 in main.c and it compiled and the
executive
> > >>
> > >>run.
> > >>
> > >>>>2    I run ser with the example script rtpproxy.cfg (modified to
work
> > >
> > > in
> > >
> > >>my
> > >>
> > >>>>network). rtpproxy is also started. I made a nat call and here is
the
> > >>
> > >>debug
> > >>
> > >>>>message:
> > >>>>
> > >>>> 0(29497) WARNING: could not rev. resolve 192.17.1.173
> > >>>>Listening on
> > >>>>              192.17.1.173 [192.17.1.173]:5060
> > >>>>Aliases:
> > >>>>WARNING: no fork mode
> > >>>>textops - initializing
> > >>>>stateless - initializing
> > >>>> 0(0) INFO: udp_init: SO_RCVBUF is initially 65535
> > >>>> 0(0) INFO: udp_init: SO_RCVBUF is finally 131070
> > >>>> 0(29497) ERROR: extract_mediaip: no `c=' in SDP
> > >>>> 0(29497) ERROR: get_rtpp_port: can't read reply from a RTP proxy
> > >>>> 0(29497) WARNING: get_body_len: Content-TYPE header absent!let's
> > >
> > > assume
> > >
> > >>the
> > >>
> > >>>>content is text/plain ;-)
> > >>>> 0(29497) ERROR: on_reply processing failed
> > >>>> 0(29497) WARNING: get_body_len: Content-TYPE header absent!let's
> > >
> > > assume
> > >
> > >>the
> > >>
> > >>>>content is text/plain ;-)
> > >>>> 0(29497) ERROR: on_reply processing failed
> > >>>> 0(29497) ERROR: extract_mediaip: no `c=' in SDP
> > >>>> 0(29497) ERROR: get_rtpp_port: can't read reply from a RTP proxy
> > >>>> 0(29497) ERROR: on_reply processing failed
> > >>>> 0(29497) ERROR: extract_mediaip: no `c=' in SDP
> > >>>> 0(29497) ERROR: get_rtpp_port: can't read reply from a RTP proxy
> > >>>> 0(29497) WARNING: get_body_len: Content-TYPE header absent!let's
> > >
> > > assume
> > >
> > >>the
> > >>
> > >>>>content is text/plain ;-)
> > >>>> 0(29497) ERROR: on_reply processing failed
> > >>>> 0(29497) WARNING: get_body_len: Content-TYPE header absent!let's
> > >
> > > assume
> > >
> > >>the
> > >>
> > >>>>content is text/plain ;-)
> > >>>> 0(29497) ERROR: on_reply processing failed
> > >>>> 0(29497) ERROR: extract_mediaip: no `c=' in SDP
> > >>>> 0(29497) ERROR: get_rtpp_port: can't read reply from a RTP proxy
> > >>>> 0(29497) ERROR: on_reply processing failed
> > >>>>
> > >>>>    In fact, it should not work because I did not tell ser  how to
> > >
> > > find
> > >
> > >>>>rtpproxy. But I did not find any information to do so.
> > >>>>
> > >>>>3.  In rtpproxy.cfg, I found the following script:
> > >>>>
> > >>>>if (search("User-Agent: Cisco ATA.*")) {
> > >>>>                setflag(1); # remember this is ATA
> > >>>>                force_rport();
> > >>>>                fix_nated_contact();
> > >>>>
> > >>>>   What force_rport() is for?  And in which module is it defined?
> > >>>>
> > >>>>4.  There is two option or parameters for rtpproxy.
> > >>>>     rtpproxy: usage: rtpproxy [-f] [-l address]
> > >>>>
> > >>>>     Is there more information about its usage other than message
> > >
> > > above?
> > >
> > >>>>5.  In README of module nathelper, I found:
> > >>>>
> > >>>>Name:   fix_nated_sdp()
> > >>>>Params: mode - 0x01 (add direction=active), 0x02 (rewrite media IP
> > >>>>        address with source address of the message)
> > >>>>Desc:   Rewrites SDP body in accordance with mode flag
> > >>>>Example:        if (search("User-Agent: Cisco ATA.*")
> > >>
> > >>{fix_nated_sdp(3);};
> > >>
> > >>>>Does fix_nated_sdp(3) means direction=active and rewrite media IP
> > >>
> > >>address
> > >>
> > >>>>with source address of the message?  And what does direction=active
> > >>
> > >>means?
> > >>
> > >>>>     And:
> > >>>>
> > >>>>Name:   force_rtp_proxy
> > >>>>Params: none
> > >>>>
> > >>>>So what does mean?
> > >>>>
> > >>>>
> > >>>>Your reply is so soon, Maxim.
> > >>>>
> > >>>>Younger Wang
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>>----- Original Message ----- 
> > >>>>From: "Maxim Sobolev" <sobomax at portaone.com>
> > >>>>To: <serusers at lists.iptel.org>
> > >>>>Cc: <serdev at lists.iptel.org>
> > >>>>Sent: Sunday, July 06, 2003 10:16 AM
> > >>>>Subject: [Serdev] nathelper updated to support RTP proxy
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>>>Folks,
> > >>>>>
> > >>>>>Today I've updated nathelper module to support RTP proxy. It would
> > >>>>>be nice if somebody can test it on platforms other than FreeBSD,
> > >>>>>because I don't have an access to such boxes right now. The RTP
> > >>>>>proxy itself can be downloaded from:
> > >>>>>
> > >>>>>https://demo.portaone.com/~sobomax/PortaSIP/rtpproxy/
> > >>>>>
> > >>>>>Any feedback is greatly appreciated.
> > >>>>>
> > >>>>>-Maxim
> > >>>>>P.S. I've committed it to the HEAD, those with 0.8.11 prerelease
> > >>>>>please apply the following patch:
> > >>>>>
> > >>>>>https://demo.portaone.com/~sobomax/nathelper.diff
> > >>>>>
> > >>>>>_______________________________________________
> > >>>>>Serdev mailing list
> > >>>>>serdev at lists.iptel.org
> > >>>>>http://lists.iptel.org/mailman/listinfo/serdev
> > >>>>
> > >>>>
> > >>>>_______________________________________________
> > >>>>Serusers mailing list
> > >>>>serusers at lists.iptel.org
> > >>>>http://lists.iptel.org/mailman/listinfo/serusers
> > >>>>
> > >>>>
> > >>>>
> > >>>
> > >>>
> > >>>_______________________________________________
> > >>>Serusers mailing list
> > >>>serusers at lists.iptel.org
> > >>>http://lists.iptel.org/mailman/listinfo/serusers
> > >>
> > >>_______________________________________________
> > >>Serdev mailing list
> > >>serdev at lists.iptel.org
> > >>http://lists.iptel.org/mailman/listinfo/serdev
> > >
> > >
> > > _______________________________________________
> > > Serusers mailing list
> > > serusers at lists.iptel.org
> > > http://lists.iptel.org/mailman/listinfo/serusers
> > >
> > >
> > >
> >
> >
> > _______________________________________________
> > Serusers mailing list
> > serusers at lists.iptel.org
> > http://lists.iptel.org/mailman/listinfo/serusers
>



More information about the sr-users mailing list