Audio/Video conversation

[kakaroto]

Hi,
so yes, it works!
When you do a call, aMSN will launch farsight, and it will wait for it to finish detecting all your codecs and your local candidates and start the pipeline, once it's done, it will make the call.. if it's not able to do so, then it will tell you that farsight needs to be installed.. so this means that it all went well, cool
now.. you should be able to hear sound from one side at least.. as explained before, WLM sends its internal ip, so if you're on two separate networks, you won't be able to send to WLM because you don't know his IP, but you should be able to receive from WLM since it knows your IP... if you're on the same network, then you should be able to send to WLM since you know it's internal ip, but WLM won't send to you because it only knows the external and not the internal ip... either way, one side should work...
it's not a good idea to keep winamp playing when testing because you might not hear the sound (you don't know at what volume you receive the sound)... easy way to test is putting the volume high and yelling/scratching the microphone on the other end  :p

[PjhN]

Hey. Should have been clearer about Winamp; I stopped playing for testing, only resuming playback after I'd ended the call, but it was THEN that sound quality was reduced. Closing aMSN immediately fixed it.

Can I run two versions of aMSN from the same install, at the same time? I tried, since I have two users I can log into MSN with, but when I do this they each tell me 'User does not support Audio Calls'. So how do I run two versions of aMSN on one PC, to test? Would a copy -> paste of the install be sufficient?

[kakaroto]

Hi,
yes, you can just launch as many aMSNs as you want and they will all work, the problem with 'user does not support audio calls' is as I explained before, you need to be logged in with MSNP15 to be able to 'receive' calls.. it's because you have a 'client id' which contains 'flags' of what your capabilities are (like, if you support winks or if you have a webcam, etc... in this case if you support audio calls).. in order to receive a call you need to be using MSNP15.. you can read more about MSNP15 here : http://www.amsn-project.net/forums/viewtopic.php?t=4666
to enable it, just do ctrl-shift-C from amsn's main window, in the window that pops up, type :

Code:

::config::setKey protocol 15

then reconnect... note that this is experimental and you will not be able to add/remove/rename/copy/move contacts or groups if you use MSNP15.. everything else should work just fine...

[H@t Trick]

Well I just did a little test, as I have mentioned before I run 4 msn accounts, 3 with default protocol and one with MSNP15,  I tried to start an audio call from one account to my MSNP15 account and initially I got "User does not support Audio Calls.", I added myself as a contact on each list, had to log out and change protocols...Kakaroto I think MSNP15 is mature enough for contact list management functionality now eh? ...anyways, once the contact management stuff was done, change back to P15, log in, send from P12 (aka 11 in aMSN) to P15, it rings, it connects, it disconnects but no sound, but not sure if this is normal.

I guess I will pull my defective laptop out of it's warranty return box (it goes back tomorrow) and if I can get it booted I will load WLM and try it.
I'll keep you posted, oh and this is on XP Pro SP2 btw.

[H@t Trick]

Ok now some WLM<<-->>aMSN P15 results, screenshots and logs
So I logged in from one account on my laptop with WLM 8.5 send the request to my P15 account, which tells me it receieved a voice call request that is not supported and a link to return the call, so I click the link to return the call, it rings on both computers, I accept on WLM, and WLM has no errors, says it connects successfully, but I get a pop up window with an error, I think from farsight (screenshot included), and there was a weird random CW opened in a  new tab the first time but not again, and not updated after that. Sound does not seem to be transfered though. For some reason my main msn account which I was not using crashed during this process, and I have included the screenshot form the error but obviously no logs
Here are the logs:

EDIT: I am using SVN r9756

WLM-->aMSN (with call back, is that normal?) Status log

Code:

[01:52:39] MSNSIP : Received SIP invite on 207.46.112.144
[01:52:39] MSNSIP : Creating SIP connection to 207.46.112.144
[01:52:39] MSNSIP : SIP connection created : ::MSNSIP::SIPConnection13
[01:52:39] SIP : Registering :
[01:52:40] SIP : Registered
[01:52:40] Going to Read : 1959
[01:52:40] MSNSIP : requestSIP : ::MSNSIP::SIPConnection13 f62b95252f264ea88482c6b081a91a20 INVITE
[01:52:40] Received unsupported SIP call from user@domain.com
[01:52:40] SIP : Answering Invite with status 480
[01:52:40] MSNSIP : Destroying ::MSNSIP::SIPConnection13
[01:52:40] SIP : Unregistering
[01:52:40] SIP : InviteRequestHandler called
[01:52:40] MSNSIP : requestSIP : ::MSNSIP::SIPConnection13 f62b95252f264ea88482c6b081a91a20 ACK
[01:52:40] Got Disconnected from SIP
[01:52:40] MSNSIP: Got an error
[01:52:40] MSNSIP : Destroying ::MSNSIP::SIPConnection13
[01:52:44] CallInviteUser user@domain.com
[01:52:44] User supports SIP
[01:52:44] MSNSIP : Inviting user user@domain.com to a SIP call
[01:52:44] MSNSIP : Creating SIP connection to vp.sip.messenger.msn.com
[01:52:44] MSNSIP : SIP connection created : ::MSNSIP::SIPConnection15
[01:52:44] Farsight : Preparing
[01:52:45] Farsight answering : LOCAL_CODEC: 8 PCMA 8000
[01:52:45] Farsight answering : LOCAL_CODEC: 0 PCMU 8000
[01:52:45] Farsight answering : LOCAL_CODEC: 96 SIREN 16000
[01:52:45] Farsight answering : LOCAL_CODECS_DONE
[01:52:45] Farsight answering : LOCAL_CANDIDATE: L0 1  UDP 0 X.X.X.X 7078
[01:52:45] Farsight answering : LOCAL_CANDIDATE: L0 2  UDP 0 X.X.X.X 7079
[01:52:45] Farsight answering : LOCAL_CANDIDATES_DONE
[01:52:45] Farsight : Farsight is now prepared!
[01:52:45] SIP : Registering :
[01:52:45] SIP invite sent
[01:52:45] SIP : Registered
[01:52:45] SIP : Sending Invite
[01:52:45] Received INVITE response
[01:52:45] MSNSIP : inviteSIPCB : ::MSNSIP::SIPConnection15 user@domain.com 788ed7475a536820c70f3e8c3260abaf TRYING
[01:52:47] Received INVITE response
[01:52:47] MSNSIP : inviteSIPCB : ::MSNSIP::SIPConnection15 user@domain.com 788ed7475a536820c70f3e8c3260abaf RINGING
[01:52:50] Got Disconnected from SIP
[01:52:54] Going to Read : 293
[01:52:54] Received INVITE response
[01:52:54] MSNSIP : inviteSIPCB : ::MSNSIP::SIPConnection15 user@domain.com 788ed7475a536820c70f3e8c3260abaf OK
[01:52:54] SIP callee accepted our call
[01:52:54] Farsight starting : {SIREN 111 16000} {PCMA 8 8000} {PCMU 0 8000} {telephone-event 101 8000} - {{} 1 {} UDP 1 X.X.X.X 34531} {{} 2 {} UDP 1 X.X.X.X 34532}
[01:53:05] SIP Keepalive
[01:53:25] SIP Keepalive
[01:53:43] Received INVITE response
[01:53:43] MSNSIP : inviteSIPCB : ::MSNSIP::SIPConnection15 user@domain.com 788ed7475a536820c70f3e8c3260abaf CLOSED REMOTE_BYE
[01:53:43] SIP callee closed the call
[01:53:43] MSNSIP : Destroying ::MSNSIP::SIPConnection15
[01:53:43] SIP : Unregistering
[01:53:52] Closed pipe :
(farsight.exe:2500): GLib-GObject-WARNING **: g_object_set_valist: object class `GstDshowAudioSrc' has no property named `@9\xb3'

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
[01:53:52] Got Disconnected from SIP
[01:53:52] MSNSIP: Got an error
[01:53:52] MSNSIP : Destroying ::MSNSIP::SIPConnection15
[01:53:53] Got Disconnected from SIP

