I have searched the dev and user mailing lists and can find no hardware
requirements. Is there a list of minimum requirements somewhere?

Not officially. As far as I know most developers are using machines with about 1GB RAM and around 2GHz CPU. I guess you could also run SIP Communicator on less than that but I doubt you'd get reasonable performance with less than 256MB RAM and 1 GHz CPU.

Also, I know you are trying to stay Java 1.4 compatible. Should all
Communicator development use the 1.4 SDK, and be built with 1.4?

There has been some talk about moving to 1.5 as a minimum requirement but I don't think that, as of now, we have settled on an official migration schedule.

Therefore, in case you are planning on making contributions to the SIP Communicator project, it would indeed be appreciated that you try to keep the 1.4 compatibility. Otherwise, in case you are developing modules for your own use you are free to use whatever J version best suits you.

So, any Windows OS will do?
We're using Asterisk; do some telephony platforms work better with the
Communicator than others?

Also, we *are* doing some in-house development and because we are having
some trouble getting 2-way communication on some of our machines, I wondered
if using non-1.4 Java to code and build might be causing some of our issues.
(you're talking to a C++ developer, no Java experience)

I have searched the dev and user mailing lists and can find no hardware
requirements. Is there a list of minimum requirements somewhere?

Not officially. As far as I know most developers are using machines with
about 1GB RAM and around 2GHz CPU. I guess you could also run SIP
Communicator on less than that but I doubt you'd get reasonable
performance with less than 256MB RAM and 1 GHz CPU.

Also, I know you are trying to stay Java 1.4 compatible. Should all
Communicator development use the 1.4 SDK, and be built with 1.4?

There has been some talk about moving to 1.5 as a minimum requirement
but I don't think that, as of now, we have settled on an official
migration schedule.

Therefore, in case you are planning on making contributions to the SIP
Communicator project, it would indeed be appreciated that you try to
keep the 1.4 compatibility. Otherwise, in case you are developing
modules for your own use you are free to use whatever J version best
suits you.

I guess so, though I don't know whether anyone has tested it against Win 95/98/ME.

We're using Asterisk; do some telephony platforms work better with the
Communicator than others?

We are doing most of our testing against an Asterisk ourselves. I think that others have also successfully used SIP Communicator with SER and OpenSER.

Also, we *are* doing some in-house development and because we are having
some trouble getting 2-way communication on some of our machines, I wondered
if using non-1.4 Java to code and build might be causing some of our issues.
(you're talking to a C++ developer, no Java experience)

I've been hearing stories about audio capture problems with J 1.5, but it's supposed to be ok with 1.4 and 1.6. Therefore, if you're doing your tests with 1.5, you may want to switch to 1.6 and give them a try with it.

I have searched the dev and user mailing lists and can find no hardware
requirements. Is there a list of minimum requirements somewhere?

Not officially. As far as I know most developers are using machines with about 1GB RAM and around 2GHz CPU. I guess you could also run SIP Communicator on less than that but I doubt you'd get reasonable performance with less than 256MB RAM and 1 GHz CPU.

Also, I know you are trying to stay Java 1.4 compatible. Should all
Communicator development use the 1.4 SDK, and be built with 1.4?

There has been some talk about moving to 1.5 as a minimum requirement but I don't think that, as of now, we have settled on an official migration schedule.

Therefore, in case you are planning on making contributions to the SIP Communicator project, it would indeed be appreciated that you try to keep the 1.4 compatibility. Otherwise, in case you are developing modules for your own use you are free to use whatever J version best suits you.

Also, we *are* doing some in-house development and because we are having
some trouble getting 2-way communication on some of our machines, I wondered
if using non-1.4 Java to code and build might be causing some of our issues.
(you're talking to a C++ developer, no Java experience)

which version of sip-communicator you are using as there were recently some bug fixes on this issues.
Also if there is nat between SC and * make sure nat=yes is set in * (if you haven't set it).

I guess so, though I don't know whether anyone has tested it against Win
95/98/ME.

We're using Asterisk; do some telephony platforms work better with the
Communicator than others?

We are doing most of our testing against an Asterisk ourselves. I think
that others have also successfully used SIP Communicator with SER and
OpenSER.

Also, we *are* doing some in-house development and because we are having
some trouble getting 2-way communication on some of our machines, I

wondered

if using non-1.4 Java to code and build might be causing some of our

issues.

(you're talking to a C++ developer, no Java experience)

I've been hearing stories about audio capture problems with J 1.5, but
it's supposed to be ok with 1.4 and 1.6. Therefore, if you're doing your
tests with 1.5, you may want to switch to 1.6 and give them a try with it.

I have searched the dev and user mailing lists and can find no hardware
requirements. Is there a list of minimum requirements somewhere?

Not officially. As far as I know most developers are using machines with
about 1GB RAM and around 2GHz CPU. I guess you could also run SIP
Communicator on less than that but I doubt you'd get reasonable
performance with less than 256MB RAM and 1 GHz CPU.

Also, I know you are trying to stay Java 1.4 compatible. Should all
Communicator development use the 1.4 SDK, and be built with 1.4?

There has been some talk about moving to 1.5 as a minimum requirement
but I don't think that, as of now, we have settled on an official
migration schedule.

Therefore, in case you are planning on making contributions to the SIP
Communicator project, it would indeed be appreciated that you try to
keep the 1.4 compatibility. Otherwise, in case you are developing
modules for your own use you are free to use whatever J version best
suits you.