**** BEGIN LOGGING AT Fri Jun 24 02:59:58 2016
Jun 24 03:07:11 <gry> Turns out that Firefox instance crashed while doing a Windows upgrade. Darn. I better get my notes together and get some things done.
Jun 24 03:09:16 <Juest> :|
Jun 24 03:10:35 <Oksana> :?
Jun 24 03:11:11 <Oksana> By the way, am I the only one having issues with imgur , does it work for you, or does it not-work for you?
Jun 24 03:15:14 <Juest> Works fine
Jun 24 06:08:37 <Juest> gry now it doesnt let me
Jun 24 06:08:42 <Juest> return
Jun 24 06:45:49 <KotCzarny> vajb: yes, there is /tmp/ file that you can write commands
Jun 24 11:49:40 <zGrr> moin 
Jun 24 20:56:59 <Juest> Apparently Voice Calls work properly, so does IM
Jun 24 20:57:22 <Juest> but not SIP presence and calls stop working as soon video is attempted
Jun 24 21:03:27 <Sicelo> ?
Jun 24 21:04:20 <Juest> Damnit timezones
Jun 25 00:22:11 <DocScrutinizer05> SIP presence is a non-satndard SIP extension. Video: I never seen it working but that's mainly been for lack of support by my service provider, anyway I never seen maemo SIP UI quit on trying video
Jun 25 00:23:15 <DocScrutinizer05> possibly the service provider sends a BYE to you when you announce you want to initiate/chnage-to a *video* session
Jun 25 00:25:20 <DocScrutinizer05> again ethereal is your friend, check the Session Description and which codecs are offered/requested and what's the response
Jun 25 00:25:54 <DocScrutinizer05> ethereal even has very nice dissectors for all that stuff
Jun 25 00:26:13 <DocScrutinizer05> almost self explanatory
Jun 25 00:28:17 <Juest> Linphone does video, tested already.
Jun 25 00:28:42 <Juest> Just with her, Jingle and SIP video /does not work *at all* /
Jun 25 00:30:23 <DocScrutinizer05> you *might* be interestef in this little cmdline hack: http://talk.maemo.org/showthread.php?p=1022444  - take care to apply a filter for the ethereal traffic when you use this (modified for WLAN instead ISI) to monitor the VoIP traffic. Otherwise you get an avalanche of self referential logging
Jun 25 00:31:14 <DocScrutinizer05> again, this is no help channel for linphone
Jun 25 00:31:25 <Juest> Not asking linphone help :|
Jun 25 00:31:31 <Juest> but video call help
Jun 25 00:31:37 <DocScrutinizer05> neither jingle
Jun 25 00:33:14 <DocScrutinizer05> all relevant data for maemo SIP video can get gathered by using ethereal on device as suggested above
Jun 25 00:33:58 <Juest> wireshark-like ?
Jun 25 00:34:18 <DocScrutinizer05> ethereal/wireshark, I forget which is the recent name
Jun 25 00:35:01 <DocScrutinizer05> prolly wireshark, yes
Jun 25 00:35:23 <Juest> aka you're telling us to capture the "event"
Jun 25 00:35:40 <DocScrutinizer05> if you want to put it that way, yes
Jun 25 00:36:32 <DocScrutinizer05> the only effective way to debug SIP issues is to look what's going on on SIP protocol level
Jun 25 00:38:19 <Juest> Voice calls work great, the issue is when any video is attempted it just stops responding
Jun 25 00:38:39 <DocScrutinizer05> when your client receives a session description that's not compliant with its capabilities, or when other end sends an error because of similar problem there, then the session will abort. That's normal
Jun 25 00:39:05 <DocScrutinizer05> yes, understood. Sesion Descriptions differ between voice calls and video calls
Jun 25 00:40:30 <DocScrutinizer05> when you switch on video, the client tries to negotiate a new session (description) with far end
Jun 25 00:40:52 <DocScrutinizer05> since a new RTP channel and a associated video codec is needed
Jun 25 00:41:03 <Juest> i do not even receive video calls
Jun 25 00:41:21 <DocScrutinizer05> en passant a new audio channel description mightt get negotiated too
Jun 25 00:41:56 <DocScrutinizer05> sorry, I don't understand what you meant by >>i do not even receive video calls<<
Jun 25 00:43:44 <Juest> Anything that involves video calls = doesnt work properly
Jun 25 00:45:04 <DocScrutinizer05> and I explained above WHY that might be the case
Jun 25 00:45:37 <Juest> Jingle barely worked, Skype on maemo crashes when video is attempted and i never receive a sip video call and if its attempted mid-call the call dies
Jun 25 00:45:43 <DocScrutinizer05> so either you want to check if we can find the reason and possibly fix it, or you contine to state "video doesn't work" and I'm out
Jun 25 00:47:20 <DocScrutinizer05> please understand that it's worth nothing in this context to list what works or doesn't work
Jun 25 00:48:09 <DocScrutinizer05> the only way to takle this is looking at either error logs or traffic dump
Jun 25 00:48:12 <Juest> didnt you just said you didnt understand?
Jun 25 00:48:16 <Juest> Okay
Jun 25 00:48:24 <Juest> i'll do that
Jun 25 00:49:01 <DocScrutinizer05> alas maemo telepathy logs are pathetic at best, rather non-existent at all
Jun 25 00:49:16 <DocScrutinizer05> so your best chance is wireshark
Jun 25 00:51:46 * DocScrutinizer05 suspects that maemo only offers h.263 video codec and that might not be very popular and commonly supported anymore
Jun 25 00:52:08 <Juest> umm, Jingle and Skype are on H264....
Jun 25 00:52:42 <DocScrutinizer05> so unless far end offers same h.263 codec, a video call will fail (if the assumption is corect)
Jun 25 00:53:35 <DocScrutinizer05> N900 only can do 'low profile' video on the h.26x codecs
Jun 25 00:55:38 <DocScrutinizer05> err maybe it's called baseline profile
Jun 25 00:56:20 <DocScrutinizer05> H.254 Baseline Profile (BP): Primarily for lower-cost applications with limited computing resources, this profile is used widely in videoconferencing and mobile applications.
Jun 25 00:56:32 <DocScrutinizer05> H.264 even
Jun 25 00:57:15 <Juest> And Skype shouldnt crash on video then -_-
Jun 25 00:57:42 <DocScrutinizer05> aha
Jun 25 00:58:01 <DocScrutinizer05> Skype crashes too?
Jun 25 00:59:11 <Juest> As soon she taps Camera = "boom" literally
Jun 25 01:00:03 <DocScrutinizer05> when SIP and Skype both crash, odds are it's either both 'protocols' switched from H.263 / H.254 base line to more CPU power demanding codecs during the last 6 years, or your device's DSP is defect on a hw level
Jun 25 01:00:49 <DocScrutinizer05> dang, s H.254 H.264
Jun 25 01:02:34 <DocScrutinizer05> though the user agents /clients should handle a "codec not supported" gracefully, falling back to audio-only and possibly even telling in plaintext why video isn't possible. a crash would suggest sth is odd on hw level. maybe a peek into syslog could help reveal the root cause
Jun 25 01:03:38 <DocScrutinizer05> I wonder if video recording still works on same device where video calls crash
Jun 25 01:04:17 <DocScrutinizer05> ooh ugh! is the device overclocked?
Jun 25 01:05:01 <Juest> in summary: Jingle barely works, SIP video calls do not function at all (call ghosts on my side and ends on her side if video activated mid-call and i never receive a call if she tries to video call from the start) and Skype crashes on her side on any attempt to send video
Jun 25 01:05:21 <DocScrutinizer05> or rather: has it been used in overclocked mode for extended periods of time?
Jun 25 01:07:57 <DocScrutinizer05> reportedly the DSP which does the H.26x encoding is particularly prone to wearing out permanently and then crashing when operated in overclocked mode
Jun 25 01:09:24 <Juest> Damnit, its Saturday in Australia and I'm not the maemo user, i am unable to answer such device questions. Oksana is the user who i am helping/asking on behalf
Jun 25 01:09:27 <DocScrutinizer05> actually it's even notorious for not being that stable and wearing out eventually on non-OC devices
Jun 25 01:10:00 <DocScrutinizer05> dammit then why isn't it HER who asks in here?
Jun 25 01:10:49 <Juest> Because she's either busy or unavailable
Jun 25 01:11:01 <DocScrutinizer05> when you're asking on behalf, you should receive the answers on behalf as well, no?
Jun 25 01:11:32 <Juest> I cant answer your device questions but sure, i am going to tell her to put a network tracer on her device
Jun 25 01:12:36 <DocScrutinizer05> *sigh*, we already changed investigation vecor towards why Skype also crashes and that it suggests there might be a hw problem
Jun 25 01:14:26 <DocScrutinizer05> a colorblind in a phonecall to the Police ATF guy: "So what do next? the display shows 10s!!"  Reply: "cut the green wire!"
Jun 25 01:17:47 <DocScrutinizer05> you're aware that oksana is ex-councilor and knows about this IRC channel and the chanlog, and she also knows she can ask me any time and will get an answer?
Jun 25 01:18:05 <Juest> Yes
Jun 25 01:18:17 <Juest> but she apparently somewhat isolated from everyone
Jun 25 01:18:22 <Juest> and i am helping her on my own
Jun 25 01:18:30 <DocScrutinizer05> so I don't see how you in a role as proxy will simplify things
Jun 25 01:18:45 <Juest> At least i tried
Jun 25 01:19:03 <Juest> or trying
Jun 25 01:23:26 <DocScrutinizer05> when wikiwide err oksana can't use IRC and instead has other non-public channels to communicate to you, then please you chime in here next time when you have contact to her realtime, so we at least can answer the "multiple choice part" of the test in a timely manner
Jun 25 01:24:57 <Juest> I'll let you know
Jun 25 01:25:01 <DocScrutinizer05> :-)
Jun 25 01:28:47 <Juest> And yes, i am aware.
Jun 25 01:40:54 <DocScrutinizer05> for now things to do: install syslog and get the logs of any crash and pastebin them. Test camera recording videos in all offered resolutions/modes, at least 30s each, check for crashes and again see syslog. Do a traffic dump with "tshark .. >dumpfile" and provide it per pastebin or on a server
Jun 25 01:41:36 <DocScrutinizer05> enable coredumps and provide any that may get produced by crashes
Jun 25 01:45:04 <DocScrutinizer05> please see "sp-rich-core - Rich core"  app
Jun 25 01:45:28 <DocScrutinizer05> apt-get install sp-rich-core
Jun 25 02:14:41 <Juest> gdb support?
**** ENDING LOGGING AT Sat Jun 25 02:59:58 2016