Re: [Linphone-developers] oddities with Linphone's handling of USB camera / microphone

[Jim Diamond]

On Fri, Jul 17, 2009 at 23:15 (+0200), Simon Morlat wrote:

Hi Simon,

> It seems that the video stream you receive is seriously damaged.
Indeed!

> Apparently the network mtu between the two phones is uncommon.
OK, it probably is.  I had a VPN running between my home and my wok
LAN, and the MTU of the VPN interface is (according to ifconfig) 1356,
compared to 1500 for my wireless interface.

So I tried the program without the VPN, and this time it worked (with
some complaints, see below).

> It is perhaps not detected correctly by the remote linphone, causing
> truncated packets or more likely packet losses.  A full log (until
> termination) would confirm this thanks to the statistics displayed
> at each end of call.
Mea culpa.  Here is what I think you are looking for, when I am trying
to use linphone with the VPN running:

linphone-warning : ms_AVdecoder_process: error -1.
linphone-warning : ms_AVdecoder_process: error -1.
linphone-message : DNS resolution with 131.162.131.135:5060
linphone-message : getaddrinfo returned the following addresses:
linphone-message : 131.162.131.135 port 5060
linphone-message : eXosip: here is the resolved destination host=131.162.131.135
linphone-message : allocating transaction ressource 5 354424296
linphone-message : allocating NICT context
linphone-message : DNS resolution with 131.162.131.135:5060
linphone-message : getaddrinfo returned the following addresses:
linphone-message : 131.162.131.135 port 5060
linphone-message : Message sent: (to dest=131.162.131.135:5060)
BYE sip:address@hidden:5060 SIP/2.0^M
Via: SIP/2.0/UDP 192.168.1.3:5060;rport;branch=z9hG4bK378288970^M
From: Jim Diamond <sip:address@hidden>;tag=1133099083^M
To: <sip:address@hidden>;tag=1301838161^M
Call-ID: 354424296^M
CSeq: 21 BYE^M
Contact: <sip:address@hidden:5060>^M
Max-Forwards: 70^M
User-Agent: Linphone/3.0.0 (eXosip2/3.1.0)^M
Content-Length: 0^M
^M

linphone-message : cb_sndbye (id=5)
linphone-message : eXosip: timer sec:0 usec:100000!
linphone-message : oRTP-stats:
   Audio session's RTP statistics :
linphone-message :  number of rtp packet sent=244
linphone-message :  number of rtp bytes sent=11753 bytes
linphone-message :  number of rtp packet received=240
linphone-message :  number of rtp bytes received=14315 bytes
linphone-message :  number of incoming rtp bytes successfully delivered to the a
pplication=13304
linphone-message :  number of times the application queried a packet that didn't
 exist=494
linphone-message :  number of rtp packet lost=0
linphone-message :  number of rtp packets received too late=12
linphone-message :  number of bad formatted rtp packets=0
linphone-message :  number of packet discarded because of queue overflow=0
linphone-message : ms_filter_unlink: MSAlsaRead:0x919e710,0-->MSSpeexEnc:0x91a72
f8,0
linphone-message : ms_filter_unlink: MSDtmfGen:0x91c1710,0-->MSAlsaWrite:0x91b4a
b8,0
linphone-message : ms_filter_unlink: MSSpeexEnc:0x91a72f8,0-->MSRtpSend:0x91a12f
8,0
linphone-message : ms_filter_unlink: MSRtpRecv:0x91a6380,0-->MSSpeexDec:0x91c17e
0,0
linphone-message : ms_filter_unlink: MSSpeexDec:0x91c17e0,0-->MSDtmfGen:0x91c171
0,0
linphone-message : MSTicker thread exiting
linphone-message : oRTP-stats:
   Video session's RTP statistics :
linphone-message :  number of rtp packet sent=13
linphone-message :  number of rtp bytes sent=13582 bytes
linphone-message :  number of rtp packet received=65
linphone-message :  number of rtp bytes received=54113 bytes
linphone-message :  number of incoming rtp bytes successfully delivered to the a
pplication=53133
linphone-message :  number of times the application queried a packet that didn't
 exist=487
linphone-message :  number of rtp packet lost=0
linphone-message :  number of rtp packets received too late=0
linphone-message :  number of bad formatted rtp packets=0
linphone-message :  number of packet discarded because of queue overflow=0
linphone-message : ms_filter_unlink: MSStaticImage:0x9193328,0-->MSPixConv:0x919
30b8,0
linphone-message : ms_filter_unlink: MSPixConv:0x91930b8,0-->MSSizeConv:0x919300
0,0
linphone-message : ms_filter_unlink: MSSizeConv:0x9193000,0-->MSTee:0x9193368,0
linphone-message : ms_filter_unlink: MSTee:0x9193368,0-->MSMpeg4Enc:0x91704e8,0
linphone-message : ms_filter_unlink: MSMpeg4Enc:0x91704e8,0-->MSRtpSend:0x91a1e2
0,0
linphone-message : ms_filter_unlink: MSRtpRecv:0x9193420,0-->MSMpeg4Dec:0x919321
8,0
linphone-message : ms_filter_unlink: MSMpeg4Dec:0x9193218,0-->MSVideoOut:0x91923
18,0
linphone-message : ms_filter_unlink: MSTee:0x9193368,1-->MSVideoOut:0x9192318,1
linphone-message : MSTicker thread exiting
linphone-message : ms_filter_link: MSStaticImage:0x91a1de0,0-->MSPixConv:0x91930
b8,0
linphone-message : ms_filter_link: MSPixConv:0x91930b8,0-->MSVideoOut:0x9193368,
0
linphone-message : Using yuv overlay.



> You can try to configure manually the mtu of the other phone (in
> configuration box, network tab) and retry.
Setting the remote linphone's MTU to 1200 worked like a charm.  Thanks
for the precise solution!

Is this a bug that should be formally documented somewhere?  (Or
fixed, if the fix is "obvious"?)

> From what I see it is unrelated with the fact of using the webcam's
> microphone or not.
Yes, so it seems.  I will have to play around with the webcam and get
back to you on that.  However, a solution to this other problem is a
big help for me.

Thanks.
                                Jim