Audio/Video conversation

[Quetzal]

I can see SIREN output, but call don't really work (unfortunatly), i had not test before my last post but now, testing, I find an error in the debug log:

[22:47:06] <--SIP (207.46.112.32) SIP/2.0 400 Bad Ticket policy=PPM_?id=69264;lifetime=86400
Content-Length: 0
Via: SIP/2.0/TLS 192.168.10.1:51989;received=XXX.XXX.XXX.XXX;ms-received-port=51989;ms-received-cid=91d2b00
From: <sip:MYMSNADDRESS@HOTMAIL.COM>;tag=E548FC17DC;epid=8C7303F8D4
To: <sip:MYMSNADRESS@HOTMAIL.COM>;tag=865EE25B31BD0062DD8886823B82CC58
Call-ID: 1609ECB4E053A71FF19D294397C5BBDE
CSeq: 1 REGISTER

I've tried both msnp12 and 15.
Is it normal that "To:" indicate my msn adress and not the adress of the person that I call ?
With msnp 15, I can't see when my contact send me an invitation (and I can see the invitation with msnp12)

[kakaroto]

@trv, it failed to find farsight because it installed it in /usr/local/lib instead of /usr/lib ... this error is in the 'FAQ' of the wiki/Farsight.. read that :p
@Quetzal : it's normal that it sends your email in the 'To'.. it's because you REGISTER first.. then in the INVITE, it will put the email of your contact...
I don't know why it says bad token..  could you PM me the REGISTER message in full ? (the one that you send).. thanks
also.. svn update and you'll get some more status log messages for debug..

p.s.: I have build gstreamer, gst-plugins-base and now building gst plugins good and bad... for gutsy!

[trv]

@trv, it failed to find farsight because it installed it in /usr/local/lib instead of /usr/lib ... this error is in the 'FAQ' of the wiki/Farsight.. read that :p

nop, thats not the case, i have had manually installed it in /usr/lib the files are there.. the error is there too !

anyway, the ppa repository files worked excelent, and i compiled / made deb of amsn, and now i am running it, and ready to test it

[kakaroto]

cool!! paste me the output of ./utils/farsight/farsight 1 2 (you can remove your ip from there)

[trv]

hmmmm thats not very good

LOCAL_CODEC: 96 AMR-WB 16000
LOCAL_CODEC: 97 AMR 8000
LOCAL_CODEC: 3 GSM 8000
LOCAL_CODEC: 98 MPA 90000
LOCAL_CODEC: 8 PCMA 8000
LOCAL_CODEC: 0 PCMU 8000
LOCAL_CODEC: 99 SIREN 16000
LOCAL_CODECS_DONE
**
** ERROR:(utils/farsight/farsight.c:370):main: assertion failed: (gst_element_set_state (pipeline, GST_STATE_PLAYING) != GST_STATE_CHANGE_FAILURE)
Aborted (core dumped)

[kakaroto]

humm... ok, it finds SIREN codec which is good.. but it doesn't change the state.. I wonder why!
do you think you can join on #amsn IRC channel on irc.freenode.net ? or send me by PM your ip with an ssh account so I can debug this..
thanks!

[trv]

the previous error was because of alsa misconfiguration (thx kakaroto), now all is fine!

the correct output is:

LOCAL_CODEC: 96 AMR-WB 16000
LOCAL_CODEC: 97 AMR 8000
LOCAL_CODEC: 3 GSM 8000
LOCAL_CODEC: 98 MPA 90000
LOCAL_CODEC: 8 PCMA 8000
LOCAL_CODEC: 0 PCMU 8000
LOCAL_CODEC: 99 SIREN 16000
LOCAL_CODECS_DONE
LOCAL_CANDIDATE: L0 2  UDP 0 123.456.789.100 7079
LOCAL_CANDIDATE: L0 1  UDP 0 123.456.789.100 7078
LOCAL_CANDIDATES_DONE

[kakaroto]

Hi all,
for all you ubuntu gutsy users.. you can now go grab the debs that I build from here : http://people.collabora.co.uk/~kakaroto/gutsy-debs/
you should install them all with :

Code:

sudo dpkg -i *.deb

then try configuring amsn again... it should detect farsight2 and compile farsight.. you can then try the audio call...

some users (kr0n1x and trv... the only ones able to compile all that so far) reported that aMSN freezes when trying to make a call.. and they weren't able to make a call.. hopefully, i'll soon find out why this happens and fix it.. for me, it all works correctly (with the debs I provided).


EDIT : The gst-plugins-farsight-siren.tar.gz is there only for those who would want the source, but it is already compiled and provided in one of the debs.. the reason I put the source for that package is because it's a modified version from the latest release (contains siren encoder/decoder/payloader/depayloader)... so you don't need to download/extract that file! just to make things clear..
Good luck.. I can't wait to hear the results of your experiments!

