[jitsi-dev] JAIN SIP log4j 1.2.x issue


#1

Has anybody encountered an issue like this with JAIN SIP in Jitsi?

https://issues.apache.org/jira/browse/CAMEL-10071


#2

Has anybody encountered an issue like this with JAIN SIP in Jitsi?

https://issues.apache.org/jira/browse/CAMEL-10071

No, we're still using log4j-1.2

But: The reference to jain-sip-ri in Camel goes to version 1.2.169, which is rather old and I see there have been changes to how the logger is addressed. You can also specify your own logger wrapper by setting the stack property gov.nist.javax.sip.STACK_LOGGER to a class name that implements StackLogger.

I'm not sure what the servicemix-bundles adds to the jain-sip-ri jar, but you could try using a Jitsi-version to get a) a more recent version of the jain-sip-ri and b) a dependency that is free of the javax.sip licensing issues (the code isn't included there).

<dependency>
    <groupId>org.jitsi</groupId>
    <artifactId>jain-sip-ri-ossonly</artifactId>
    <version>1.2.279-jitsi-oss1</version>
</dependency>

Ingo


#3

Does that version work with the revised java-sip-api JAR?

https://github.com/opentelecoms-org/java-sip-api

The Apache Camel project already accepted a pull request for that

https://issues.apache.org/jira/browse/CAMEL-9021

···

On 18/06/16 21:21, Ingo Bauersachs wrote:

Has anybody encountered an issue like this with JAIN SIP in Jitsi?

https://issues.apache.org/jira/browse/CAMEL-10071

No, we're still using log4j-1.2

But: The reference to jain-sip-ri in Camel goes to version 1.2.169, which is rather old and I see there have been changes to how the logger is addressed. You can also specify your own logger wrapper by setting the stack property gov.nist.javax.sip.STACK_LOGGER to a class name that implements StackLogger.

I'm not sure what the servicemix-bundles adds to the jain-sip-ri jar, but you could try using a Jitsi-version to get a) a more recent version of the jain-sip-ri and b) a dependency that is free of the javax.sip licensing issues (the code isn't included there).

<dependency>
    <groupId>org.jitsi</groupId>
    <artifactId>jain-sip-ri-ossonly</artifactId>
    <version>1.2.279-jitsi-oss1</version>
</dependency>


#4

I'm not sure what the servicemix-bundles adds to the jain-sip-ri jar, but
you could try using a Jitsi-version to get a) a more recent version of the
jain-sip-ri and b) a dependency that is free of the javax.sip licensing
issues (the code isn't included there).

<dependency>
    <groupId>org.jitsi</groupId>
    <artifactId>jain-sip-ri-ossonly</artifactId>
    <version>1.2.279-jitsi-oss1</version>
</dependency>

Does that version work with the revised java-sip-api JAR?
https://github.com/opentelecoms-org/java-sip-api

Yes, it's what we're using in Jitsi and ice4j now.

The Apache Camel project already accepted a pull request for that
https://issues.apache.org/jira/browse/CAMEL-9021

I'm afraid but this isn't enough to circumvent the licensing issue:
The jain-sip-ri jar still contains the javax.sip headers. And you cannot simply strip these files from the jar (because of the issues I mentioned in https://github.com/opentelecoms-org/java-sdp-api/pull/2)

Ingo