WLM-->aMSN Protocol Log

Code:

[01:52:35] <-ns-sock8084 UBN user@domain.com 11 28
[01:52:35] Message Contents:
1 1 65541 134546710 54000000
[01:52:39] <-ns-sock8084 UBN user@domain.com 2 54
[01:52:39] Message Contents:
INVITE 207.46.112.144 by2msg2vp6.sip.messenger.msn.com
[01:52:39] -->SIP (207.46.112.144) REGISTER sip:rogers.com SIP/2.0

v: SIP/2.0/TLS 0.0.0.0:3476

Max-Forwards: 70

f: <sip:user2@domain2.com>;tag=9f2b865858;epid=300959dd11

t: <sip:user2@domain2.com>

i: 604f92ce8d0e21809f1c916a51e8a514

CSeq: 1 REGISTER

m: <sip:0.0.0.0:3476;transport=tls>;proxy=replace

User-Agent: aTSC/0.1

ms-keep-alive: UAC;hop-hop=yes

o: registration

Authorization: Basic <censored>

l: 0




[01:52:40] <--SIP (207.46.112.144) SIP/2.0 200 OK 207.46.112.144
Content-Length: 0
Via: SIP/2.0/TLS 0.0.0.0:3476;received=X.X.X.X;ms-received-port=3476;ms-received-cid=4bd3cf00
From: <sip:user2@domain2.com>;tag=9f2b865858;epid=300959dd11
To: <sip:user2@domain2.com>;tag=05E1D5C089ADD95B289C63C587E40731
Call-ID: 604f92ce8d0e21809f1c916a51e8a514
CSeq: 1 REGISTER
Expires: 600
ms-keep-alive: UAS; tcp=no; hop-hop=yes; end-end=no; timeout=20
Contact: <sip:X.X.X.X:3476;transport=tls;ms-received-cid=4BD3CF00>;Expires=600




[01:52:40] <--SIP (207.46.112.144) INVITE sip:X.X.X.X:3476;transport=tls;ms-received-cid=4BD3CF00 SIP/2.0
Record-Route: <sip:BY2MSG2132906.phx.gbl:443;transport=tls;lr;ms-route-sig=aa57eD4EYS5iNfHAxk2USviSx8v0EA>;tag=05E1D5C089ADD95B289C63C587E40731
Via: SIP/2.0/TLS 207.46.112.144:443;branch=z9hG4bKF5087241.C4B20558;branched=TRUE;ms-internal-info="bah3O6_vbcI99PXX2820DN2Ugxn-AA"
Max-Forwards: 69
Content-Length: 1959
Via: SIP/2.0/TLS 192.168.0.120:1210;received=207.46.112.236;ms-received-port=1210;ms-received-cid=4bd3c800
Contact: <sip:user@domain.com:1210;maddr=207.46.112.236;transport=tls;ms-received-cid=4BD3C800>
From: "0" <sip:user@domain.com;wl-type=1>;tag=3cee529b29;epid=61fddf42eb
To: <sip:user2@domain2.com>
Call-ID: f62b95252f264ea88482c6b081a91a20
CSeq: 1 INVITE
User-Agent: LCC/1.7
Ms-Conversation-ID: f=0
Content-Type: application/sdp



v=0

o=- 0 0 IN IP4 207.46.112.165

s=session

c=IN IP4 207.46.112.165

b=CT:100

t=0 0

m=audio 46257 RTP/AVP 114 111 112 115 116 4 8 0 97 101

a=candidate:hHKFfQITSOHjq28FED0o8PHt+jBru2ukbkI9qCpK5/g= 1 atWZFnu2G0uR1aFbGP4Pqw== UDP 0.850 192.168.0.120 12286

a=candidate:hHKFfQITSOHjq28FED0o8PHt+jBru2ukbkI9qCpK5/g= 2 atWZFnu2G0uR1aFbGP4Pqw== UDP 0.850 192.168.0.120 63162

a=candidate:C8j4kS35gZh/FPVB8a9nTt629jWxkKSlfBzxqyLHV7Q= 1 y/z6vFHwx9RISd2zyJBhtg== UDP 0.450 207.46.112.165 46257