EDIT 2 : ok I found what the problem was for trv and the others would have their aMSN freezing and the call not working!!!! it's because of tcl/tk 8.5!! the tls extension is weird in 8.5 so if you use tcl/tk 8.4 it works! that's why I wasn't able to reproduce

EDIT 3 : more good news.. I fixed the bug with an ugly hack (but that should work just fine)  to workaround the bug in tcltls... now, starting revision 9736.. the freezing/not working/ bugs you have should not happen anymore!
@Quetzal, your registration/authentification error you posted before should also be fixed in the latest SVN version. others have reported the same problem (it only worked for me! lol) but I fixed it by modifying the authentication string, just try it again now!

[flomar34]

Thanks, i hope i could test it this evening

So all i have to do now (i'm a bit long to understand sometimes )

1) update amsn to revision 9736

2) uninstall gstreamer and plugins from gustsy

3) install your debs

4) compil fasight2 with then option -prefix=/usr

5) Enjoy it

Am i right ?

[kakaroto]

no... 1-2-3 are right.. but the 4th no.. you don't need to compile farsight2, it's already compiled and available in those .deb files ... everything you need is there... apart from amsn...
so :
1) update amsn to latest svn
2) install all the .deb files in that link (the old ones will get removed automatically by the newer version)
3) cd amsn && ./configure && make
4) enjoy

[Quetzal]

@Quetzal, your registration/authentification error you posted before should also be fixed in the latest SVN version. others have reported the same problem (it only worked for me! lol) but I fixed it by modifying the authentication string, just try it again now!

I look fixed but I can't test now (not in my home, and nobody connected in my contactlist)
You are too fast for me !! (you have fix the bug before I can send you the debug log ^^)

[kakaroto]

lol.. sorry about that :p it just said bad ticket, and a pure coincidence yesterday I was reverse engineering some more for the ICE stuff and I realized that the username/password it sends are not your real username and password.. it's actually :
username : "msmsgs"
password : "PRT_" + the password...
don't ask me why.. but for me it worked with username password.. then with kr1n0x he had the bad ticket problem and I thought I might try the 'msmsgs' username instead.. tried it, worked for me, worked for him.. so that's it! hehe
anyways..
a bit more news... in the latest SVN version, I just committed some code that uses STUN over TCP/TLS to authenticate to the relay server (TURN) with a shared secret request/response algorithm.. and it works, so I get a username/password/ip to use for an Allocate request/response on the TURN server (over udp this time). This will allow people who can't connect between them because of a firewall and a network topography too complex for STUN to work (right now STUN is enough to pass through most firewalls, but maybe not huge corporate setups with NAT inside NAT inside NAT and proxies and stuff)... so with this (kind of like the reflector for the webcam where you can do webcam even if both are firewalled), we should be able to work around those kind of network topographies!
Note though that this is not in use yet, it is just a preliminary work for later when we will have ICE introduced... once ICE works, *then* we'll use this piece of code to make aMSN use the TURN server...
Don't expect this code to be used until maybe 2 weeks from now.

[kr0n1x]

tonight... 3.30 AM in italy...i heard kakaroto's sexy voice  :oops:  

congratz man

edit: i'm in my home now, i downgraded tcl/tk to 8.4 and tried a call with a WLM user (she has Windows XP). It works too

[trv]

i don't know if its a sideeffect of the tcltls bug that was fixed last night, but i can't login anymore with msnp15, only 11. using 15 it just hangs/freezes at the login, for ever!

edit: hmm ok now it connected with 15, don't know why it froze before..

edit2: i must say i'm experiencing sever 'freezes for ever' but i cannto identify when this happens, it seems to be random.

One thing i noticed is that when it stucks like that, the cpu is 100% becaulse of farsight2 executable running with some localhost arguments.. I kill amsn and must kill farsight too, and then launch amsn again.

this is a ps output

trv       2646 89.8  0.6  83832  6772 ?        Rl   01:31 881:00 ./utils/farsight/farsight user@localhost remote@remotehost

Now i was able to log in with msnp15, after a minute or more frozen (probably because of 100% cpu usage by farsight, tcl is slower.....)

[kakaroto]

hummm... trv, you have the latest SVN ?
vivia just downloaded my .deb files, installed, compiled amsn and ran it and we had a voice call, no problems...
I did notice the 100% cpu for farsight, but it only happened when we had the freezes in amsn with the bug in tls...
I'm wondering if you did update amsn...
anyways, when you say 'random freezes'.. is it when you do a voice call or just when chatting normally ?
afaik, none of my changes should affect anything outside the voice call feature...