I cannot modify the H323 side, because I have no control of it. So, I need to adapt SER to work with.<br>
<br>
H323 could work in slow start and fast start. <br>
A call between a H323 fast start side and a natted SIP side, is working ok. Because, in that case, the INVITE has SDP.<br>
<br>
The problem I have is when H323 is working in slow start and the
B sides is a SIP UAC an it's natted. Because, the INVITE does not have
that SDP that creates the session in the proxydispatcher.<br>
The problem is on the mediaproxy module, because it only makes a <span style="font-weight: bold;">request</span>
command to the proxydispatcher when an ACK or INVITE is received. So,
if the first INVITE doesn't have SDP info, the 200 OK/SDP will not find
a session opened in the distpatcher.<br>
<br>
Is the sequence of message (shown below) according to the RFC of SIP?
or maybe it's a bug of the mediaproxy module? or the RFCs of SIP says
that the INVITE has to have always an SDP info?<br>
<br>
<br><br><div><span class="gmail_quote">On 2/1/06, <b class="gmail_sendername">Voipers Portugal</b> <<a href="mailto:voipers@gmail.com">voipers@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>But in H.323 it is not possible to use SDP in the INVITE? Does it
have to be slow start? You could always add the SDP to the message in
the H.323 to SIP converter (that is, if you can control it of course).</div><div><span class="e" id="q_109263ee1d42c9f9_1">
<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" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">carla.ares@gmail.com</a>
> wrote:</span>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0px 0px 0px 0.8ex; padding-left: 1ex;">Sides
A (the origin of the call), cannot send the SDP in the INVITE, because
it does not know the rtp information until the destination confirms his
rtp info.
<br><br>This cannot be done in another way, because H323 (slow start) works in that way.
<div><span><br><br><br>
<div><span class="gmail_quote">On 2/1/06, <b class="gmail_sendername">Voipers Portugal</b> <<a href="mailto:voipers@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">voipers@gmail.com</a>
> wrote:</span>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>Why don't you send SDP in the INVITE message?</div>
<div> </div>
<div>Jose Simoes<br><br> </div>
<div>
<div><span><span class="gmail_quote">On 2/1/06, <b class="gmail_sendername">Carla Ares</b> <<a href="mailto:carla.ares@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"> carla.ares@gmail.com
</a>> wrote:</span> </span></div>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0px 0px 0px 0.8ex; padding-left: 1ex;">
<div><span>
<div><span><span class="gmail_quote"></span>Hi all,<br>
<div>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<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 href="http://200.68.89.2/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
200.68.89.2</a> <a href="http://200.68.89.12/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">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 href="http://192.168.0.101/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">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 href="http://192.168.0.101/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">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 href="http://192.168.0.101/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
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 href="http://192.168.0.101/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">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 href="mailto:2281401749@200.68.89.10" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">2281401749@200.68.89.10
</a><a href="http://192.168.0.101:23018/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">192.168.0.101:23018</a>:audio <a href="http://200.68.89.2/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
200.68.89.2</a> <a href="http://200.68.89.10/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">200.68.89.10</a> remote <a href="http://200.68.89.10/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
200.68.89.10</a> unknown AddPac=20SIP=20Gateway info=<a href="mailto:from:1150316660@200.68.89.10" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">from:1150316660@200.68.89.10</a>,<a href="mailto:to:1152464490@200.68.89.10" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
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 href="mailto:2281401749@200.68.89.10" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
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></span></div>_______________________________________________<br>Serusers mailing list<br><a href="mailto:serusers@lists.iptel.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
serusers@lists.iptel.org</a><br><a href="http://lists.iptel.org/mailman/listinfo/serusers" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://lists.iptel.org/mailman/listinfo/serusers</a><br><br><br></blockquote>
</div><br></blockquote></div><br></span></div></blockquote></div><br>
</span></div></blockquote></div><br>