a=candidate:C8j4kS35gZh/FPVB8a9nTt629jWxkKSlfBzxqyLHV7Q= 2 y/z6vFHwx9RISd2zyJBhtg== UDP 0.450 207.46.112.165 39527

a=candidate:GroupW/W+N6mOY/DwDhGao3852XV+d0VF6PTuz4bBRI= 1 jyV8XGw5QkZUIj8wG/sJlw== TCP 0.150 207.46.112.165 51010

a=candidate:GroupW/W+N6mOY/DwDhGao3852XV+d0VF6PTuz4bBRI= 2 jyV8XGw5QkZUIj8wG/sJlw== TCP 0.150 207.46.112.165 47377

a=candidate:irBxm+T/9rcpfUZVKzhHy9RaxSJucB2xZ7/UUqboxMs= 1 TjUrKHh8bG4zUoK3sGZ1tg== UDP 0.550 X.X.X.X 37332

a=candidate:irBxm+T/9rcpfUZVKzhHy9RaxSJucB2xZ7/UUqboxMs= 2 TjUrKHh8bG4zUoK3sGZ1tg== UDP 0.550 X.X.X.X 43450

a=candidate:iSGBkh15vY5E9+Ss3VrMJuYr2+bAfsg3U6J4QD4nzQE= 1 8WgFezIRwVyybTd1xBNrZg== TCP 0.250 X.X.X.X 1212

a=candidate:iSGBkh15vY5E9+Ss3VrMJuYr2+bAfsg3U6J4QD4nzQE= 2 8WgFezIRwVyybTd1xBNrZg== TCP 0.250 X.X.X.X 1213

a=candidate:EpaHfy/Q9XQmWUvMXnJtv2JPGbGiR9zcR3tI1Yw4vYY= 1 v6DKM4qaRsbsbY0E8kfNNg== UDP 0.670 X.X.X.X 12014

a=candidate:EpaHfy/Q9XQmWUvMXnJtv2JPGbGiR9zcR3tI1Yw4vYY= 2 v6DKM4qaRsbsbY0E8kfNNg== UDP 0.670 X.X.X.X 12015

a=rtcp:39527

a=rtpmap:114 x-msrta/16000

a=fmtp:114 bitrate=12000

a=rtpmap:111 SIREN/16000

a=fmtp:111 bitrate=16000

a=rtpmap:112 G7221/16000

a=fmtp:112 bitrate=24000

a=rtpmap:115 x-msrta/8000

a=fmtp:115 bitrate=12000

a=rtpmap:116 AAL2-G726-32/8000

a=rtpmap:4 G723/8000

a=rtpmap:8 PCMA/8000

a=rtpmap:0 PCMU/8000

a=rtpmap:97 RED/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=encryption:rejected


[01:52:40] -->SIP (207.46.112.144) SIP/2.0 100 Trying

v: SIP/2.0/TLS 207.46.112.144:443;branch=z9hG4bKF5087241.C4B20558;branched=TRUE;ms-internal-info="bah3O6_vbcI99PXX2820DN2Ugxn-AA"

v: SIP/2.0/TLS 192.168.0.120:1210;received=207.46.112.236;ms-received-port=1210;ms-received-cid=4bd3c800

Max-Forwards: 70

f: "0" <sip:user@domain.com;wl-type=1>;tag=3cee529b29;epid=61fddf42eb

t: <sip:user2@domain2.com>

i: f62b95252f264ea88482c6b081a91a20

CSeq: 1 INVITE

User-Agent: aTSC/0.1

l: 0




[01:52:40] -->SIP (207.46.112.144) SIP/2.0 480 Temporarily Unavailable

v: SIP/2.0/TLS 207.46.112.144:443;branch=z9hG4bKF5087241.C4B20558;branched=TRUE;ms-internal-info="bah3O6_vbcI99PXX2820DN2Ugxn-AA"

v: SIP/2.0/TLS 192.168.0.120:1210;received=207.46.112.236;ms-received-port=1210;ms-received-cid=4bd3c800

Record-Route: <sip:BY2MSG2132906.phx.gbl:443;transport=tls;lr;ms-route-sig=aa57eD4EYS5iNfHAxk2USviSx8v0EA>;tag=05E1D5C089ADD95B289C63C587E40731

Max-Forwards: 70

f: "0" <sip:user@domain.com;wl-type=1>;tag=3cee529b29;epid=61fddf42eb

t: "0" <sip:user2@domain2.com>;tag=3b27177e7f

i: f62b95252f264ea88482c6b081a91a20

CSeq: 1 INVITE

User-Agent: aTSC/0.1

l: 0




[01:52:40] -->SIP (207.46.112.144) REGISTER sip:rogers.com SIP/2.0

v: SIP/2.0/TLS 192.168.0.108:3476

Max-Forwards: 70

f: <sip:user2@domain2.com>;tag=e1d8a4bddf;epid=9f5dc552e7

t: <sip:user0@domain2.com>

i: afacfbeb37c93356e820ef595982751f

CSeq: 2 REGISTER

m: <sip:192.168.0.108:3476;transport=tls>;proxy=replace

User-Agent: aTSC/0.1

ms-keep-alive: UAC;hop-hop=yes

Expires: 0

Authorization: Basic  <censored>

l: 0




[01:52:40] <--SIP (207.46.112.144) ACK sip:X.X.X.X:3476;transport=tls;ms-received-cid=4BD3CF00 SIP/2.0
Via: SIP/2.0/TLS 207.46.112.144:443;branch=z9hG4bKF5087241.C4B20558;branched=FALSE
Max-Forwards: 70
CSeq: 1 ACK
Call-ID: f62b95252f264ea88482c6b081a91a20
To: "0" <sip:user2@domain2.com>;tag=3b27177e7f
From: "0" <sip:user@domain.com;wl-type=1>;tag=3cee529b29;epid=61fddf42eb
Content-Length: 0




[01:52:40] <--SIP (207.46.112.144) SIP/2.0 200 OK
Content-Length: 0
Via: SIP/2.0/TLS 192.168.0.108:3476;received=X.X.X.X;ms-received-port=3476;ms-received-cid=4bd3cf00
From: <sip:user2@domain2.com>;tag=e1d8a4bddf;epid=9f5dc552e7
To: <sip:user2@domain2.com>;tag=05E1D5C089ADD95B289C63C587E40731
Call-ID: afacfbeb37c93356e820ef595982751f
CSeq: 2 REGISTER




