x-rtppr...@sidell.org wrote:
> I'm trying to get rtpproxy running with kamailio ser.  The problem is
> that I'm only getting audio in one direction, when both clients need
> to be nated.  From the logs, it looks like the originating client is
> getting set up correctly, but when ser call force_rtp_proxy() when it
> handles the OK from the receiving client, rtpproxy returns a 0 (zero)
> port number for that end.  This causes ser to fail to rewrite the SDP
> info for that client.
> 
> Below is the rtpproxy log output.  What looks strange is the "lookup
> request failed" line, and then the sending reply "3560_8 0
> 174.133.24.130", with the 0 port number.
> 
> Anyone know what I'm doing wrong?
> 
> Here is the setup for the originating client:
> 
>> DBUG:handle_command: received command "3560_7 
>> Uc107,119,100,106,0,105,98,8,3,101 
>> YTc5OTljZTc4OTFjNDQwZDYxZTVhMTUzMzQ0ZTNkMGE. 64.105.44.39 16548 ae213634;0"
>> INFO:handle_command: new session 
>> YTc5OTljZTc4OTFjNDQwZDYxZTVhMTUzMzQ0ZTNkMGE., tag ae213634;0 requested, type 
>> strong
>> INFO:handle_command: new session on a port 64680 created, tag ae213634;0
>> INFO:handle_command: pre-filling caller's address with 64.105.44.39:16548
>> DBUG:doreply: sending reply "3560_7 64680 174.133.24.130"
> 
> Here is the setup for the receiving client:
> 
>> DBUG:handle_command: received command "3560_8 Lc107,0,8,101 
>> YTc5OTljZTc4OTFjNDQwZDYxZTVhMTUzMzQ0ZTNkMGE. 64.105.44.41 3000 ae213634;1 
>> bf2ce529baeb74e;1"
>> INFO:handle_command: lookup request failed: session 
>> YTc5OTljZTc4OTFjNDQwZDYxZTVhMTUzMzQ0ZTNkMGE., tags 
>> ae213634;1/bf2ce529baeb74e;1 not found
>> DBUG:doreply: sending reply "3560_8 0 174.133.24.130"
> 
> This is when the call is terminated:
> 
>> DBUG:handle_command: received command "3560_9 D 
>> YTc5OTljZTc4OTFjNDQwZDYxZTVhMTUzMzQ0ZTNkMGE. bf2ce529baeb74e ae213634"
>> INFO:handle_delete: forcefully deleting session 0 on ports 64680/0
>> INFO:remove_session: RTP stats: 0 in from callee, 0 in from caller, 0 
>> relayed, 0 dropped
>> INFO:remove_session: RTCP stats: 0 in from callee, 0 in from caller, 0 
>> relayed, 0 dropped
>> INFO:remove_session: session on ports 64680/0 is cleaned up
>> DBUG:doreply: sending reply "3560_9 0"

Mark,

0 means the proxy cannot locate the session. For some reason the proxy 
requests stream #0 in INVITE, while stream #1 in the 200 OK. I am not 
sure why it does so, can you please send us you kamalio configuration file?

Regards,
-- 
Maksym Sobolyev
Sippy Software, Inc.
Internet Telephony (VoIP) Experts
T/F: +1-646-651-1110
Web: http://www.sippysoft.com
MSN: sa...@sippysoft.com
Skype: SippySoft
_______________________________________________
Users mailing list
Users@rtpproxy.org
http://lists.rtpproxy.org/mailman/listinfo/users

Reply via email to