On Mon, Mar 06, 2006 at 11:26:12AM +0100, Vadim Lebedev wrote:
> Matthias Schneider wrote:
>
> >Hi,
> >
> >trying out the video functionality of wengophone-classic (using the cvs
> >version revision 4179)
> >with an asterisk server's loopback extension I encountered the following
> >problem:
> >
> >Sniffing on the SIP signaling traffic shows the follpwing advertised video
> >capability in the SDP
> >part of the INVITE message, indicating a video port of UDP/RTP/10700:
> >
> > Media Description, name and address (m): video 10700 RTP/AVP 34
> > Media Type: video
> > Media Port: 10700
> > Media Proto: RTP/AVP
> > Media Format: ITU-T H.263
> > Media Attribute (a): rtpmap:34 H263/90000/1
> > Media Attribute Fieldname: rtpmap
> > Media Attribute Value: 34 H263/90000/1
> >
> >Interestingly the wengophone debug output reveals that the video port
> >shall be 10602:
> >
> >...
> >Starting video stream from port: 10602 to 192.168.134.1:10664
> >...
> >
> >which can be confirmed by a netstat -lpn
> >
> >Proto Recv-Q Send-Q Local Address Foreign Address State
> >PID/Program name
> >udp 0 0 0.0.0.0:5060 0.0.0.0:*
> >16367/wengophone
> >udp 3224 0 0.0.0.0:10600 0.0.0.0:*
> >16367/wengophone
> >udp 0 0 0.0.0.0:10601 0.0.0.0:*
> >16367/wengophone
> >udp 0 0 0.0.0.0:10602 0.0.0.0:*
> >16367/wengophone
> >udp 0 0 0.0.0.0:10603 0.0.0.0:*
> >16367/wengophone
> >
> >So all the returning video traffic from the asterisk server is sent to the
> >port 10700, where
> >wengophone is not listening. A change of wifo/trunk/eXosip/phapi/phapi.c
> >
> >/usr/src/wengophone/1.0/wifo/trunk/eXosip/phapi# diff phapi.c.sav phapi.c
> >365c365
> >< MY_DLLEXPORT phConfig_t phcfg = { "10600", "", "10700", "",
> >---
> >
> >
> >>MY_DLLEXPORT phConfig_t phcfg = { "10600", "", "10602", "",
> >>
> >>
> >
> >fixes this problem. I wonder how anyone could try out the video
> >functionality with this mismatch.
> >Or am I missing a point here?
> >
> >
>
> Nice catch Mattias,
> Thanks a lot.
Nice catch indeed. Why was it working ? Most people are behind a NAT.
When you send your first video RTP packet with source port 10602 your
router will open a udp NAT entry for you, using this port and your
local IP. So when the rtp proxy sends you other party's packets your
router sends it to you on port 10602 using the nat table.
>
> >Another issue I do not yet understand correctly is the listen on ports
> >10601 and 10603 which
> >should not be necessary if symmetric RTP is used.
> >
> 10601 and 10603 are for RTCP....
>
> >Furthermore I would like to ask about the state
> >of the mpeg4 / H264 support. Analysing the SDP in the INVITE messages this
> >capability is not
> >announced although it is enabled in the configuration dialogue.
> >
> >
> >
MPEG4 support is working, you just need to put it first in phapi's
codecs list (won't work using the GUI, i disabled it on purpose).
I could show you how to enable it with a patch. Also be aware that a
hack is used to make the RTP packets go through our SIP servers; we
modify the payload number to be the one of H263 (and not MPEG4).
H264 is mostly working using libavcodec's x264 wrapper, but there is
no RTP encapsulation, so it's pretty useless since packets won't be
splitted (and as a result will be dropped by the first router).
>
> David (krp) will answer better than me to that one...
>
> >Thanks a lot in advance,
> >Matthias
> >
> >
> >
> >
> >
> >
> >___________________________________________________________
> >Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
> >_______________________________________________
> >Wengophone-devel mailing list
> >[email protected]
> >http://dev.openwengo.com/mailman/listinfo/wengophone-devel
> >
> >
> >
> >
> >
>
> _______________________________________________
> Wengophone-devel mailing list
> [email protected]
> http://dev.openwengo.com/mailman/listinfo/wengophone-devel
--
David Ferlier -- [EMAIL PROTECTED]
"Humor is mankind's greatest blessing."
-- Mark Twain
_______________________________________________
Wengophone-devel mailing list
[email protected]
http://dev.openwengo.com/mailman/listinfo/wengophone-devel