[01:52:45] -->SIP (vp.sip.messenger.msn.com) REGISTER sip:rogers.com SIP/2.0

v: SIP/2.0/TLS 0.0.0.0:3477

Max-Forwards: 70

f: <sip:user2@domain2.com>;tag=503373efd4;epid=0bbb02f53a

t: <sip:user2@domain2.com>

i: e1fc008319ec87b63301cfb520ce8e41

CSeq: 1 REGISTER

m: <sip:0.0.0.0:3477;transport=tls>;proxy=replace

User-Agent: aTSC/0.1

ms-keep-alive: UAC;hop-hop=yes

o: registration

Authorization: Basic  <censored>


l: 0




[01:52:45] <--SIP (vp.sip.messenger.msn.com) SIP/2.0 200 OK 207.46.112.142
Content-Length: 0
Via: SIP/2.0/TLS 0.0.0.0:3477;received=207.46.112.242;ms-received-port=3477;ms-received-cid=41082800
From: <sip:user2@domain2.com>;tag=503373efd4;epid=0bbb02f53a
To: <sip:user2@domain2.com>;tag=B7081A6C0685B5FE82B8C756046DA4A6
Call-ID: e1fc008319ec87b63301cfb520ce8e41
CSeq: 1 REGISTER
Expires: 600
ms-keep-alive: UAS; tcp=no; hop-hop=yes; end-end=no; timeout=20
Contact: <sip:207.46.112.242:3477;transport=tls;ms-received-cid=41082800>;Expires=600




[01:52:45] -->SIP (vp.sip.messenger.msn.com) INVITE sip:user@domain.com SIP/2.0

v: SIP/2.0/TLS 0.0.0.0:3477

Max-Forwards: 70

f: "0" <sip:user2@domain2.com>;tag=33bc484715;epid=207c4ff8ab

t: <sip:user@domain.com>

i: 788ed7475a536820c70f3e8c3260abaf

CSeq: 1 INVITE

m: "0" <sip:user2@domain2.com:3477;maddr=0.0.0.0;transport=tls>;proxy=replace

User-Agent: aTSC/0.1

Ms-Conversation-ID: f=0

c: application/sdp

l: 245



v=0
o=- 0 0 IN IP4 X.X.X.X

s=session

c=IN IP4 X.X.X.X

b=CT:100

t=0 0

m=audio 7078 RTP/AVP 96 8 0

a=rtcp:7079

a=rtpmap:96 SIREN/16000

a=fmtp:96 bitrate=16000

a=rtpmap:8 PCMA/8000

a=rtpmap:0 PCMU/8000

a=encryption:rejected


[01:52:45] <--SIP (vp.sip.messenger.msn.com) SIP/2.0 100 Trying
Via: SIP/2.0/TLS 0.0.0.0:3477;received=207.46.112.242;ms-received-port=3477;ms-received-cid=41082800
From: "0" <sip:user2@domain2.com>;tag=33bc484715;epid=207c4ff8ab
To: <sip:user@domain.com>
Call-ID: 788ed7475a536820c70f3e8c3260abaf
CSeq: 1 INVITE
Content-Length: 0




[01:52:47] <--SIP (vp.sip.messenger.msn.com) SIP/2.0 180 Ringing
v: SIP/2.0/TLS 0.0.0.0:3477;received=207.46.112.242;ms-received-port=3477;ms-received-cid=41082800
l: 0
From: "0" <sip:user2@domain2.com;wl-type=1>;tag=33bc484715;epid=207c4ff8ab
To: "0" <sip:user@domain.com>;tag=3afea4582a
Call-ID: 788ed7475a536820c70f3e8c3260abaf
CSeq: 1 INVITE
User-Agent: LCC/1.7




[01:52:54] <--SIP (vp.sip.messenger.msn.com) SIP/2.0 200 OK
v: SIP/2.0/TLS 0.0.0.0:3477;received=207.46.112.242;ms-received-port=3477;ms-received-cid=41082800
l: 293
Contact: <sip:user@domain.com:1214;maddr=X.X.X.X;transport=tls;ms-received-cid=41082B00>
From: "0" <sip:user2@domain2.com;wl-type=1>;tag=33bc484715;epid=207c4ff8ab
To: "0" <sip:user@domain.com>;tag=3afea4582a
Call-ID: 788ed7475a536820c70f3e8c3260abaf
CSeq: 1 INVITE
Record-Route: <sip:BY2MSG2132904.phx.gbl:444;transport=tls;lr;ms-route-sig=dafymVG_Rt_R7afW_0o9znhQ_vhVz_>
User-Agent: LCC/1.7
Content-Type: application/sdp



v=0

o=- 0 0 IN IP4 X.X.X.X

s=session

c=IN IP4 X.X.X.X

b=CT:100

t=0 0

m=audio 34531 RTP/AVP 111 8 0 101

a=rtpmap:111 SIREN/16000

a=fmtp:111 bitrate=16000

a=rtpmap:8 PCMA/8000

a=rtpmap:0 PCMU/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=encryption:rejected


[01:52:54] -->SIP (vp.sip.messenger.msn.com) ACK sip:user@domain.com SIP/2.0

v: SIP/2.0/TLS 192.168.0.108:3477

Max-Forwards: 70

f: "0" <sip:user2@domain2.com;wl-type=1>;tag=33bc484715;epid=207c4ff8ab

t: "0" <sip:user@domain.com>;tag=3afea4582a

i: 788ed7475a536820c70f3e8c3260abaf

CSeq: 1 ACK

User-Agent: aTSC/0.1

l: 0




[01:52:58] <-::MSN::SB23-sock8348 BYE user@domain.com
[01:53:14] ->ns-sock8084 PNG


