[sip-comm] Lag and connecting to windows machines


#1

First of all: Thanks Emil, for all your quick help! The sip-com is now
running like a charm (atleast most of the time).

But (again) two questions remains.

There is quite a lot of lag in the audio (running over a 10 mbit LAN on more
then 1 GHz computers). Do you know where this is introduced, through
buffering, encoding or because of overhead caused by Java? Do you believe
this to be fixable?

When trying to connect to a windows (2003 and XP) machine the call is always
rejected because the user is not known on that machine. I've tried the login
name, the computername and the displayname (set in sip-com.properties).
Calling out to a linux machine is not a problem. What am I missing? Or what
did I forget to try? The address I'm using is name@[ipv6 address].

Regards

Mikael Formanek

ยทยทยท

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: users-help@sip-communicator.dev.java.net


#2

Hello Michael,

First of all: Thanks Emil, for all your quick help! The sip-com is now
running like a charm (atleast most of the time).

U r welcome!

There is quite a lot of lag in the audio (running over a 10 mbit LAN on more
then 1 GHz computers). Do you know where this is introduced, through
buffering, encoding or because of overhead caused by Java? Do you believe
this to be fixable?

Well ... performanche has been an issue with JMF for quite a while. My experience is that you get satisfactory performance on Windows machines because of the directsound plugin. Lag in that case is (I think) about or less than 200 ms. With Linux the problem comes from the fact that there is no native sound plugin such as directsound and the only option is javasound hence the lag. We are planning on developing a JMF plugin that interacts with ALSA but I have no idea when this would happen (could be a while). Then u have J2SE 1.5 Tiger which is supposed to greatly improbe performance (haven't tried it yet). This could also help improve lag.

When trying to connect to a windows (2003 and XP) machine the call is always
rejected because the user is not known on that machine. I've tried the login
name, the computername and the displayname (set in sip-com.properties).
Calling out to a linux machine is not a problem. What am I missing? Or what
did I forget to try? The address I'm using is name@[ipv6 address].

Whatch out for the case (upper and lower case matters). The user name is the one specified against the public address property in the configuration file or (if none has been given) ur OS user name... this problem is actually beginning to annoy me. Think I'll add a property to cancel that behavior or at least ask the user to decide.

Cheers
Emil