[Serusers] SER and rtpproxy

Klaus Darilion klaus.mailinglists at pernau.at
Mon Mar 1 13:58:36 CET 2004


Hi Fabio!

Just replace your condition in the reply route with my condition.

No, you don't need to any special commands for the rtpproxy.

Yes I have sample cfg - i already postet is ome time ago - search the 
archive.

regards,
klaus

PS: cc to the list

Fabio Silvestri wrote:

> Well, where do I need to include that code if { } on my ser.cfg?
> 
> Do you have a sample cfg?
> 
> How do I need to run rtpproxy, have some special command line?
> 
> On Mon, 1 Mar 2004, Klaus Darilion wrote:
> 
> 
>>Date: Mon, 01 Mar 2004 09:35:12 +0100
>>From: Klaus Darilion <klaus.mailinglists at pernau.at>
>>To: Fábio Silvestri <fabio at informatec.com.br>
>>Cc: serusers at lists.iptel.org
>>Subject: Re: [Serusers] SER and rtpproxy
>>
>>
>>
>>Fábio Silvestri wrote:
>>
>>
>>>Hi!
>>>
>>>After a long search on maillinst, I'm trying to run SER with rtpproxy, 
>>>for resolve problems with SIP UA (ata186) behind a nat, but I'm still 
>>>get in trouble.
>>>
>>>I have setup ser.cfg to use rtpproxy, like this:
>>>
>>>...
>>>    if (method=="INVITE") {
>>>        log(1,"INVITE\n");
>>>        fix_nated_sdp("1");
>>>        record_route();
>>>        force_rport();
>>>        setflag(1);
>>>        force_rtp_proxy();
>>>        t_on_reply("1");
>>>    }
>>>...
>>>onreply_route[1] {
>>>        log(1, ">=====> reply 1\n");
>>>       if ((status=~"[12][0-9][0-9]")) {
>>>          force_rtp_proxy();
>>>        }
>>>}
>>>...
>>>
>>>But I get this error on syslog:
>>>
>>> 0(5463) ERROR: extract_mediaip: no `c=' in SDP
>>>
>>
>>This will happen when you try to rewrite a response without sdp, e.g. 
>>100 trying, 180 ringing....
>>
>>I'm unsing:
>>	if ( (status=~"200" || status=~"183") ) {
>>            force_rtp_proxy();
>>
>>
>>>I'm running rtpproxy, on linux shell without any parameters.
>>>
>>>Does anybody knows what this means that message, and how to solve, a 
>>>ser.cfg for rtpproxy, and others tips will be helpfull...
>>>
>>>Regards.
>>>
>>
> 




More information about the sr-users mailing list