[01:53:14] <-ns-sock8084 QNG 40
[01:53:43] <--SIP (vp.sip.messenger.msn.com) BYE sip:207.46.112.242:3477;transport=tls;ms-received-cid=41082800 SIP/2.0
Via: SIP/2.0/TLS 207.46.112.142:444;branch=z9hG4bKF4786E55.D5A3C060;branched=TRUE;ms-internal-info="daDIVpQOV0v1ANHqe63pn2c_7nkbkA"
Max-Forwards: 69
Content-Length: 0
Via: SIP/2.0/TLS 192.168.0.120:1214;received=X.X.X.X;ms-received-port=1214;ms-received-cid=41082b00
From: "0" <sip:user@domain.com;wl-type=1>;tag=3afea4582a
To: "0" <sip:user2@domain2.com;wl-type=1>;tag=33bc484715;epid=207c4ff8ab
Call-ID: 788ed7475a536820c70f3e8c3260abaf
CSeq: 1 BYE
User-Agent: LCC/1.7




[01:53:43] -->SIP (vp.sip.messenger.msn.com) SIP/2.0 200 OK

v: SIP/2.0/TLS 207.46.112.142:444;branch=z9hG4bKF4786E55.D5A3C060;branched=TRUE;ms-internal-info="daDIVpQOV0v1ANHqe63pn2c_7nkbkA"

v: SIP/2.0/TLS 192.168.0.120:1214;received=X.X.X.X;ms-received-port=1214;ms-received-cid=41082b00

Max-Forwards: 70

f: "0" <sip:user2@domain2.com;wl-type=1>;tag=33bc484715;epid=207c4ff8ab

t: "0" <sip:user@domain.com>;tag=3afea4582a

i: 788ed7475a536820c70f3e8c3260abaf

CSeq: 1 BYE

User-Agent: aTSC/0.1

l: 0




[01:53:43] -->SIP (vp.sip.messenger.msn.com) REGISTER sip:rogers.com SIP/2.0

v: SIP/2.0/TLS 192.168.0.108:3477

Max-Forwards: 70

f: <sip:user2@domain2.com>;tag=8d7bc006a9;epid=b6103aeeb7

t: <sip:user2@domain2.com>

i: fa0fba26e438ef3a2f6ce83a1b7ed477

CSeq: 2 REGISTER

m: <sip:192.168.0.108:3477;transport=tls>;proxy=replace

User-Agent: aTSC/0.1

ms-keep-alive: UAC;hop-hop=yes

Expires: 0

Authorization: Basic  <censored>

l: 0




[01:53:52] <--SIP (vp.sip.messenger.msn.com) SIP/2.0 200 OK
Content-Length: 0
Via: SIP/2.0/TLS 192.168.0.108:3477;received=207.46.112.242;ms-received-port=3477;ms-received-cid=41082800
From: <sip:user2@domain2.com>;tag=8d7bc006a9;epid=b6103aeeb7
To: <sip:user2@domain2.com>;tag=B7081A6C0685B5FE82B8C756046DA4A6
Call-ID: fa0fba26e438ef3a2f6ce83a1b7ed477
CSeq: 2 REGISTER




[01:54:14] ->ns-sock8084 PNG


[01:54:14] <-ns-sock8084 QNG 46
[01:55:14] ->ns-sock8084 PNG


[01:55:14] <-ns-sock8084 QNG 47
[01:56:14] ->ns-sock8084 PNG


[01:56:14] <-ns-sock8084 QNG 49

Screenshots:

Farsight error:


Random CW tab opened:


Error on crash of main account:


I am not sure if this helps but My Event log has 3 Identical entries for farsight.exe:
Event Type:   Error
Event Source:   Application Hang
Event Category:   (101)
Event ID:   1002
Date:      4/22/08
Time:      1:11:34 AM
User:      N/A
Computer:   DANIEL2
Description:
Hanging application farsight.exe, version 0.0.0.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74   Applicat
0008: 69 6f 6e 20 48 61 6e 67   ion Hang
0010: 20 20 66 61 72 73 69 67     farsig
0018: 68 74 2e 65 78 65 20 30   ht.exe 0
0020: 2e 30 2e 30 2e 30 20 69   .0.0.0 i
0028: 6e 20 68 75 6e 67 61 70   n hungap
0030: 70 20 30 2e 30 2e 30 2e   p 0.0.0.
0038: 30 20 61 74 20 6f 66 66   0 at off
0040: 73 65 74 20 30 30 30 30   set 0000
0048: 30 30 30 30               0000    

And the wish.exe crash:
Event Type:   Error
Event Source:   Application Error
Event Category:   None
Event ID:   1000
Date:      4/22/08
Time:      1:43:36 AM
User:      N/A
Computer:   DANIEL2
Description:
Faulting application wish.exe, version 8.4.2.14, faulting module ntdll.dll, version 5.1.2600.2180, fault address 0x00001230.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74   Applicat
0008: 69 6f 6e 20 46 61 69 6c   ion Fail
0010: 75 72 65 20 20 77 69 73   ure  wis
0018: 68 2e 65 78 65 20 38 2e   h.exe 8.
0020: 34 2e 32 2e 31 34 20 69   4.2.14 i
0028: 6e 20 6e 74 64 6c 6c 2e   n ntdll.
0030: 64 6c 6c 20 35 2e 31 2e   dll 5.1.
0038: 32 36 30 30 2e 32 31 38   2600.218
0040: 30 20 61 74 20 6f 66 66   0 at off
0048: 73 65 74 20 30 30 30 30   set 0000
0050: 31 32 33 30 0d 0a         1230..  


I hope I have not provided useless irrelevant information, but I have tried to be as thorough as I can be. I hope it helps. Did I do something wrong when I installed farsight? I just updated my SVN as normal with TortoiseSVN using the context menu for SVN update in explorer. I had an idea of what could be wrong as I was typing this but I just forgot it, so any ideas?

<off-topic> Yes I know this was a long post but I wanted to wish you a congratulations (or as we say in Hebrew Mazal Tov!) on passing your last and final exam and on becoming an Engineer kakaroto!! And we all really appreciate the work you and the rest of the dev team put into this project!</off-topic>

EDIT: Cleaned logs of personal info, external IP =X.X.X.X, Internal IP's modified, p15 account=user2@domain2.com, and P12 (default P11) account=user@domain.com

[kakaroto]

