[Users] Problems with Mediaproxy. Bad Port.

[Ricardo Martinez]

Hello list. 
I'm having a problem with my mediaproxy box. I have a NAT'd client (a softphone) calling to a SIP-H323 conversor through my OpenSER-Mediaproxy box and then to a Cisco Call Manager (it's a very weird configuration). Anyway, the problem presents when the 200 - OK message arrives from my conversor, the SDP part indicate the media address (10.10.148.230) and port (16952) where the remote endpoint will listen RTP, despite of this the mediaproxy open a session for the port 17360.  The escenario is something like this.
100.100.148.248 ------- 100.100.148.246 ----- 100.100.154.36 ------ 100.100.154.119 ---- 100.100.148.230
Softphone	      OpenSer/Mediaproxy      Proxy Sip             siph323 conversor         Call Manager.H323

Please check the log from the mediaproxy and the execution of the "sessions.py" utility, plus the OK message.
U 100.100.154.36:5060 -> 100.100.148.246:5060 
SIP/2.0 200 OK. 
Via: SIP/2.0/UDP 100.100.148.246;branch=z9hG4bK67ea.aa12dc97.0. 
Via: SIP/2.0/UDP 192.168.1.101;received=100.100.148.248;rport=46096;branch=z9hG4bKc0a801650000001d4533a0ee00007c2900000011.
Record-Route: <sip:100.100.154.36;ftag=2214787970;lr=on>. 
Record-Route: <sip:7072408196 at 100.100.148.246:5060;nat=yes;ftag=2214787970;lr=on>. 
From: "unknown"<sip:5502408196 at sip.desa.mydomain.net>;tag=2214787970. 
To: <sip:7072408196 at sip.desa.mydomain.net>;tag=2260729709. 
Call-ID: A2304B7B-AA05-42C5-A467-C16B1BD9102A at 192.168.1.101. 
Cseq: 2 INVITE. 
Date: Mon, 16 Oct 2006 15:10:37 GMT. 
Server: siph323. 
Content-Type: application/sdp. 
Content-Length: 162. 
Contact: sip:7072408196 at 100.100.154.119. 
. 
v=0. 
o=100.100.154.119 1 505533324 IN IP4 100.100.154.119. 
s=SIP Library call. 
c=IN IP4 100.100.148.230. 
t=3370000237 0. 
m=audio 16952 RTP/AVP 0. 
a=rtpmap:0 PCMU/8000. 
Oct 16 12:12:00 sip mediaproxy[18289]: lookup A2304B7B-AA05-42C5-A467-C16B1BD9102A at 192.168.1.101 100.100.148.230:16952:audio 100.100.154.36 sip.desa.mydomain.net local sip.desa.mydomain.net unknown siph323 info=from:5502408196 at sip.desa.mydomain.net,to:7072408196 at sip.desa.mydomain.net,fromtag:2214787970,totag:2260729709
Oct 16 12:12:00 sip mediaproxy[18289]: execution time: 0.48 ms 
Oct 16 12:12:00 sip mediaproxy[18289]: session A2304B7B-AA05-42C5-A467-C16B1BD9102A at 192.168.1.101: caller signed in from 100.100.148.248:49154 (RTP) (will return to 100.100.148.248:49154)
Oct 16 12:12:00 sip mediaproxy[18289]: session A2304B7B-AA05-42C5-A467-C16B1BD9102A at 192.168.1.101: called signed in from 100.100.148.230:17360 (RTP) (will return to 100.100.148.230:17360)
[root at sip ]# /usr/src/mediaproxy-1.7.2/mediaproxy/sessions.py 
Caller Via Called Status Duration Codec Type Traffic 
------------------------------------------------------------------------------------------------------------------------
100.100.148.248:49154 - 100.100.148.246:60022 - 100.100.148.230:17360 active 0'39" G711u Audio 336.91k/669.53k/332.62k
Total traffic: 79.69kbps/78.12kbps/157.81kbps (in1/in2/out) 
Session count: 1 
Proxy version: 1.7.2 
Doing more debugs i discover the RTP traffic coming from the 100.100.148.230 it has source port 17360, but the listening port is not the same (i guess is the one indicated in the SDP). Why mediaproxy assumes the 17360 port is for listening too and ommit the SDP 16952 port ?
Is this maybe an asymmetric regarding the RTP media?. If so, i added this line into the rtp-asymmetric-clients file: 
# 
# Lines starting with a '#' character or empty lines are ignored. 
# Put a User-Agent name or regular expression per line. 
# Check is case insensitive. 
# 
# This file should only list SIP clients that are asymmetric regarding 
# the RTP media streams. For clients that are asymmetric regarding the SIP 
# signaling, use the equivalent SIP version of this file. 
# Clients that are asymmetric for both SIP signaling as well as RTP media 
# streams should go in both files. 
# 
siph323 
But not solve the problem. 
Can someone help me here? 
Thanks in advance 
Regards 
Ricardo Martinez.- 
RedVoiss. 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20061017/713800e5/attachment.htm>