Maybe you can send some SIP traces, a generic diagram doesn't tell too much in this case.<br><br><div><span class="gmail_quote">On 11/24/06, <b class="gmail_sendername">hiSIPatH</b> <<a href="mailto:hisipath@gmail.com">
hisipath@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;">Hi all,<br><br>as suggested by Bogdan, i try to fix my issue with OptiPoint, using
<br>the "force_rport()" statement in my ser.cfg. I have tried several<br>changes but have still the same result.<br><br>I am able to register the OptiPoint...<br>optipoint------[Request REGISTER]------>SER<br>
optipoint<----[ 100 Trying ]--------SER<br>optipoint<----[ 401 Unauthorized ]--------SER<br>optipoint------[Request REGISTER]------>SER<br>optipoint<----[ 100 Trying ]--------SER<br>optipoint<----[ 200 OK ]--------SER
<br><br>but the when the OptiPoint sends an INVITE, the response from ser is sent to Src<br>Port: 5060 (5060), Dst Port: 5060 (5060) instead of the NATed port.<br><br>I use the nat-rtpproxy.5.0.cfg from the GettingStarted. Is there some
<br>thing more i have to change in the ser.cfg.<br><br>suggestions are wellcome.<br><br>thx in advance!!!<br><br><br>On 11/20/06, hiSIPatH <<a href="mailto:hisipath@gmail.com">hisipath@gmail.com</a>> wrote:<br>> Hi Bogdan,
<br>><br>> you are right. There is no rport in the VIA header field for the<br>> INVITE from the Optipoint.<br>><br>> Via: SIP/2.0/UDP <a href="http://192.168.204.5:5060">192.168.204.5:5060</a>;branch=z9hG4bK416072b30
<br>><br>> But for other UA you can notice this VIA header (received and rport<br>> parameter)...<br>> Via: SIP/2.0/UDP<br>> <a href="http://192.168.204.2:26010">192.168.204.2:26010</a>;received=89.xxx.xxx.xxx
;branch=z9hG4bK-d87543-fb641a689c2c295f-1--d87543-;rport=64365.<br>><br>> i will try to use the "force_rport()" to fix this issue...<br>><br>> thx again for the hint.<br>><br>><br>><br>><br>
> On 11/19/06, Bogdan Pintea <<a href="mailto:pintea@iptego.de">pintea@iptego.de</a>> wrote:<br>> > Your OptiPoint might not add the "rport" Via parameter (unfortunately,<br>> > your net trace is not too relevant), probably unlike your other Snom and
<br>> > Xlite clients.<br>> ><br>> > In this case, check if you have a "force_rport();" statement in you SER<br>> > cfg. See a NAT handling SER sample script otherwise, for how to add it,
<br>> > if missing; or try tune the UA to add it, at least in REGISTERs.<br>> ><br>> > Hth,<br>> > Bogdan.<br>> ><br>> > hiSIPatH wrote:<br>> > > Hi Michal,<br>> > ><br>
> > > Thx for the reply. It seems that there isn't such an option in the<br>> > > OptiPoint.<br>> > > But to be honest i am a little confused, because i am able to register<br>> > > my OptiPoint. So NAT seems to work with the REGISTER but doesn't with
<br>> > > the INVITE.<br>> > ><br>> > ><br>> > ><br>> > > On 11/16/06, Michal Matyska <<a href="mailto:michal@iptel.org">michal@iptel.org</a>> wrote:<br>> > >> Check whether there is configuration option "symetric signalling" (
e.g.<br>> > >> use the same port for sending requests and receiveng replies) in your<br>> > >> OptiPoint UEa and check that to be used.<br>> > >><br>> > >> The asymetric signaling does not work when the UE is behind NAT, the
<br>> > >> port is not open for replies.<br>> > >><br>> > >> The same applies to RTP streams, you have to setup the RTP to be<br>> > >> symetric.<br>> > >><br>> > >> Michal
<br>> > >><br>> > >> On Thu, 2006-11-16 at 13:19 +0100, hiSIPatH wrote:<br>> > >> > Hi all,<br>> > >> ><br>> > >> > i have a ser setup (CentOS 4.4/ser 0.9.6
) with several ip phones<br>> > >> > (SNOM320 and Xlite30) and every thing seems to work fine. The ser<br>> > >> > server has a public ip address 89.xxx.xxx.xxx and the ua are behind a<br>> > >> > NAT device (corporate FW).
<br>> > >> ><br>> > >> > I want now to add some OptiPoint420 SIP but was unable to get them<br>> > >> > working. That means that the registration is ok and calls to the<br>> > >> > Optipoints from other ua (xlite or Snom) work but i was unable to
<br>> > >> > place a call from Optipoint to other ua.<br>> > >> ><br>> > >> > In the trace you can notice that the INVITE is sent to ser with Src<br>> > >> > Port 38625 and Dst Port 5060. But the response from ser is sent to Src
<br>> > >> > Port: 5060 (5060), Dst Port: 5060 (5060). The result is of couse ICMP<br>> > >> > Destination unreachable (Port unreachable).<br>> > >> ><br>> > >> > I have rtp proxy and ser running on the same server and my
ser.cfg<br>> > >> > looks like the one from the SER GettingStarted<br>> > >> > <a href="http://siprouter.onsip.org/doc/gettingstarted/ch08s02.html">http://siprouter.onsip.org/doc/gettingstarted/ch08s02.html
</a>). I read<br>> > >> > the doc about "handling of NAT using RTP Proxy" but was unable to<br>> > >> > change the config to get this scenario with OptiPoint working. Has<br>> > >> > anyone managed to get OptiPoint to work with ser?
<br>> > >> ><br>> > >> > thx in advance?<br>> > >> ><br>> > >> > No. Time Source Destination<br>> > >> Protocol Info<br>> > >> > 14
8.907171 89.xxx.xxx.xxx 89.xxx.xxx.xxx<br>> > >> > SIP/SDP Request: INVITE<br>> > >> > <a href="mailto:sip:8001@registrar.mydomaine.com">sip:8001@registrar.mydomaine.com</a>;transport=udp, with session
<br>> > >> > description<br>> > >> ><br>> > >> > Frame 14 (972 bytes on wire, 972 bytes captured)<br>> > >> > Ethernet II, Src: AminoCom_02:02:02 (00:02:02:02:02:02), Dst:
<br>> > >> > AcerTech_9c:00:8d (00:00:e2:9c:00:8d)<br>> > >> > Internet Protocol, Src: 89.xxx.xxx.xxx (89.xxx.xxx.xxx), Dst:<br>> > >> > 89.xxx.xxx.xxx (89.xxx.xxx.xxx)<br>> > >> > User Datagram Protocol, Src Port: 38625 (38625), Dst Port: 5060 (5060)
<br>> > >> > Session Initiation Protocol<br>> > >> ><br>> > >> > No. Time Source Destination<br>> > >> Protocol Info<br>> > >> > 15
8.907394 89.xxx.xxx.xxx 89.xxx.xxx.xxx SIP<br>> > >> > Status: 407 Proxy Authentication Required<br>> > >> ><br>> > >> > Frame 15 (772 bytes on wire, 772 bytes captured)
<br>> > >> > Ethernet II, Src: AcerTech_9c:00:8d (00:00:e2:9c:00:8d), Dst:<br>> > >> > AminoCom_02:02:02 (00:02:02:02:02:02)<br>> > >> > Internet Protocol, Src: 89.xxx.xxx.xxx (
89.xxx.xxx.xxx), Dst:<br>> > >> > 89.xxx.xxx.xxx (89.xxx.xxx.xxx)<br>> > >> > User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 5060 (5060)<br>> > >> > Session Initiation Protocol
<br>> > >> > _______________________________________________<br>> > >> > Serusers mailing list<br>> > >> > <a href="mailto:Serusers@lists.iptel.org">Serusers@lists.iptel.org</a>
<br>> > >> > <a href="http://lists.iptel.org/mailman/listinfo/serusers">http://lists.iptel.org/mailman/listinfo/serusers</a><br>> > >><br>> > >> _______________________________________________
<br>> > >> Serusers mailing list<br>> > >> <a href="mailto:Serusers@lists.iptel.org">Serusers@lists.iptel.org</a><br>> > >> <a href="http://lists.iptel.org/mailman/listinfo/serusers">http://lists.iptel.org/mailman/listinfo/serusers
</a><br>> > >><br>> > > _______________________________________________<br>> > > Serusers mailing list<br>> > > <a href="mailto:Serusers@lists.iptel.org">Serusers@lists.iptel.org</a>
<br>> > > <a href="http://lists.iptel.org/mailman/listinfo/serusers">http://lists.iptel.org/mailman/listinfo/serusers</a><br>> > ><br>> ><br>> ><br>> > --<br>> > Bogdan Pintea<br>
> ><br>> > iptego GmbH - VoIP Security<br>> > <a href="http://www.iptego.de">http://www.iptego.de</a><br>> ><br>> ><br>><br>_______________________________________________<br>Serusers mailing list
<br><a href="mailto:Serusers@lists.iptel.org">Serusers@lists.iptel.org</a><br><a href="http://lists.iptel.org/mailman/listinfo/serusers">http://lists.iptel.org/mailman/listinfo/serusers</a><br></blockquote></div><br>