Hi,
ok, first, you forgot to clean the Authorization: Basic ...... that contains your password... :p ok, not your 'password' but your ticket token that can be used to connect to the SIP server and make calls (it's a password, but with something like 24h or 48h expiration).
anyways, the wish.exe crash is probably totally unrelated (especially if you say it's another account).
the farsight 'crash' is not actually a crash.. it should just exit but windows (or glib) is stupid... I do a g_error() which should assert() and make amsn realize that farsight quit and that's it, you get the error in status log.. but the assert seems to trigger windows to consider it a crash.. have it show you an error box and add a crash report to the event viewer...
the most important thing is the error message you screenshoted.. stupid thing... also a windows compatibility issue.. when sending a UDP packet to somewhere it's not listening on, we get an ICMP response telling us it's unreachable, which triggers that 'error'.. I should just make the utility ignore that error instead of saying "humm. I got an unknown error, ok, I'll just cancel everything".

[MastaG]

Ive installed the following things with ./configure --prefix=/usr, make, make install
1.  gstreamer-0.10.19/
2.  gst-plugins-base-0.10.19/          
3.  gst-plugins-good-0.10.7/
4.  gst-plugins-bad-0.10.6/              
5.  gst-python-0.10.11/
6.  farsight2/ (git pulled at 22-04-2008)
7.  gst-plugins-farsight-0.12.7/ (link from the wiki)
No problems at all with the above.
Now I configure amsn with:
**************************************************************************************************
[mastag@amd3000 amsn]$ ./configure --prefix=/usr --with-tcl=/usr/local/lib --with-tk=/usr/local/lib
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking tcl build dir... using tcl library in /usr/local/lib
checking tk build dir... using tk library in /usr/local/lib
checking for main in -lstdc++... yes
checking how to run the C preprocessor... gcc -E
checking for X... libraries , headers
checking for gethostbyname... yes
checking for connect... yes
checking for remove... yes
checking for shmat... yes
checking for IceConnectionNumber in -lICE... yes
checking for png_read_info in -lpng... yes
checking png.h usability... yes
checking png.h presence... yes
checking for png.h... yes
checking for jpeg_CreateDecompress in -ljpeg... yes
checking jpeglib.h usability... yes
checking jpeglib.h presence... yes
checking for jpeglib.h... yes
checking jerror.h usability... yes
checking jerror.h presence... yes
checking for jerror.h... yes
checking for ftello... yes
checking for fseeko... yes
checking for getpt... yes
checking for strcasestr... yes
checking for memmem... yes
checking for dlopen... no
checking for pthread_create in -lpthread... yes
checking if mmx should be used... yes
checking for pkg-config... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for GLIB... yes
checking for GST... yes
checking for FARSIGHT2... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating utils/linux/capture/config.h
config.status: utils/linux/capture/config.h is unchanged

compile time options summary
============================

    X11          : yes
    Tcl          : 8.5
    TK           : 8.5
    DEBUG        : no
    STATIC       : no
    FARSIGHT     : yes

[mastag@amd3000 amsn]$
**************************************************************************************************
And then make:
**************************************************************************************************
[mastag@amd3000 amsn]$ make
  CXX     utils/TkCximage/src/TkCximage.cpp.o
  CXX     utils/TkCximage/src/PhotoFormat.cpp.o
  CXX     utils/TkCximage/src/procs.cpp.o
  CXX     utils/TkCximage/src/CxImage/ximadsp.cpp.o
  CXX     utils/TkCximage/src/CxImage/ximaexif.cpp.o
  CXX     utils/TkCximage/src/CxImage/ximagif.cpp.o
  CXX     utils/TkCximage/src/CxImage/ximainfo.cpp.o
  CXX     utils/TkCximage/src/CxImage/ximajpg.cpp.o
  CXX     utils/TkCximage/src/CxImage/ximalyr.cpp.o
  CXX     utils/TkCximage/src/CxImage/ximapng.cpp.o
  CXX     utils/TkCximage/src/CxImage/ximatga.cpp.o
  CXX     utils/TkCximage/src/CxImage/ximatran.cpp.o
  CXX     utils/TkCximage/src/CxImage/ximabmp.cpp.o
  CXX     utils/TkCximage/src/CxImage/ximaenc.cpp.o
  CXX     utils/TkCximage/src/CxImage/ximage.cpp.o
  CXX     utils/TkCximage/src/CxImage/ximahist.cpp.o
  CXX     utils/TkCximage/src/CxImage/ximaint.cpp.o
  CXX     utils/TkCximage/src/CxImage/ximalpha.cpp.o
  CXX     utils/TkCximage/src/CxImage/ximapal.cpp.o
  CXX     utils/TkCximage/src/CxImage/ximasel.cpp.o
  CXX     utils/TkCximage/src/CxImage/ximath.cpp.o
  CXX     utils/TkCximage/src/CxImage/xmemfile.cpp.o
  AR      utils/TkCximage/src/CxImage/libCxImage.a
ar: creating utils/TkCximage/src/CxImage/libCxImage.a
  LDX     utils/TkCximage/src/TkCximage.cpp.so
  LDX     utils/TkCximage/src/TkCximage.cpp.so
cp utils/TkCximage/src/TkCximage.cpp.so utils/TkCximage/TkCximage.so
  CC      utils/webcamsn/src/webcamsn.o
  CC      utils/webcamsn/src/kidhash.o
  CC      utils/webcamsn/src/bitstring.o
  CC      utils/webcamsn/src/deblock.o
  CC      utils/webcamsn/src/encode.o
  CC      utils/webcamsn/src/idct_dequant.o
  CC      utils/webcamsn/src/mimic.o
  CC      utils/webcamsn/src/vlc_decode.o
  CC      utils/webcamsn/src/colorspace.o
  CC      utils/webcamsn/src/decode.o
  CC      utils/webcamsn/src/fdct_quant.o
  CC      utils/webcamsn/src/vlc_common.o
  CC      utils/webcamsn/src/vlc_encode.o
  AR      utils/webcamsn/src/libmimic.a
ar: creating utils/webcamsn/src/libmimic.a
  LD      utils/webcamsn/src/webcamsn.so
cp utils/webcamsn/src/webcamsn.so utils/webcamsn/webcamsn.so
  CC      utils/tcl_siren/src/tcl_siren.o
  CC      utils/tcl_siren/src/common.o
  CC      utils/tcl_siren/src/dct4.o
  CC      utils/tcl_siren/src/encoder.o
  CC      utils/tcl_siren/src/decoder.o
  CC      utils/tcl_siren/src/huffman.o
  CC      utils/tcl_siren/src/rmlt.o
  AR      utils/tcl_siren/src/libsiren.a
ar: creating utils/tcl_siren/src/libsiren.a
  LD      utils/tcl_siren/src/tcl_siren.so
cp utils/tcl_siren/src/tcl_siren.so utils/tcl_siren/tcl_siren.so
  CC      utils/tclISF/src/tclISF.o
  CC      utils/tclISF/src/libISF/compression.o
  CC      utils/tclISF/src/libISF/createTags.o
  CC      utils/tclISF/src/libISF/decodeTags.o
  CC      utils/tclISF/src/libISF/decompression.o
  CC      utils/tclISF/src/libISF/decProperty.o
  CC      utils/tclISF/src/libISF/encoding.o
  CC      utils/tclISF/src/libISF/libISF.o
  CC      utils/tclISF/src/libISF/read.o
  AR      utils/tclISF/src/libISF/libISF.a
ar: creating utils/tclISF/src/libISF/libISF.a
  LD      utils/tclISF/src/tclISF.so
  LD      utils/tclISF/src/tclISF.so
cp utils/tclISF/src/tclISF.so utils/tclISF/tclISF.so
  CC      utils/farsight/farsight.o
utils/farsight/farsight.c: In function ‘_new_local_candidate’:
utils/farsight/farsight.c:19: fout: ‘FsCandidate’ has no member named ‘candidate_id’
utils/farsight/farsight.c:19: fout: ‘FsCandidate’ has no member named ‘candidate_id’
utils/farsight/farsight.c: In function ‘stdin_io_cb’:
utils/farsight/farsight.c:125: fout: ‘FsCandidate’ has no member named ‘candidate_id’
make: *** [utils/farsight/farsight.o] Fout 1
**************************************************************************************************
Whats wrong?

[H@t Trick]

Hi,
ok, first, you forgot to clean the Authorization: Basic ...... that contains your password... :p ok, not your 'password' but your ticket token that can be used to connect to the SIP server and make calls (it's a password, but with something like 24h or 48h expiration).
anyways, the wish.exe crash is probably totally unrelated (especially if you say it's another account).
the farsight 'crash' is not actually a crash.. it should just exit but windows (or glib) is stupid... I do a g_error() which should assert() and make amsn realize that farsight quit and that's it, you get the error in status log.. but the assert seems to trigger windows to consider it a crash.. have it show you an error box and add a crash report to the event viewer...
the most important thing is the error message you screenshoted.. stupid thing... also a windows compatibility issue.. when sending a UDP packet to somewhere it's not listening on, we get an ICMP response telling us it's unreachable, which triggers that 'error'.. I should just make the utility ignore that error instead of saying "humm. I got an unknown error, ok, I'll just cancel everything".

Lol well I didn't know what the authorization stuff was plus I thought it might be relevant. Plus I am not sure what exactly is the authorization info in the logs.
So basically all is working as it should on Windows, based on how it is coded right now? Should I get sound or not on Windows?
Should I wait for some updates before I try testing again?

[kakaroto]

@MastaG : the issue is this :  
6. farsight2/ (git pulled at 22-04-2008)
as is said in the wiki :

 8 - farsight2 - 0.0.2 (for big endian systems, there is a bug fixed in git, but you'll have to wait until the API gets stable)

so.. the git version has an incompatible API, which means that it will not work (and will not even compile).. you should just go get the 0.0.2 version and install that...
the current git is moving a lot, once the API gets more stable and stops changing, we'll release 0.0.3 and I'll update farsight to use the new API.

@H@t Trick : ok, latest revision now fixes this bug.. it was a bug in gstreamer's udpsrc. I sent the patch to gstreamer upstream and updated the binary, you shouldn't get that error anymore, and hopefully it will work now.

[H@t Trick]

Well I can finally give you some testing results on XP. While testing I went to plug my mic in and cause a reboot of my system (I think there is a loose standoff under the mobo that when jostled shorts/grounds something), this happened twice and SeaMonkey decided it didnt want to to read my profile files, lost access to over 2GBs of emails too, and the normal process I have done in the past to restore my profile manually (it used to happen on a crash every few months but not in over a year) failed. I have finally rebuilt my profile as best as I could, got my emails back so thats good. Anyways enough off topic rambling.
Well theres good news and bad news. Kakaroto's fix works for the error I had. So aMSN to aMSN (both p15) on two pc's only works 1 way it seems, not sure what is happening. IT connects no problem no matter which pc initiates the request. When I initiate from my desktop to my laptop I can send sound from my laptop through the mic to the desktop, but not from the desktop to the laptop using either the mic or routing wav output from WMP (yeah I know more stupid Voleware but I don't have any other music files other than the samples so VLC and MPC weren't options) using the Creative driver app. When I initiate the call from my laptop to my desktop no sound either way. When I log in using WLM 8.5 on my laptop, and connect, sound works bi-directionally no problems and my mic input from my laptop is outputted on the desktop louder than aMSN to aMSN when I get one way sound working. I also had some gstreamer/farsight error windows come up after prolonged SIP sessions, I didnt get a chance to take screenshots, but I think I have a status log with the error, can I PM you with that log Kakaroto instead of posting and editing out all the personal info, man that was pain.

I hope this info helps, do you want logs of my sessions so you can see why I get the behaviour I am getting with the sound?
Anyways it works perfectly with WLM so thats good.

[kakaroto]

Hello,
Finally, H@t Trick was able to test :p I also tried it with Tjikkun today, he managed to build rpms for fedora core (should be ready soon for public download).
anyways, I don't care about your rambling, so let's skip to your second paragraph :p
so if I summarize :
1 - amsn -> amsn (1 way...)
2 - desktop <- laptop
3 - laptop >< desktop
4 - WLM8.5 on laptop <--> desktop

ok... so, first case, you say it works 1 way whoever initiates the call.. but you don't say who can hear who? the caller of the callee ?
second case, you don't specify what is used on each pc.. is it amsn to amsn ? in that case, case 2 = case 1, but you just specified that the caller can hear the callee, but callee can't hear the caller.
third case, same as above, you don't specify the client.. if it's amsn to amsn, then it contradicts case 1 where you said it connects no matter who is calling... if it's wlm, then it contracts case 4 where you specify the client (as if other cases were not using WLM8.5)
fourth case works... with the desktop as the callee.

ok, so my analysis with the so bad explanation you just gave is that you're doing this from the same network with one pc having some problems accessing the stun server...
as I said before, amsn to amsn will only work if you're on separate networks, and wlm to amsn will only work one way (wlm user hears nothing), unless you're on the networks in which case it also works one way but the other way (amsn user hears nothing). and that's all because of the external vs. internal ip problem.

1 - one amsn timed out on the stun server and falled back on using its internal ip. the other sent his external ip.. so it worked one way only
2 - same here
3 - the stun request didn't time out and they both sent their external ips so they couldn't connect to each other
4 - the stun request in amsn timed out again and amsn sent his internal ip, while WLM always sends his internal IP, so it worked both ways.


you can PM me the logs for each session if you have them, if you only have the log with the crash, then PM me only the status log for that one.. but I think that the crash error won't show up in the status log (not sure but it seems that it gets eaten by the error box).

can you just confirm whether your 4 cases happen 100% of the time or not (stun timeout would make the results change from time to time), and if you understand the issue, look at the status logs for remote and local candidates, they should contain the remote and local ips you have, if it's internal/external, it will help you know what's happening...
then I'll be waiting for a more detailed report explaining which client to which client (amsn protocol version is useless info in this case because it works the same, it's just a matter of being able to receive a request or not) and what the outcome is.. a useful thing would be for example : case X happened 3/10 of the tests.... and of course, before reporting a case, make sure it's reproducable so I can judge if it's a possible stun timeout or a consistent bug...
if you could get whether the internal or external ip was used in each case (for amsn only, since WLM always uses internal ip), that would certainly help too (status log, line like "Farsight answered : LOCAL_CANDIDATE: ..... ip here ....")

[H@t Trick]

Hi,
Sorry for not being so clear, I was stressed from my SeaMonkey profile issues, sorry about the rambling
Anyways quick summary:

- Both PCs on my internal network.
- Making a successful connection happens each attempt in all situations.

PC1=Desktop with aMSN P15
PC2=Laptop with aMSN P15
WLM=Laptop with WLM8.5

Cases:
1) PC1 calls PC2, PC1 hears PC2, but PC2 does not hear PC1
2) PC2 calls PC1, no sound either direction
3) PC1 calls WLM, bi-directional sound
4) WLM calls PC1, which causes aMSN to do a call back, bi-directional sound.
Case 4=Case3

