[sip-comm-dev] GSoC coding is now officially open


#1

Hey all,

A quick note to remind everyone concerned (or interested) that the GSoC
coding period is officially open. Good luck to all the students and mentors!

Students, now is probably a good time for all of you to check out your
project requirement lists (http://sip-communicator.org/gsoc) and make
sure that your plans are inline with them. Remember that they represent
the work that's important to the project and not getting carried away
with "cool stuff" is an essential thing to learn.

I'll soon create trunk branches for all of you so that you can commit
your work on java.net. That's probably going to take a couple of weeks
so that gives you enough time to prepare something to commit.

Again, good luck to everyone and looking forward to seeing and playing
with your contributions!

Cheers
Emil

···

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


#2

Hello

I upgraded recently from build 1661 to build 1896

I noticed that know its no longer possible to have more than one call
simultaneously (SIP).

When i place a second call, the first one goes automaticaly "on Hold".

When i place a third call, the second one goes automaticaly "on Hold",
and so on.

And usually after three calls simultaneous, one on them falls by it
self.

In previous builds this was not happening.

How can i reverse this feature, and keep simultaneous calls ?

thanks

···

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


#3

Hey Carlos,

Carlos Alexandre wrote:

Hello

I upgraded recently from build 1661 to build 1896

I noticed that know its no longer possible to have more than one call
simultaneously (SIP).

When i place a second call, the first one goes automaticaly "on Hold".

When i place a third call, the second one goes automaticaly "on Hold",
and so on.

And usually after three calls simultaneous, one on them falls by it
self.

In previous builds this was not happening.

How can i reverse this feature, and keep simultaneous calls ?

Afraid you can't. At least not without changing the code. Putting the
first call on hold is intentional. We thought that having two calls in
parallel where you hear both your interlocutors but they don't hear each
other would be a scenario that would probably confuse a many users.

We therefore decided to disable it until we implement proper conferences.

As for the failing calls, this doesn't sound normal. Could you please
log an issue describing the problem and how to reproduce it?

Thanks
Emil

···

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


#4

Well, believe it or not, that was one of the features that we were using
the most, and it was the perfect feature for our use of SC....

I think ill have a look at the code to reverse this.

About the falling calls, when u say "to log na issue", u mean send it
here?

Thanks for your work.

Carlos

From: Emil Ivov [mailto:emil@sip-communicator.org] On Behalf Of Emil

Ivov

···

-----Original Message-----
Sent: quarta-feira, 27 de Maio de 2009 17:03
To: dev@sip-communicator.dev.java.net
Subject: Re: [sip-comm-dev] placing simultaneous calls

Hey Carlos,

Carlos Alexandre wrote:

Hello

I upgraded recently from build 1661 to build 1896

I noticed that know its no longer possible to have more than one call
simultaneously (SIP).

When i place a second call, the first one goes automaticaly "on Hold".

When i place a third call, the second one goes automaticaly "on Hold",
and so on.

And usually after three calls simultaneous, one on them falls by it
self.

In previous builds this was not happening.

How can i reverse this feature, and keep simultaneous calls ?

Afraid you can't. At least not without changing the code. Putting the
first call on hold is intentional. We thought that having two calls in
parallel where you hear both your interlocutors but they don't hear each
other would be a scenario that would probably confuse a many users.

We therefore decided to disable it until we implement proper
conferences.

As for the failing calls, this doesn't sound normal. Could you please
log an issue describing the problem and how to reproduce it?

Thanks
Emil

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

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


#5

Hey Carlos,

Carlos Alexandre wrote:

Well, believe it or not, that was one of the features that we were using
the most, and it was the perfect feature for our use of SC....

I think ill have a look at the code to reverse this.

Hm ... didn't realize this. Maybe we should think about making the
behaviour configuratble then.

About the falling calls, when u say "to log na issue", u mean send it
here?

Nah. I mean opening an issue on our issue tracker:

https://sip-communicator.dev.java.net/issues/enter_bug.cgi

Check this out if you need more details on working with issues:

http://www.sip-communicator.org/index.php/Development/BugsAndIssues

Cheers
Emil

···

Thanks for your work.

Carlos

-----Original Message-----
From: Emil Ivov [mailto:emil@sip-communicator.org] On Behalf Of Emil
Ivov
Sent: quarta-feira, 27 de Maio de 2009 17:03
To: dev@sip-communicator.dev.java.net
Subject: Re: [sip-comm-dev] placing simultaneous calls

Hey Carlos,

Carlos Alexandre wrote:

Hello

I upgraded recently from build 1661 to build 1896

I noticed that know its no longer possible to have more than one call
simultaneously (SIP).

When i place a second call, the first one goes automaticaly "on Hold".

When i place a third call, the second one goes automaticaly "on Hold",
and so on.

And usually after three calls simultaneous, one on them falls by it
self.

In previous builds this was not happening.

How can i reverse this feature, and keep simultaneous calls ?

Afraid you can't. At least not without changing the code. Putting the
first call on hold is intentional. We thought that having two calls in
parallel where you hear both your interlocutors but they don't hear each
other would be a scenario that would probably confuse a many users.

We therefore decided to disable it until we implement proper
conferences.

As for the failing calls, this doesn't sound normal. Could you please
log an issue describing the problem and how to reproduce it?

Thanks
Emil

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

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

--
Emil Ivov, Ph.D. 30a rue de la Patrie
Project Lead 67300 Schiltigheim
SIP Communicator
emcho@sip-communicator.org FAX: +33.1.77.62.47.31
http://sip-communicator.org PHONE: +33.1.77.62.43.30

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


#6

Hi Carlos,

For starters, look at .impl.protocol.SingleCallInProgressPolicy which
takes care of putting existing calls on hold when a new one is
established. It's created in
impl.protocol.ProtocolProviderActivator#start(BundleContext) so I
guess it should be enough to comment out its instantiation there.

Regards,
Lubo

···

2009/5/28 Carlos Alexandre <Carlos.Alexandre@nav.pt>:

Well, believe it or not, that was one of the features that we were using
the most, and it was the perfect feature for our use of SC....

I think ill have a look at the code to reverse this.

About the falling calls, when u say "to log na issue", u mean send it
here?

Thanks for your work.

Carlos

-----Original Message-----
From: Emil Ivov [mailto:emil@sip-communicator.org] On Behalf Of Emil
Ivov
Sent: quarta-feira, 27 de Maio de 2009 17:03
To: dev@sip-communicator.dev.java.net
Subject: Re: [sip-comm-dev] placing simultaneous calls

Hey Carlos,

Carlos Alexandre wrote:

Hello

I upgraded recently from build 1661 to build 1896

I noticed that know its no longer possible to have more than one call
simultaneously (SIP).

When i place a second call, the first one goes automaticaly "on Hold".

When i place a third call, the second one goes automaticaly "on Hold",
and so on.

And usually after three calls simultaneous, one on them falls by it
self.

In previous builds this was not happening.

How can i reverse this feature, and keep simultaneous calls ?

Afraid you can't. At least not without changing the code. Putting the
first call on hold is intentional. We thought that having two calls in
parallel where you hear both your interlocutors but they don't hear each
other would be a scenario that would probably confuse a many users.

We therefore decided to disable it until we implement proper
conferences.

As for the failing calls, this doesn't sound normal. Could you please
log an issue describing the problem and how to reproduce it?

Thanks
Emil

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

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

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


#7

Hello everyone!

We are using a slightly modified version of sip communicator without GUI for a big project. I am facing a problem that a call will successfully be established but if the caller hangs up callee doesn't recognize that the call was terminated. This causes inconsistencies in our system.
My next thought was to test this with two original versions of sip communicator (build 1896), and the problems did not occur.

So I tested my program in the following environment:

- WIN XP
- java version "1.6.0_11"
- Java Hotspot(TM) Client VM (build 10.0-b16, mixed mode, sharing)

B: Sip Communicator (build 1896) using eclipse
- WIN XP
- java version "1.6.0_07"
- Java Hotspot(TM) Client VM (build 10.0-b23, mixed mode, sharing)

Server: 3CX Phone System v6.1.0 run on WIN XP

My tests showed that
- if A calls B and A hangs up, B gets the CallParticipantChangeEvent and terminates the call correctly, but
- if B calls A and B hangs up, A does not get the CallParticipantChangeEvent and therefore doesn't hang up

I used whireshark and found out, that in the second case the BYE request from B is not forwarded to A by the server. That is why the CallParticipantChangeEvent won't be fired and A is not able to terminate the call correctly. Does anyone know why the server does not forward the BYE request? I also found out that the BYE Requests differ slightly between A and B
(The BYE Packet of B is missing the following: "Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REGISTER,SUBSCRIBE,NOTIFY,REFER,INFO" - could that be the problem?)

I attached the flow of both cases as well as the dump of both BYE packets.

Thanks for your help!

Best wishes, Nico

A-B_BYE_Working.zip (105 KB)

B-A_BYE_notWorking.zip (134 KB)

···

A: modified version of Sip Communicator (based on build 1896)

____________________________________________________
Nicolaus Klinger
Biomedical Engineering
Smart Biomedical Systems

ARC - Austrian Research Centers
Viktor Kaplan Straße 2
2700 Wr. Neustadt
mail: nicolaus.klinger@arcs.ac.at


#8

About the falling calls:
I found out that after being on hold for 30 seconds, the calls
disconnect.

I suppose this is a feature....

Carlos

From: Emil Ivov [mailto:emil@sip-communicator.org] On Behalf Of Emil

Ivov

···

-----Original Message-----
Sent: quinta-feira, 28 de Maio de 2009 12:24
To: dev@sip-communicator.dev.java.net
Subject: Re: [sip-comm-dev] placing simultaneous calls

Hey Carlos,

Carlos Alexandre wrote:

Well, believe it or not, that was one of the features that we were

using

the most, and it was the perfect feature for our use of SC....

I think ill have a look at the code to reverse this.

Hm ... didn't realize this. Maybe we should think about making the
behaviour configuratble then.

About the falling calls, when u say "to log na issue", u mean send it
here?

Nah. I mean opening an issue on our issue tracker:

https://sip-communicator.dev.java.net/issues/enter_bug.cgi

Check this out if you need more details on working with issues:

http://www.sip-communicator.org/index.php/Development/BugsAndIssues

Cheers
Emil

Thanks for your work.

Carlos

-----Original Message-----
From: Emil Ivov [mailto:emil@sip-communicator.org] On Behalf Of Emil
Ivov
Sent: quarta-feira, 27 de Maio de 2009 17:03
To: dev@sip-communicator.dev.java.net
Subject: Re: [sip-comm-dev] placing simultaneous calls

Hey Carlos,

Carlos Alexandre wrote:

Hello

I upgraded recently from build 1661 to build 1896

I noticed that know its no longer possible to have more than one call
simultaneously (SIP).

When i place a second call, the first one goes automaticaly "on

Hold".

When i place a third call, the second one goes automaticaly "on

Hold",

and so on.

And usually after three calls simultaneous, one on them falls by it
self.

In previous builds this was not happening.

How can i reverse this feature, and keep simultaneous calls ?

Afraid you can't. At least not without changing the code. Putting the
first call on hold is intentional. We thought that having two calls in
parallel where you hear both your interlocutors but they don't hear

each

other would be a scenario that would probably confuse a many users.

We therefore decided to disable it until we implement proper
conferences.

As for the failing calls, this doesn't sound normal. Could you please
log an issue describing the problem and how to reproduce it?

Thanks
Emil

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

dev-help@sip-communicator.dev.java.net

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

dev-help@sip-communicator.dev.java.net

--
Emil Ivov, Ph.D. 30a rue de la Patrie
Project Lead 67300 Schiltigheim
SIP Communicator
emcho@sip-communicator.org FAX: +33.1.77.62.47.31
http://sip-communicator.org PHONE: +33.1.77.62.43.30

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

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


#9

Carlos,

Carlos Alexandre wrote:

About the falling calls:
I found out that after being on hold for 30 seconds, the calls
disconnect.

I suppose this is a feature....

Definitely not. Could you please send logs and wireshark dumps here? If
this is not a server issue then we need to log it in the tracker.

Incidentally, could you please open an issue for 2.0 on making the
automatic on-hold behaviour configurable? We'd still need to do some
research on how users expect this to work but we'd better log it so that
we don't forget to ask around.

Cheers
Emil

···

Carlos

-----Original Message-----
From: Emil Ivov [mailto:emil@sip-communicator.org] On Behalf Of Emil
Ivov
Sent: quinta-feira, 28 de Maio de 2009 12:24
To: dev@sip-communicator.dev.java.net
Subject: Re: [sip-comm-dev] placing simultaneous calls

Hey Carlos,

Carlos Alexandre wrote:

Well, believe it or not, that was one of the features that we were

using

the most, and it was the perfect feature for our use of SC....

I think ill have a look at the code to reverse this.

Hm ... didn't realize this. Maybe we should think about making the
behaviour configuratble then.

About the falling calls, when u say "to log na issue", u mean send it
here?

Nah. I mean opening an issue on our issue tracker:

https://sip-communicator.dev.java.net/issues/enter_bug.cgi

Check this out if you need more details on working with issues:

http://www.sip-communicator.org/index.php/Development/BugsAndIssues

Cheers
Emil

Thanks for your work.

Carlos

-----Original Message-----
From: Emil Ivov [mailto:emil@sip-communicator.org] On Behalf Of Emil
Ivov
Sent: quarta-feira, 27 de Maio de 2009 17:03
To: dev@sip-communicator.dev.java.net
Subject: Re: [sip-comm-dev] placing simultaneous calls

Hey Carlos,

Carlos Alexandre wrote:

Hello

I upgraded recently from build 1661 to build 1896

I noticed that know its no longer possible to have more than one call
simultaneously (SIP).

When i place a second call, the first one goes automaticaly "on

Hold".

When i place a third call, the second one goes automaticaly "on

Hold",

and so on.

And usually after three calls simultaneous, one on them falls by it
self.

In previous builds this was not happening.

How can i reverse this feature, and keep simultaneous calls ?

Afraid you can't. At least not without changing the code. Putting the
first call on hold is intentional. We thought that having two calls in
parallel where you hear both your interlocutors but they don't hear

each

other would be a scenario that would probably confuse a many users.

We therefore decided to disable it until we implement proper
conferences.

As for the failing calls, this doesn't sound normal. Could you please
log an issue describing the problem and how to reproduce it?

Thanks
Emil

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

dev-help@sip-communicator.dev.java.net

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

dev-help@sip-communicator.dev.java.net

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
SIP Communicator
emcho@sip-communicator.org FAX: +33.1.77.62.47.31
http://sip-communicator.org PHONE: +33.1.77.62.43.30

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


#10

Emil:
This is what is happening:

1 - A call is established between asterisk SIP Server and SipCommunicator.
2 - The call is put on Hold on Sip Communicator
3 - From this moment on, Asterisk stops sending RTCP packets to SC.
4 - After 30 seconds without receiving packets from asterisk, SC sends na RTCP goodBye packet to Asterisk and disconnects the call with a "failed" message.
5 - Asterisk doesnt know how to handle with RTCP goodbye packet, and on its side the call continues on hold, though SC hás hung up.

Im sending you the whireshark dump....

200.200.200.249 is SC
200.200.200.10 is Asterisk

You can see that after being put on hold on second 53, only SC sends RTCP packets, and that at second 82 it sends a Goodbye.

Is there a way i can put the RTCP timeout on SC side to "infinity"? There is nothing i can do on Asterisk.....

thanks

Carlos

call_onhold.pcap (885 KB)

···

-----Original Message-----

From: Emil Ivov [mailto:emcho@sip-communicator.org]

Sent: sábado, 13 de Junho de 2009 13:13
To: dev@sip-communicator.dev.java.net
Subject: Re: [sip-comm-dev] placing simultaneous calls

Carlos,

Carlos Alexandre wrote:

About the falling calls:
I found out that after being on hold for 30 seconds, the calls
disconnect.

I suppose this is a feature....

Definitely not. Could you please send logs and wireshark dumps here? If
this is not a server issue then we need to log it in the tracker.

Incidentally, could you please open an issue for 2.0 on making the
automatic on-hold behaviour configurable? We'd still need to do some
research on how users expect this to work but we'd better log it so that
we don't forget to ask around.

Cheers
Emil

Carlos

-----Original Message-----
From: Emil Ivov [mailto:emil@sip-communicator.org] On Behalf Of Emil
Ivov
Sent: quinta-feira, 28 de Maio de 2009 12:24
To: dev@sip-communicator.dev.java.net
Subject: Re: [sip-comm-dev] placing simultaneous calls

Hey Carlos,

Carlos Alexandre wrote:

Well, believe it or not, that was one of the features that we were

using

the most, and it was the perfect feature for our use of SC....

I think ill have a look at the code to reverse this.

Hm ... didn't realize this. Maybe we should think about making the
behaviour configuratble then.

About the falling calls, when u say "to log na issue", u mean send it
here?

Nah. I mean opening an issue on our issue tracker:

https://sip-communicator.dev.java.net/issues/enter_bug.cgi

Check this out if you need more details on working with issues:

http://www.sip-communicator.org/index.php/Development/BugsAndIssues

Cheers
Emil

Thanks for your work.

Carlos

-----Original Message-----
From: Emil Ivov [mailto:emil@sip-communicator.org] On Behalf Of Emil
Ivov
Sent: quarta-feira, 27 de Maio de 2009 17:03
To: dev@sip-communicator.dev.java.net
Subject: Re: [sip-comm-dev] placing simultaneous calls

Hey Carlos,

Carlos Alexandre wrote:

Hello

I upgraded recently from build 1661 to build 1896

I noticed that know its no longer possible to have more than one call
simultaneously (SIP).

When i place a second call, the first one goes automaticaly "on

Hold".

When i place a third call, the second one goes automaticaly "on

Hold",

and so on.

And usually after three calls simultaneous, one on them falls by it
self.

In previous builds this was not happening.

How can i reverse this feature, and keep simultaneous calls ?

Afraid you can't. At least not without changing the code. Putting the
first call on hold is intentional. We thought that having two calls in
parallel where you hear both your interlocutors but they don't hear

each

other would be a scenario that would probably confuse a many users.

We therefore decided to disable it until we implement proper
conferences.

As for the failing calls, this doesn't sound normal. Could you please
log an issue describing the problem and how to reproduce it?

Thanks
Emil

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

dev-help@sip-communicator.dev.java.net

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

dev-help@sip-communicator.dev.java.net

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
SIP Communicator
emcho@sip-communicator.org FAX: +33.1.77.62.47.31
http://sip-communicator.org PHONE: +33.1.77.62.43.30

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


#11

Hi emil,
i opened the issue

thanks

···

-----Original Message-----

From: Emil Ivov [mailto:emcho@sip-communicator.org]

Sent: sábado, 13 de Junho de 2009 13:13
To: dev@sip-communicator.dev.java.net
Subject: Re: [sip-comm-dev] placing simultaneous calls

Carlos,

Carlos Alexandre wrote:

About the falling calls:
I found out that after being on hold for 30 seconds, the calls
disconnect.

I suppose this is a feature....

Definitely not. Could you please send logs and wireshark dumps here? If
this is not a server issue then we need to log it in the tracker.

Incidentally, could you please open an issue for 2.0 on making the
automatic on-hold behaviour configurable? We'd still need to do some
research on how users expect this to work but we'd better log it so that
we don't forget to ask around.

Cheers
Emil

Carlos

-----Original Message-----
From: Emil Ivov [mailto:emil@sip-communicator.org] On Behalf Of Emil
Ivov
Sent: quinta-feira, 28 de Maio de 2009 12:24
To: dev@sip-communicator.dev.java.net
Subject: Re: [sip-comm-dev] placing simultaneous calls

Hey Carlos,

Carlos Alexandre wrote:

Well, believe it or not, that was one of the features that we were

using

the most, and it was the perfect feature for our use of SC....

I think ill have a look at the code to reverse this.

Hm ... didn't realize this. Maybe we should think about making the
behaviour configuratble then.

About the falling calls, when u say "to log na issue", u mean send it
here?

Nah. I mean opening an issue on our issue tracker:

https://sip-communicator.dev.java.net/issues/enter_bug.cgi

Check this out if you need more details on working with issues:

http://www.sip-communicator.org/index.php/Development/BugsAndIssues

Cheers
Emil

Thanks for your work.

Carlos

-----Original Message-----
From: Emil Ivov [mailto:emil@sip-communicator.org] On Behalf Of Emil
Ivov
Sent: quarta-feira, 27 de Maio de 2009 17:03
To: dev@sip-communicator.dev.java.net
Subject: Re: [sip-comm-dev] placing simultaneous calls

Hey Carlos,

Carlos Alexandre wrote:

Hello

I upgraded recently from build 1661 to build 1896

I noticed that know its no longer possible to have more than one call
simultaneously (SIP).

When i place a second call, the first one goes automaticaly "on

Hold".

When i place a third call, the second one goes automaticaly "on

Hold",

and so on.

And usually after three calls simultaneous, one on them falls by it
self.

In previous builds this was not happening.

How can i reverse this feature, and keep simultaneous calls ?

Afraid you can't. At least not without changing the code. Putting the
first call on hold is intentional. We thought that having two calls in
parallel where you hear both your interlocutors but they don't hear

each

other would be a scenario that would probably confuse a many users.

We therefore decided to disable it until we implement proper
conferences.

As for the failing calls, this doesn't sound normal. Could you please
log an issue describing the problem and how to reproduce it?

Thanks
Emil

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

dev-help@sip-communicator.dev.java.net

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

dev-help@sip-communicator.dev.java.net

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
SIP Communicator
emcho@sip-communicator.org FAX: +33.1.77.62.47.31
http://sip-communicator.org PHONE: +33.1.77.62.43.30

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

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


#12

Thanks for the report Carlos! Definitely very helpful!

There's no doubt that this is an SC issue so could you please create an
issue for this as well and paste your description and attachments in there?

Thanks
Emil

Carlos Alexandre wrote:

···

Emil:
This is what is happening:

1 - A call is established between asterisk SIP Server and SipCommunicator.
2 - The call is put on Hold on Sip Communicator
3 - From this moment on, Asterisk stops sending RTCP packets to SC.
4 - After 30 seconds without receiving packets from asterisk, SC sends na RTCP goodBye packet to Asterisk and disconnects the call with a "failed" message.
5 - Asterisk doesnt know how to handle with RTCP goodbye packet, and on its side the call continues on hold, though SC hás hung up.

Im sending you the whireshark dump....

200.200.200.249 is SC
200.200.200.10 is Asterisk

You can see that after being put on hold on second 53, only SC sends RTCP packets, and that at second 82 it sends a Goodbye.

Is there a way i can put the RTCP timeout on SC side to "infinity"? There is nothing i can do on Asterisk.....

thanks

Carlos

-----Original Message-----
From: Emil Ivov [mailto:emcho@sip-communicator.org]
Sent: sábado, 13 de Junho de 2009 13:13
To: dev@sip-communicator.dev.java.net
Subject: Re: [sip-comm-dev] placing simultaneous calls

Carlos,

Carlos Alexandre wrote:

About the falling calls:
I found out that after being on hold for 30 seconds, the calls
disconnect.

I suppose this is a feature....

Definitely not. Could you please send logs and wireshark dumps here? If
this is not a server issue then we need to log it in the tracker.

Incidentally, could you please open an issue for 2.0 on making the
automatic on-hold behaviour configurable? We'd still need to do some
research on how users expect this to work but we'd better log it so that
we don't forget to ask around.

Cheers
Emil

Carlos

-----Original Message-----
From: Emil Ivov [mailto:emil@sip-communicator.org] On Behalf Of Emil
Ivov
Sent: quinta-feira, 28 de Maio de 2009 12:24
To: dev@sip-communicator.dev.java.net
Subject: Re: [sip-comm-dev] placing simultaneous calls

Hey Carlos,

Carlos Alexandre wrote:

Well, believe it or not, that was one of the features that we were

using

the most, and it was the perfect feature for our use of SC....

I think ill have a look at the code to reverse this.

Hm ... didn't realize this. Maybe we should think about making the
behaviour configuratble then.

About the falling calls, when u say "to log na issue", u mean send it
here?

Nah. I mean opening an issue on our issue tracker:

https://sip-communicator.dev.java.net/issues/enter_bug.cgi

Check this out if you need more details on working with issues:

http://www.sip-communicator.org/index.php/Development/BugsAndIssues

Cheers
Emil

Thanks for your work.

Carlos

-----Original Message-----
From: Emil Ivov [mailto:emil@sip-communicator.org] On Behalf Of Emil
Ivov
Sent: quarta-feira, 27 de Maio de 2009 17:03
To: dev@sip-communicator.dev.java.net
Subject: Re: [sip-comm-dev] placing simultaneous calls

Hey Carlos,

Carlos Alexandre wrote:

Hello

I upgraded recently from build 1661 to build 1896

I noticed that know its no longer possible to have more than one call
simultaneously (SIP).

When i place a second call, the first one goes automaticaly "on

Hold".

When i place a third call, the second one goes automaticaly "on

Hold",

and so on.

And usually after three calls simultaneous, one on them falls by it
self.

In previous builds this was not happening.

How can i reverse this feature, and keep simultaneous calls ?

Afraid you can't. At least not without changing the code. Putting the
first call on hold is intentional. We thought that having two calls in
parallel where you hear both your interlocutors but they don't hear

each

other would be a scenario that would probably confuse a many users.

We therefore decided to disable it until we implement proper
conferences.

As for the failing calls, this doesn't sound normal. Could you please
log an issue describing the problem and how to reproduce it?

Thanks
Emil

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

dev-help@sip-communicator.dev.java.net

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

dev-help@sip-communicator.dev.java.net

------------------------------------------------------------------------

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

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
SIP Communicator
emcho@sip-communicator.org FAX: +33.1.77.62.47.31
http://sip-communicator.org PHONE: +33.1.77.62.43.30

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


#13

Hi guys

I placed Issue 684 - making the automatic on-hold behaviour configurable a while ago, (https://sip-communicator.dev.java.net/issues/show_bug.cgi?id=684) and I saw

ubomirs followup "r5683 allows the feature to be disabled through the configuration property SingleCallInProgressPolicy#PNAME_SINGLE_CALL_IN_PROGRESS_POLICY_ENABLED, no GUI is

provided."

The SIP part of this issue is working perfectly, but there is still a pronlem with the RTP packets:

When I place a second call, the outgoing RTP packets flow of the first call stop. And even if I hang up the second call, the outgoing RTP flow of the first call is never restored.

I send a wireshark capture that illustrates this, with a call from a SipCommunicator (200.200.200.250) to a remote SIPPhone (200.200.200.10).

At second 6.350408 Call 1 starts :

You can see RTP packets incoming and outgoing from both peers

At second 11.367196 Call 2 starts :

You can see RTP packets incoming and outgoing from both peers, but from SC only the ones from the second call ...

At second 15.858766 Call 2 ends

You can see only RTP incoming packets from call 1

At second 21.090245 Call 1 ends :

No RTP traffic

Thanks for your attention

cap.pcap (324 KB)

···

-----Original Message-----

From: Emil Ivov [mailto:emcho@sip-communicator.org]

Sent: quarta-feira, 17 de Junho de 2009 14:10
To: Carlos Alexandre
Subject: Re: [sip-comm-dev] placing simultaneous calls

Yup saw it. Thanks!

Carlos Alexandre wrote:

Hi emil,

i opened the issue

thanks

-----Original Message-----

From: Emil Ivov [mailto:emcho@sip-communicator.org]

Sent: sábado, 13 de Junho de 2009 13:13

To: dev@sip-communicator.dev.java.net

Subject: Re: [sip-comm-dev] placing simultaneous calls

Carlos,

Carlos Alexandre wrote:

About the falling calls:

I found out that after being on hold for 30 seconds, the calls

disconnect.

I suppose this is a feature....

Definitely not. Could you please send logs and wireshark dumps here? If

this is not a server issue then we need to log it in the tracker.

Incidentally, could you please open an issue for 2.0 on making the

automatic on-hold behaviour configurable? We'd still need to do some

research on how users expect this to work but we'd better log it so that

we don't forget to ask around.

Cheers

Emil

Carlos

-----Original Message-----

From: Emil Ivov [mailto:emil@sip-communicator.org] On Behalf Of Emil

Ivov

Sent: quinta-feira, 28 de Maio de 2009 12:24

To: dev@sip-communicator.dev.java.net

Subject: Re: [sip-comm-dev] placing simultaneous calls

Hey Carlos,

Carlos Alexandre wrote:

Well, believe it or not, that was one of the features that we were

using

the most, and it was the perfect feature for our use of SC....

I think ill have a look at the code to reverse this.

Hm ... didn't realize this. Maybe we should think about making the

behaviour configuratble then.

About the falling calls, when u say "to log na issue", u mean send it

here?

Nah. I mean opening an issue on our issue tracker:

https://sip-communicator.dev.java.net/issues/enter_bug.cgi

Check this out if you need more details on working with issues:

http://www.sip-communicator.org/index.php/Development/BugsAndIssues

Cheers

Emil

Thanks for your work.

Carlos

-----Original Message-----

From: Emil Ivov [mailto:emil@sip-communicator.org] On Behalf Of Emil

Ivov

Sent: quarta-feira, 27 de Maio de 2009 17:03

To: dev@sip-communicator.dev.java.net

Subject: Re: [sip-comm-dev] placing simultaneous calls

Hey Carlos,

Carlos Alexandre wrote:

Hello

I upgraded recently from build 1661 to build 1896

I noticed that know its no longer possible to have more than one call

simultaneously (SIP).

When i place a second call, the first one goes automaticaly "on

Hold".

When i place a third call, the second one goes automaticaly "on

Hold",

and so on.

And usually after three calls simultaneous, one on them falls by it

self.

In previous builds this was not happening.

How can i reverse this feature, and keep simultaneous calls ?

Afraid you can't. At least not without changing the code. Putting the

first call on hold is intentional. We thought that having two calls in

parallel where you hear both your interlocutors but they don't hear

each

other would be a scenario that would probably confuse a many users.

We therefore decided to disable it until we implement proper

conferences.

As for the failing calls, this doesn't sound normal. Could you please

log an issue describing the problem and how to reproduce it?

Thanks

Emil

---------------------------------------------------------------------

To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net

For additional commands, e-mail:

dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------

To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net

For additional commands, e-mail:

dev-help@sip-communicator.dev.java.net

--

Emil Ivov, Ph.D. 67000 Strasbourg,

Project Lead France

SIP Communicator

emcho@sip-communicator.org FAX: +33.1.77.62.47.31

http://sip-communicator.org PHONE: +33.1.77.62.43.30


#14

Issue submited as 686.
Hope im not giving u a lot of work...

Carlos

···

-----Original Message-----

From: Emil Ivov [mailto:emcho@sip-communicator.org]

Sent: quarta-feira, 17 de Junho de 2009 17:43
To: dev@sip-communicator.dev.java.net
Subject: Re: [sip-comm-dev] falling "on hold" calls

Thanks for the report Carlos! Definitely very helpful!

There's no doubt that this is an SC issue so could you please create an
issue for this as well and paste your description and attachments in there?

Thanks
Emil

Carlos Alexandre wrote:

Emil:
This is what is happening:

1 - A call is established between asterisk SIP Server and SipCommunicator.
2 - The call is put on Hold on Sip Communicator
3 - From this moment on, Asterisk stops sending RTCP packets to SC.
4 - After 30 seconds without receiving packets from asterisk, SC sends na RTCP goodBye packet to Asterisk and disconnects the call with a "failed" message.
5 - Asterisk doesnt know how to handle with RTCP goodbye packet, and on its side the call continues on hold, though SC hás hung up.

Im sending you the whireshark dump....

200.200.200.249 is SC
200.200.200.10 is Asterisk

You can see that after being put on hold on second 53, only SC sends RTCP packets, and that at second 82 it sends a Goodbye.

Is there a way i can put the RTCP timeout on SC side to "infinity"? There is nothing i can do on Asterisk.....

thanks

Carlos

-----Original Message-----
From: Emil Ivov [mailto:emcho@sip-communicator.org]
Sent: sábado, 13 de Junho de 2009 13:13
To: dev@sip-communicator.dev.java.net
Subject: Re: [sip-comm-dev] placing simultaneous calls

Carlos,

Carlos Alexandre wrote:

About the falling calls:
I found out that after being on hold for 30 seconds, the calls
disconnect.

I suppose this is a feature....

Definitely not. Could you please send logs and wireshark dumps here? If
this is not a server issue then we need to log it in the tracker.

Incidentally, could you please open an issue for 2.0 on making the
automatic on-hold behaviour configurable? We'd still need to do some
research on how users expect this to work but we'd better log it so that
we don't forget to ask around.

Cheers
Emil

Carlos

-----Original Message-----
From: Emil Ivov [mailto:emil@sip-communicator.org] On Behalf Of Emil
Ivov
Sent: quinta-feira, 28 de Maio de 2009 12:24
To: dev@sip-communicator.dev.java.net
Subject: Re: [sip-comm-dev] placing simultaneous calls

Hey Carlos,

Carlos Alexandre wrote:

Well, believe it or not, that was one of the features that we were

using

the most, and it was the perfect feature for our use of SC....

I think ill have a look at the code to reverse this.

Hm ... didn't realize this. Maybe we should think about making the
behaviour configuratble then.

About the falling calls, when u say "to log na issue", u mean send it
here?

Nah. I mean opening an issue on our issue tracker:

https://sip-communicator.dev.java.net/issues/enter_bug.cgi

Check this out if you need more details on working with issues:

http://www.sip-communicator.org/index.php/Development/BugsAndIssues

Cheers
Emil

Thanks for your work.

Carlos

-----Original Message-----
From: Emil Ivov [mailto:emil@sip-communicator.org] On Behalf Of Emil
Ivov
Sent: quarta-feira, 27 de Maio de 2009 17:03
To: dev@sip-communicator.dev.java.net
Subject: Re: [sip-comm-dev] placing simultaneous calls

Hey Carlos,

Carlos Alexandre wrote:

Hello

I upgraded recently from build 1661 to build 1896

I noticed that know its no longer possible to have more than one call
simultaneously (SIP).

When i place a second call, the first one goes automaticaly "on

Hold".

When i place a third call, the second one goes automaticaly "on

Hold",

and so on.

And usually after three calls simultaneous, one on them falls by it
self.

In previous builds this was not happening.

How can i reverse this feature, and keep simultaneous calls ?

Afraid you can't. At least not without changing the code. Putting the
first call on hold is intentional. We thought that having two calls in
parallel where you hear both your interlocutors but they don't hear

each

other would be a scenario that would probably confuse a many users.

We therefore decided to disable it until we implement proper
conferences.

As for the failing calls, this doesn't sound normal. Could you please
log an issue describing the problem and how to reproduce it?

Thanks
Emil

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

dev-help@sip-communicator.dev.java.net

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

dev-help@sip-communicator.dev.java.net

------------------------------------------------------------------------

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

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
SIP Communicator
emcho@sip-communicator.org FAX: +33.1.77.62.47.31
http://sip-communicator.org PHONE: +33.1.77.62.43.30

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

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


#15

Hey Carlos,

I am afraid that we probably won't be looking at this issue any time in
the foreseeable future since we have other priorities.

You are welcome to submit a patch if you or someone else has the
resources to work on it.

Good luck,
Emil

Carlos Alexandre написа:

···

Hi guys

I placed Issue 684 - making the automatic on-hold behaviour
configurable a while ago,
(https://sip-communicator.dev.java.net/issues/show_bug.cgi?id=684) and I
saw

ubomirs followup "r5683 allows the feature to be disabled through the
configuration property
SingleCallInProgressPolicy#PNAME_SINGLE_CALL_IN_PROGRESS_POLICY_ENABLED,
no GUI is

provided.”

The SIP part of this issue is working perfectly, but there is still a
pronlem with the RTP packets:

When I place a second call, the outgoing RTP packets flow of the first
call stop. And even if I hang up the second call, the outgoing RTP flow
of the first call is never restored.

I send a wireshark capture that illustrates this, with a call from a
SipCommunicator (200.200.200.250) to a remote SIPPhone (200.200.200.10).

At second 6.350408 Call 1 starts :

You can see RTP packets incoming and outgoing from both peers

At second 11.367196 Call 2 starts :

You can see RTP packets incoming and outgoing from both peers, but from
SC only the ones from the second call …

At second 15.858766 Call 2 ends

You can see only RTP incoming packets from call 1

At second 21.090245 Call 1 ends :

No RTP traffic

Thanks for your attention

-----Original Message-----
From: Emil Ivov [mailto:emcho@sip-communicator.org]
Sent: quarta-feira, 17 de Junho de 2009 14:10
To: Carlos Alexandre
Subject: Re: [sip-comm-dev] placing simultaneous calls

Yup saw it. Thanks!

Carlos Alexandre wrote:

Hi emil,

i opened the issue

thanks

-----Original Message-----

From: Emil Ivov [mailto:emcho@sip-communicator.org]

Sent: sábado, 13 de Junho de 2009 13:13

To: dev@sip-communicator.dev.java.net

Subject: Re: [sip-comm-dev] placing simultaneous calls

Carlos,

Carlos Alexandre wrote:

About the falling calls:

I found out that after being on hold for 30 seconds, the calls

disconnect.

I suppose this is a feature....

Definitely not. Could you please send logs and wireshark dumps here? If

this is not a server issue then we need to log it in the tracker.

Incidentally, could you please open an issue for 2.0 on making the

automatic on-hold behaviour configurable? We'd still need to do some

research on how users expect this to work but we'd better log it so that

we don't forget to ask around.

Cheers

Emil

Carlos

-----Original Message-----

From: Emil Ivov [mailto:emil@sip-communicator.org] On Behalf Of Emil

Ivov

Sent: quinta-feira, 28 de Maio de 2009 12:24

To: dev@sip-communicator.dev.java.net

Subject: Re: [sip-comm-dev] placing simultaneous calls

Hey Carlos,

Carlos Alexandre wrote:

Well, believe it or not, that was one of the features that we were

using

the most, and it was the perfect feature for our use of SC....

I think ill have a look at the code to reverse this.

Hm ... didn't realize this. Maybe we should think about making the

behaviour configuratble then.

About the falling calls, when u say "to log na issue", u mean send it

here?

Nah. I mean opening an issue on our issue tracker:

https://sip-communicator.dev.java.net/issues/enter_bug.cgi

Check this out if you need more details on working with issues:

http://www.sip-communicator.org/index.php/Development/BugsAndIssues

Cheers

Emil

Thanks for your work.

Carlos

-----Original Message-----

From: Emil Ivov [mailto:emil@sip-communicator.org] On Behalf Of Emil

Ivov

Sent: quarta-feira, 27 de Maio de 2009 17:03

To: dev@sip-communicator.dev.java.net

Subject: Re: [sip-comm-dev] placing simultaneous calls

Hey Carlos,

Carlos Alexandre wrote:

Hello

I upgraded recently from build 1661 to build 1896

I noticed that know its no longer possible to have more than one call

simultaneously (SIP).

When i place a second call, the first one goes automaticaly "on

Hold".

When i place a third call, the second one goes automaticaly "on

Hold",

and so on.

And usually after three calls simultaneous, one on them falls by it

self.

In previous builds this was not happening.

How can i reverse this feature, and keep simultaneous calls ?

Afraid you can't. At least not without changing the code. Putting the

first call on hold is intentional. We thought that having two calls in

parallel where you hear both your interlocutors but they don't hear

each

other would be a scenario that would probably confuse a many users.

We therefore decided to disable it until we implement proper

conferences.

As for the failing calls, this doesn't sound normal. Could you please

log an issue describing the problem and how to reproduce it?

Thanks

Emil

---------------------------------------------------------------------

To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net

For additional commands, e-mail:

dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------

To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net

For additional commands, e-mail:

dev-help@sip-communicator.dev.java.net

--

Emil Ivov, Ph.D. 67000 Strasbourg,

Project Lead France

SIP Communicator

emcho@sip-communicator.org FAX: +33.1.77.62.47.31

http://sip-communicator.org PHONE: +33.1.77.62.43.30

------------------------------------------------------------------------

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

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
SIP Communicator
emcho@sip-communicator.org PHONE: +33.1.77.62.43.30
http://sip-communicator.org FAX: +33.1.77.62.47.31

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


#16

Carlos Alexandre wrote:

Issue submited as 686.

Thanks!

Hope im not giving u a lot of work...

Your reports are very valuable. Thanks for spending the effort of making
them this complete!

Cheers
Emil

···

Carlos

-----Original Message-----
From: Emil Ivov [mailto:emcho@sip-communicator.org]
Sent: quarta-feira, 17 de Junho de 2009 17:43
To: dev@sip-communicator.dev.java.net
Subject: Re: [sip-comm-dev] falling "on hold" calls

Thanks for the report Carlos! Definitely very helpful!

There's no doubt that this is an SC issue so could you please create an
issue for this as well and paste your description and attachments in there?

Thanks
Emil

Carlos Alexandre wrote:

Emil:
This is what is happening:

1 - A call is established between asterisk SIP Server and SipCommunicator.
2 - The call is put on Hold on Sip Communicator
3 - From this moment on, Asterisk stops sending RTCP packets to SC.
4 - After 30 seconds without receiving packets from asterisk, SC sends na RTCP goodBye packet to Asterisk and disconnects the call with a "failed" message.
5 - Asterisk doesnt know how to handle with RTCP goodbye packet, and on its side the call continues on hold, though SC hás hung up.

Im sending you the whireshark dump....

200.200.200.249 is SC
200.200.200.10 is Asterisk

You can see that after being put on hold on second 53, only SC sends RTCP packets, and that at second 82 it sends a Goodbye.

Is there a way i can put the RTCP timeout on SC side to "infinity"? There is nothing i can do on Asterisk.....

thanks

Carlos

-----Original Message-----
From: Emil Ivov [mailto:emcho@sip-communicator.org]
Sent: sábado, 13 de Junho de 2009 13:13
To: dev@sip-communicator.dev.java.net
Subject: Re: [sip-comm-dev] placing simultaneous calls

Carlos,

Carlos Alexandre wrote:

About the falling calls:
I found out that after being on hold for 30 seconds, the calls
disconnect.

I suppose this is a feature....

Definitely not. Could you please send logs and wireshark dumps here? If
this is not a server issue then we need to log it in the tracker.

Incidentally, could you please open an issue for 2.0 on making the
automatic on-hold behaviour configurable? We'd still need to do some
research on how users expect this to work but we'd better log it so that
we don't forget to ask around.

Cheers
Emil

Carlos

-----Original Message-----
From: Emil Ivov [mailto:emil@sip-communicator.org] On Behalf Of Emil
Ivov
Sent: quinta-feira, 28 de Maio de 2009 12:24
To: dev@sip-communicator.dev.java.net
Subject: Re: [sip-comm-dev] placing simultaneous calls

Hey Carlos,

Carlos Alexandre wrote:

Well, believe it or not, that was one of the features that we were

using

the most, and it was the perfect feature for our use of SC....

I think ill have a look at the code to reverse this.

Hm ... didn't realize this. Maybe we should think about making the
behaviour configuratble then.

About the falling calls, when u say "to log na issue", u mean send it
here?

Nah. I mean opening an issue on our issue tracker:

https://sip-communicator.dev.java.net/issues/enter_bug.cgi

Check this out if you need more details on working with issues:

http://www.sip-communicator.org/index.php/Development/BugsAndIssues

Cheers
Emil

Thanks for your work.

Carlos

-----Original Message-----
From: Emil Ivov [mailto:emil@sip-communicator.org] On Behalf Of Emil
Ivov
Sent: quarta-feira, 27 de Maio de 2009 17:03
To: dev@sip-communicator.dev.java.net
Subject: Re: [sip-comm-dev] placing simultaneous calls

Hey Carlos,

Carlos Alexandre wrote:

Hello

I upgraded recently from build 1661 to build 1896

I noticed that know its no longer possible to have more than one call
simultaneously (SIP).

When i place a second call, the first one goes automaticaly "on

Hold".

When i place a third call, the second one goes automaticaly "on

Hold",

and so on.

And usually after three calls simultaneous, one on them falls by it
self.

In previous builds this was not happening.

How can i reverse this feature, and keep simultaneous calls ?

Afraid you can't. At least not without changing the code. Putting the
first call on hold is intentional. We thought that having two calls in
parallel where you hear both your interlocutors but they don't hear

each

other would be a scenario that would probably confuse a many users.

We therefore decided to disable it until we implement proper
conferences.

As for the failing calls, this doesn't sound normal. Could you please
log an issue describing the problem and how to reproduce it?

Thanks
Emil

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

dev-help@sip-communicator.dev.java.net

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

dev-help@sip-communicator.dev.java.net

------------------------------------------------------------------------

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

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
SIP Communicator
emcho@sip-communicator.org FAX: +33.1.77.62.47.31
http://sip-communicator.org PHONE: +33.1.77.62.43.30

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


#17

Ill try to take a look at the code. Ive already seen that this is related to the way on hold is implemented...

···

-----Original Message-----

From: Emil Ivov [mailto:emil@sip-communicator.org] On Behalf Of Emil Ivov

Sent: sábado, 16 de Janeiro de 2010 10:20
To: dev@sip-communicator.dev.java.net
Subject: Re: [sip-comm-dev] placing simultaneous calls : RTP Problem

Hey Carlos,

I am afraid that we probably won't be looking at this issue any time in
the foreseeable future since we have other priorities.

You are welcome to submit a patch if you or someone else has the
resources to work on it.

Good luck,
Emil

Carlos Alexandre написа:

Hi guys

I placed Issue 684 - making the automatic on-hold behaviour
configurable a while ago,
(https://sip-communicator.dev.java.net/issues/show_bug.cgi?id=684) and I
saw

ubomirs followup "r5683 allows the feature to be disabled through the
configuration property
SingleCallInProgressPolicy#PNAME_SINGLE_CALL_IN_PROGRESS_POLICY_ENABLED,
no GUI is

provided.”

The SIP part of this issue is working perfectly, but there is still a
pronlem with the RTP packets:

When I place a second call, the outgoing RTP packets flow of the first
call stop. And even if I hang up the second call, the outgoing RTP flow
of the first call is never restored.

I send a wireshark capture that illustrates this, with a call from a
SipCommunicator (200.200.200.250) to a remote SIPPhone (200.200.200.10).

At second 6.350408 Call 1 starts :

You can see RTP packets incoming and outgoing from both peers

At second 11.367196 Call 2 starts :

You can see RTP packets incoming and outgoing from both peers, but from
SC only the ones from the second call …

At second 15.858766 Call 2 ends

You can see only RTP incoming packets from call 1

At second 21.090245 Call 1 ends :

No RTP traffic

Thanks for your attention

-----Original Message-----
From: Emil Ivov [mailto:emcho@sip-communicator.org]
Sent: quarta-feira, 17 de Junho de 2009 14:10
To: Carlos Alexandre
Subject: Re: [sip-comm-dev] placing simultaneous calls

Yup saw it. Thanks!

Carlos Alexandre wrote:

Hi emil,

i opened the issue

thanks

-----Original Message-----

From: Emil Ivov [mailto:emcho@sip-communicator.org]

Sent: sábado, 13 de Junho de 2009 13:13

To: dev@sip-communicator.dev.java.net

Subject: Re: [sip-comm-dev] placing simultaneous calls

Carlos,

Carlos Alexandre wrote:

About the falling calls:

I found out that after being on hold for 30 seconds, the calls

disconnect.

I suppose this is a feature....

Definitely not. Could you please send logs and wireshark dumps here? If

this is not a server issue then we need to log it in the tracker.

Incidentally, could you please open an issue for 2.0 on making the

automatic on-hold behaviour configurable? We'd still need to do some

research on how users expect this to work but we'd better log it so that

we don't forget to ask around.

Cheers

Emil

Carlos

-----Original Message-----

From: Emil Ivov [mailto:emil@sip-communicator.org] On Behalf Of Emil

Ivov

Sent: quinta-feira, 28 de Maio de 2009 12:24

To: dev@sip-communicator.dev.java.net

Subject: Re: [sip-comm-dev] placing simultaneous calls

Hey Carlos,

Carlos Alexandre wrote:

Well, believe it or not, that was one of the features that we were

using

the most, and it was the perfect feature for our use of SC....

I think ill have a look at the code to reverse this.

Hm ... didn't realize this. Maybe we should think about making the

behaviour configuratble then.

About the falling calls, when u say "to log na issue", u mean send it

here?

Nah. I mean opening an issue on our issue tracker:

https://sip-communicator.dev.java.net/issues/enter_bug.cgi

Check this out if you need more details on working with issues:

http://www.sip-communicator.org/index.php/Development/BugsAndIssues

Cheers

Emil

Thanks for your work.

Carlos

-----Original Message-----

From: Emil Ivov [mailto:emil@sip-communicator.org] On Behalf Of Emil

Ivov

Sent: quarta-feira, 27 de Maio de 2009 17:03

To: dev@sip-communicator.dev.java.net

Subject: Re: [sip-comm-dev] placing simultaneous calls

Hey Carlos,

Carlos Alexandre wrote:

Hello

I upgraded recently from build 1661 to build 1896

I noticed that know its no longer possible to have more than one call

simultaneously (SIP).

When i place a second call, the first one goes automaticaly "on

Hold".

When i place a third call, the second one goes automaticaly "on

Hold",

and so on.

And usually after three calls simultaneous, one on them falls by it

self.

In previous builds this was not happening.

How can i reverse this feature, and keep simultaneous calls ?

Afraid you can't. At least not without changing the code. Putting the

first call on hold is intentional. We thought that having two calls in

parallel where you hear both your interlocutors but they don't hear

each

other would be a scenario that would probably confuse a many users.

We therefore decided to disable it until we implement proper

conferences.

As for the failing calls, this doesn't sound normal. Could you please

log an issue describing the problem and how to reproduce it?

Thanks

Emil

---------------------------------------------------------------------

To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net

For additional commands, e-mail:

dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------

To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net

For additional commands, e-mail:

dev-help@sip-communicator.dev.java.net

--

Emil Ivov, Ph.D. 67000 Strasbourg,

Project Lead France

SIP Communicator

emcho@sip-communicator.org FAX: +33.1.77.62.47.31

http://sip-communicator.org PHONE: +33.1.77.62.43.30

------------------------------------------------------------------------

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

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
SIP Communicator
emcho@sip-communicator.org PHONE: +33.1.77.62.43.30
http://sip-communicator.org FAX: +33.1.77.62.47.31

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

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


#18

Hi guys

I have found some problems relating to simultaneous calls, putting calls on hold and muting calls.

When do u guys think ull have time to look at this?

I only use SC as a Sip Phone, and so I think that SC is very close to perfection...after these little problems are solved....

Thanks

Carlos

···

-----Original Message-----
From: Emil Ivov [mailto:emil@sip-communicator.org] On Behalf Of Emil Ivov
Sent: sábado, 16 de Janeiro de 2010 10:20
To: dev@sip-communicator.dev.java.net
Subject: Re: [sip-comm-dev] placing simultaneous calls : RTP Problem

Hey Carlos,

I am afraid that we probably won't be looking at this issue any time in
the foreseeable future since we have other priorities.

You are welcome to submit a patch if you or someone else has the
resources to work on it.

Good luck,
Emil

Carlos Alexandre написа:

Hi guys

I placed Issue 684 - making the automatic on-hold behaviour
configurable a while ago,
(https://sip-communicator.dev.java.net/issues/show_bug.cgi?id=684) and I
saw

ubomirs followup "r5683 allows the feature to be disabled through the
configuration property
SingleCallInProgressPolicy#PNAME_SINGLE_CALL_IN_PROGRESS_POLICY_ENABLED,
no GUI is

provided.”

The SIP part of this issue is working perfectly, but there is still a
pronlem with the RTP packets:

When I place a second call, the outgoing RTP packets flow of the first
call stop. And even if I hang up the second call, the outgoing RTP flow
of the first call is never restored.

I send a wireshark capture that illustrates this, with a call from a
SipCommunicator (200.200.200.250) to a remote SIPPhone (200.200.200.10).

At second 6.350408 Call 1 starts :

You can see RTP packets incoming and outgoing from both peers

At second 11.367196 Call 2 starts :

You can see RTP packets incoming and outgoing from both peers, but from
SC only the ones from the second call …

At second 15.858766 Call 2 ends

You can see only RTP incoming packets from call 1

At second 21.090245 Call 1 ends :

No RTP traffic

Thanks for your attention

-----Original Message-----
From: Emil Ivov [mailto:emcho@sip-communicator.org]
Sent: quarta-feira, 17 de Junho de 2009 14:10
To: Carlos Alexandre
Subject: Re: [sip-comm-dev] placing simultaneous calls

Yup saw it. Thanks!

Carlos Alexandre wrote:

Hi emil,

i opened the issue

thanks

-----Original Message-----

From: Emil Ivov [mailto:emcho@sip-communicator.org]

Sent: sábado, 13 de Junho de 2009 13:13

To: dev@sip-communicator.dev.java.net

Subject: Re: [sip-comm-dev] placing simultaneous calls

Carlos,

Carlos Alexandre wrote:

About the falling calls:

I found out that after being on hold for 30 seconds, the calls

disconnect.

I suppose this is a feature....

Definitely not. Could you please send logs and wireshark dumps here? If

this is not a server issue then we need to log it in the tracker.

Incidentally, could you please open an issue for 2.0 on making the

automatic on-hold behaviour configurable? We'd still need to do some

research on how users expect this to work but we'd better log it so that

we don't forget to ask around.

Cheers

Emil

Carlos

-----Original Message-----

From: Emil Ivov [mailto:emil@sip-communicator.org] On Behalf Of Emil

Ivov

Sent: quinta-feira, 28 de Maio de 2009 12:24

To: dev@sip-communicator.dev.java.net

Subject: Re: [sip-comm-dev] placing simultaneous calls

Hey Carlos,

Carlos Alexandre wrote:

Well, believe it or not, that was one of the features that we were

using

the most, and it was the perfect feature for our use of SC....

I think ill have a look at the code to reverse this.

Hm ... didn't realize this. Maybe we should think about making the

behaviour configuratble then.

About the falling calls, when u say "to log na issue", u mean send it

here?

Nah. I mean opening an issue on our issue tracker:

https://sip-communicator.dev.java.net/issues/enter_bug.cgi

Check this out if you need more details on working with issues:

http://www.sip-communicator.org/index.php/Development/BugsAndIssues

Cheers

Emil

Thanks for your work.

Carlos

-----Original Message-----

From: Emil Ivov [mailto:emil@sip-communicator.org] On Behalf Of Emil

Ivov

Sent: quarta-feira, 27 de Maio de 2009 17:03

To: dev@sip-communicator.dev.java.net

Subject: Re: [sip-comm-dev] placing simultaneous calls

Hey Carlos,

Carlos Alexandre wrote:

Hello

I upgraded recently from build 1661 to build 1896

I noticed that know its no longer possible to have more than one call

simultaneously (SIP).

When i place a second call, the first one goes automaticaly "on

Hold".

When i place a third call, the second one goes automaticaly "on

Hold",

and so on.

And usually after three calls simultaneous, one on them falls by it

self.

In previous builds this was not happening.

How can i reverse this feature, and keep simultaneous calls ?

Afraid you can't. At least not without changing the code. Putting the

first call on hold is intentional. We thought that having two calls in

parallel where you hear both your interlocutors but they don't hear

each

other would be a scenario that would probably confuse a many users.

We therefore decided to disable it until we implement proper

conferences.

As for the failing calls, this doesn't sound normal. Could you please

log an issue describing the problem and how to reproduce it?

Thanks

Emil

---------------------------------------------------------------------

To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net

For additional commands, e-mail:

dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------

To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net

For additional commands, e-mail:

dev-help@sip-communicator.dev.java.net

--

Emil Ivov, Ph.D. 67000 Strasbourg,

Project Lead France

SIP Communicator

emcho@sip-communicator.org FAX: +33.1.77.62.47.31

http://sip-communicator.org PHONE: +33.1.77.62.43.30

------------------------------------------------------------------------

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

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
SIP Communicator
emcho@sip-communicator.org PHONE: +33.1.77.62.43.30
http://sip-communicator.org FAX: +33.1.77.62.47.31

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

"Esta mensagem pode conter informao considerada confidencial, no devendo ser copiada ou endereada a terceiros. Se o receptor no for o destinatário apropriado, deverá destruir a mensagem e por gentileza informar o emissor do sucedido. O conteúdo desta mensagem, bem como dos respectivos anexos é da responsabilidade exclusiva do emissor, no podendo a Navegao Aérea de Portugal NAV Portugal, E.P.E. ser responsabilizada por eventuais consequências."

"This message may contain confidential information. You should not copy or address this message to anyone. If you are not the appropriate addressee, we ask you to kindly delete the message and notify the sender. The contents of this message and attachments are the responsibility of the individual sender and under no circumstances can Navegao Aérea de Portugal NAV Portugal, E.P.E. be liable for any resulting consequences."


#19

Hey Carlos,

Carlos Alexandre написа:

Hi guys

I have found some problems relating to simultaneous calls, putting calls on hold and muting calls.

When do u guys think ull have time to look at this?

Do you mean being able to keep the two calls going simultaneously
without putting either on hold? I am not aware of anyone planning to
work in that direction. We do support conference calls though which give
you exactly the same result with the only difference that the two
participants are able to hear each other. If that's bothering you then
you can put either of them on mute.

Hope this helps!
Emil

···

I only use SC as a Sip Phone, and so I think that SC is very close to perfection...after these little problems are solved....

Thanks

Carlos

-----Original Message-----
From: Emil Ivov [mailto:emil@sip-communicator.org] On Behalf Of Emil Ivov
Sent: sábado, 16 de Janeiro de 2010 10:20
To: dev@sip-communicator.dev.java.net
Subject: Re: [sip-comm-dev] placing simultaneous calls : RTP Problem

Hey Carlos,

I am afraid that we probably won't be looking at this issue any time in
the foreseeable future since we have other priorities.

You are welcome to submit a patch if you or someone else has the
resources to work on it.

Good luck,
Emil

Carlos Alexandre написа:

Hi guys

I placed Issue 684 - making the automatic on-hold behaviour
configurable a while ago,
(https://sip-communicator.dev.java.net/issues/show_bug.cgi?id=684) and I
saw

ubomirs followup "r5683 allows the feature to be disabled through the
configuration property
SingleCallInProgressPolicy#PNAME_SINGLE_CALL_IN_PROGRESS_POLICY_ENABLED,
no GUI is

provided.”

The SIP part of this issue is working perfectly, but there is still a
pronlem with the RTP packets:

When I place a second call, the outgoing RTP packets flow of the first
call stop. And even if I hang up the second call, the outgoing RTP flow
of the first call is never restored.

I send a wireshark capture that illustrates this, with a call from a
SipCommunicator (200.200.200.250) to a remote SIPPhone (200.200.200.10).

At second 6.350408 Call 1 starts :

You can see RTP packets incoming and outgoing from both peers

At second 11.367196 Call 2 starts :

You can see RTP packets incoming and outgoing from both peers, but from
SC only the ones from the second call …

At second 15.858766 Call 2 ends

You can see only RTP incoming packets from call 1

At second 21.090245 Call 1 ends :

No RTP traffic

Thanks for your attention

-----Original Message-----
From: Emil Ivov [mailto:emcho@sip-communicator.org]
Sent: quarta-feira, 17 de Junho de 2009 14:10
To: Carlos Alexandre
Subject: Re: [sip-comm-dev] placing simultaneous calls

Yup saw it. Thanks!

Carlos Alexandre wrote:

Hi emil,
i opened the issue
thanks
-----Original Message-----
From: Emil Ivov [mailto:emcho@sip-communicator.org]
Sent: sábado, 13 de Junho de 2009 13:13
To: dev@sip-communicator.dev.java.net
Subject: Re: [sip-comm-dev] placing simultaneous calls
Carlos,
Carlos Alexandre wrote:

About the falling calls:
I found out that after being on hold for 30 seconds, the calls
disconnect.
I suppose this is a feature....

Definitely not. Could you please send logs and wireshark dumps here? If
this is not a server issue then we need to log it in the tracker.
Incidentally, could you please open an issue for 2.0 on making the
automatic on-hold behaviour configurable? We'd still need to do some
research on how users expect this to work but we'd better log it so that
we don't forget to ask around.
Cheers
Emil

Carlos
-----Original Message-----
From: Emil Ivov [mailto:emil@sip-communicator.org] On Behalf Of Emil
Ivov
Sent: quinta-feira, 28 de Maio de 2009 12:24
To: dev@sip-communicator.dev.java.net
Subject: Re: [sip-comm-dev] placing simultaneous calls
Hey Carlos,
Carlos Alexandre wrote:

Well, believe it or not, that was one of the features that we were

using

the most, and it was the perfect feature for our use of SC....
I think ill have a look at the code to reverse this.

Hm ... didn't realize this. Maybe we should think about making the
behaviour configuratble then.

About the falling calls, when u say "to log na issue", u mean send it
here?

Nah. I mean opening an issue on our issue tracker:
https://sip-communicator.dev.java.net/issues/enter_bug.cgi
Check this out if you need more details on working with issues:
http://www.sip-communicator.org/index.php/Development/BugsAndIssues
Cheers
Emil

Thanks for your work.
Carlos
-----Original Message-----
From: Emil Ivov [mailto:emil@sip-communicator.org] On Behalf Of Emil
Ivov
Sent: quarta-feira, 27 de Maio de 2009 17:03
To: dev@sip-communicator.dev.java.net
Subject: Re: [sip-comm-dev] placing simultaneous calls
Hey Carlos,
Carlos Alexandre wrote:

Hello
I upgraded recently from build 1661 to build 1896
I noticed that know its no longer possible to have more than one call
simultaneously (SIP).
When i place a second call, the first one goes automaticaly "on

Hold".

When i place a third call, the second one goes automaticaly "on

Hold",

and so on.
And usually after three calls simultaneous, one on them falls by it
self.
In previous builds this was not happening.
How can i reverse this feature, and keep simultaneous calls ?

Afraid you can't. At least not without changing the code. Putting the
first call on hold is intentional. We thought that having two calls in
parallel where you hear both your interlocutors but they don't hear

each

other would be a scenario that would probably confuse a many users.
We therefore decided to disable it until we implement proper
conferences.
As for the failing calls, this doesn't sound normal. Could you please
log an issue describing the problem and how to reproduce it?
Thanks
Emil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail:

dev-help@sip-communicator.dev.java.net

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

dev-help@sip-communicator.dev.java.net

--

Emil Ivov, Ph.D. 67000 Strasbourg,

Project Lead France

SIP Communicator

emcho@sip-communicator.org FAX: +33.1.77.62.47.31

http://sip-communicator.org PHONE: +33.1.77.62.43.30

------------------------------------------------------------------------

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

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
SIP Communicator
emcho@sip-communicator.org PHONE: +33.1.77.62.43.30
http://sip-communicator.org FAX: +33.1.77.62.47.31

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