<div>Why don't you send SDP in the INVITE message?</div>
<div> </div>
<div>Jose Simoes<br><br> </div>
<div><span class="gmail_quote">On 2/1/06, <b class="gmail_sendername">Carla Ares</b> <<a href="mailto:carla.ares@gmail.com">carla.ares@gmail.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div><span class="e" id="q_109258aae434364a_0"><span class="gmail_quote"></span>Hi all,<br>
<div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<div><span>I have a problem with audio, when the destination of a call is natted and the other side is public. This problem is cause because the SDP info only is present in the 200 OK and in the ACK message.<br><br>I'm using ser (
8.14) with mediaproxy (1.2.1).<br><br>I have an H323 to SIP translator (and SIP to H323 too) connected to the PSTN and to the SIP Proxy (SER).<br>H323 is the origin of the call (public client), and SIP UAC is the destination (Natted client).
<br>My proxy is working in state full mode and has a public IP.<br><br>The H323 side is using slow start, so when it starts the transaction with an INVITE, it will not send the SDP info (it will send it in the ACK message).
<br>The proxy forwards this message to the destination.<br>SIP UAC, starts ringing. When we hooks off, the SIP UAC send an 200 OK with SDP message to the H323 side.<br><br>This is the 200 OK / SDP that the proxy receives from the SIP side.
<br><span style="FONT-STYLE: italic"><br>No. Time Source Destination Protocol Info</span><br style="FONT-STYLE: italic"><span style="FONT-STYLE: italic"> 488 28.488811 <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://200.68.89.2/" target="_blank">
200.68.89.2</a> <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://200.68.89.12/" target="_blank">200.68.89.12</a> SIP/SDP Status: <span style="FONT-WEIGHT: bold">200 OK, with session description
</span></span><br style="FONT-STYLE: italic"><span style="FONT-STYLE: italic"> Message body</span><br style="FONT-STYLE: italic"><span style="FONT-STYLE: italic"> Session Description Protocol</span><br style="FONT-STYLE: italic">
<span style="FONT-STYLE: italic"> Session Description Protocol Version (v): 0</span><br style="FONT-STYLE: italic"><span style="FONT-STYLE: italic"> Owner/Creator, Session Id (o): 700600 6015 6015 IN IP4
<a onclick="return top.js.OpenExtLink(window,event,this)" href="http://192.168.0.101/" target="_blank">192.168.0.101</a></span><br style="FONT-STYLE: italic"><span style="FONT-STYLE: italic"> Owner Username: 700600
</span><br style="FONT-STYLE: italic"><span style="FONT-STYLE: italic"> Session ID: 6015</span><br style="FONT-STYLE: italic"><span style="FONT-STYLE: italic"> Session Version: 6015</span><br style="FONT-STYLE: italic">
<span style="FONT-STYLE: italic"> Owner Network Type: IN</span><br style="FONT-STYLE: italic"><span style="FONT-STYLE: italic"> Owner Address Type: IP4</span><br style="FONT-STYLE: italic"><span style="FONT-STYLE: italic">
Owner Address: <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://192.168.0.101/" target="_blank">192.168.0.101</a></span><br style="FONT-STYLE: italic"><span style="FONT-STYLE: italic">
Session Name (s): AddPac Gateway SDP</span><br style="FONT-STYLE: italic"><span style="FONT-STYLE: italic"> Connection Information (c): IN IP4 <span style="FONT-WEIGHT: bold"><a onclick="return top.js.OpenExtLink(window,event,this)" href="http://192.168.0.101/" target="_blank">
192.168.0.101 </a></span></span><br style="FONT-STYLE: italic"><span style="FONT-STYLE: italic"> Connection Network Type: IN</span><br style="FONT-STYLE: italic"><span style="FONT-STYLE: italic"> Connection Address Type: IP4
</span><br style="FONT-STYLE: italic"><span style="FONT-STYLE: italic"> Connection Address: <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://192.168.0.101/" target="_blank">192.168.0.101
</a></span><br style="FONT-STYLE: italic"><span style="FONT-STYLE: italic"> Time Description, active time (t): 0 0</span><br style="FONT-STYLE: italic"><span style="FONT-STYLE: italic"> Session Start Time: 0
</span><br style="FONT-STYLE: italic"><span style="FONT-STYLE: italic"> Session Stop Time: 0</span><br style="FONT-STYLE: italic"><span style="FONT-STYLE: italic"> Media Description, name and address (m): audio 23018 RTP/AVP 18 8 0 101
</span><br style="FONT-STYLE: italic"><span style="FONT-STYLE: italic"> Media Type: audio</span><br style="FONT-STYLE: italic"><span style="FONT-STYLE: italic"> Media Port: 23018</span><br style="FONT-STYLE: italic">
<span style="FONT-STYLE: italic"> Media Proto: RTP/AVP</span><br style="FONT-STYLE: italic"><span style="FONT-STYLE: italic"> Media Format: ITU-T G.729</span><br style="FONT-STYLE: italic"><span style="FONT-STYLE: italic">
Media Format: ITU-T G.711 PCMA</span><br style="FONT-STYLE: italic"><span style="FONT-STYLE: italic"> Media Format: ITU-T G.711 PCMU</span><br style="FONT-STYLE: italic"><span style="FONT-STYLE: italic">
Media Format: 101</span><br style="FONT-STYLE: italic"><br>Following the ser.cfg, this 200 OK / SDP will make the proxy to use mediaproxy (use_media_proxy()), because the destination user is natted. So the mediaproxy module, will generate a lookup command to the
proxydispatcher.py. <br><br><span style="FONT-STYLE: italic">proxydispatcher[30535]: command lookup <a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:2281401749@200.68.89.10" target="_blank">2281401749@200.68.89.10
</a> <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://192.168.0.101:23018/" target="_blank">192.168.0.101:23018</a>:audio <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://200.68.89.2/" target="_blank">
200.68.89.2</a> <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://200.68.89.10/" target="_blank">200.68.89.10</a> remote <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://200.68.89.10/" target="_blank">
200.68.89.10</a> unknown AddPac=20SIP=20Gateway info=<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:from:1150316660@200.68.89.10" target="_blank">from:1150316660@200.68.89.10</a>,<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:to:1152464490@200.68.89.10" target="_blank">
to:1152464490@200.68.89.10</a>,fromtag:3512844671,totag:7b07717a4</span><br style="FONT-STYLE: italic"><span style="FONT-STYLE: italic">proxydispatcher[30535]: warning: trying to lookup session with non-existent id: '<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:2281401749@200.68.89.10" target="_blank">
2281401749@200.68.89.10</a>'</span><br style="FONT-STYLE: italic"><br>The proxydispatcher does not recognize that command because it has not generate the session before. So, the proxy forwards the 200 OK /SDP message without changing the SDP info. When the H323 sides receives that info, it thinks that it has to send RTP to the private IP.
<br><br>Then the H323 sends the ACK with SDP. <br><br>Then, we cannot ear audio in both sides. <br><br>Here is the problem, because, I didn't receive an INVITE with SDP that can create the session into the dispatcher.<br>
<br><br></span></div><span>A is public, B is natted<br><br>side A Proxy side B<br><br> INVITE without SDP<br> ----------><br> 100 Trying<br> <----------<br><br> INVITE without SDP
<br> ----------><br><br> 100 Trying<br> <----------<br> 180 Ringing<br> <----------<br> 180 Ringing<br> <----------<br><br> 200 OK SDP (B private IP)
<br> <----------<br> *1*<br> 200 OK SDP (B private IP)<br> <----------<br><br> ACK SDP (A public IP)<br> ----------><br> *2*<br> ACK SDP (mediaproxy public IP)
<br> ----------><br><br>......................................................<br> RTP from B<br> <----------------------<br> *3*<br>......................................................
<br><br><br>*1* The proxy must replace the private IP of the SDP, with the ip of the mediaproxy. The looku prequest does not work, because no session was found<br>*2* the proxy generates the session in the mediaproxy. So B thinks that the RTP must go to the mediaproxy. But A never knows the mediaproxy address.
<br>*3* RTP from A goes to anywhere, because A does not know where it is the private adrress of B.<br><br></span></blockquote></div><br><span><br>Do you know a solution to this? Is the sequence of the message all right? <br>
<br><br></span>Regards.<br><span>Carla<br><br><br><br></span></span></div><br>_______________________________________________<br>Serusers mailing list<br><a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:serusers@lists.iptel.org">
serusers@lists.iptel.org</a><br><a onclick="return top.js.OpenExtLink(window,event,this)" href="http://lists.iptel.org/mailman/listinfo/serusers" target="_blank">http://lists.iptel.org/mailman/listinfo/serusers</a><br><br><br></blockquote>
</div><br>