I just reconfirmed all cases quickly but I am just on my way out and will re-test these cases and get the status logs for all of them and do 10 tests for each, do you want the log files to show all 10 tests?

i.e. 6 or 8 log files (depending on if case 4 is considered different from case 3) containing 10 tests each?
Hopefully you respond before I get back so i get you the right log files as I wont have use of my laptop after tonight for a few days.

I hope I have clarified my results for you.

[kakaroto]

hummm... thanks for the clarified answer!
well, if you can reproduce the cases on each attempt, then only one log for one test per case would be enough, and yes, case3=case4 so no need for that log...
and only status log would be enough so no need for the protocol log (has too much data and all the important bits are outputted in status log anyways).

I'm guessing PC1 for some reason doesn't get the external ip.. no idea why! or... hummm... ok, maybe an idea :
you have forwarded the UDP port 7078 to the desktop... so when you PC1 calls PC2, it listens on 7078 (always), gives external IP and port 7078 since it's forwarded, STUN says the external port is 7078 too... PC2 sends to external IP and port 7078 which gets to PC1 (so PC1 hears PC2), but the opposite doesn't work....
on the second case, I have no idea why it doesn't work :p
third case would be the same reason case 1 works... I see no reason why the case 1 and 2 would give different results...
the logs will help me know what ips are getting sent... but important, please give me also any routing information you have (port forwarding, etc...) from your router.

thx

edit
here's from your log above :

[01:52:45] Farsight answering : LOCAL_CANDIDATE: L0 1  UDP 0 X.X.X.X 7078
[01:52:45] Farsight answering : LOCAL_CANDIDATE: L0 2  UDP 0 X.X.X.X 7079

you removed the ip.. so I'm guessing it's the external ip... but you see the port is 7078 (+1 for rtcp).. so I guess I was right (7078 is the internal port used), your router is doing it, it maps the ports 1 to 1... or maybe you have the port forwarding or DMZ or something.. anyways, the port would be random otherwise...

[H@t Trick]

You're welcome!
As I was reading your reply I was thinking it was my forwardings and DMZ settings and then you were thinking the same thing. Yes the X.X.X.X is my external IP and PC1 is in the DMZ, so thats my problem eh? My desktop is on the DMZ because using my webcam on aMSN kept giving me a solid grey image and no one saw the picture, enabling the DMZ solved this. I guess I could just forward to correct ports for for the webcam. I will get you the logs as soon as I can, hopefully this afternoon, thats if I can get approved to leave work early lol. Now I am going to have to search the forums for those port numbers lol, but how do i ensure those forwardings don't affect my brother on WLM on his pc's?

[kakaroto]

hehe, I knew it!!! :p
ok, so I guess case 1 is because you're in DMZ so the router lets the data through, case 2 might be because PC2 requests port 7078 internally for himself, so the port 7078 is not 'DMZ' anymore... so in that case, noone receives anything... it all makes sense :p
no more need for the logs now since we figured it out...
about port forwarding, it's just the ports specified in the 'connection' tab of preferences (+ a few more for multiple FT/webcam)... that should do it...
you don't need to forward any port for the audio conf, it will use STUN and do firewall punching, so it will work without having to configure anything... I don't even know if it will cause problems if you forward ports or not...