Hi all,
Looking at XX-6450, it seems that we are indeed getting a stand-alone
process (jetty instance) for CounterPath provisioning.
Just to confirm, this will show up as a new "Service" in sipXconfig?
It makes sense to make this a new "sipXprovision" service, which could
be used for XX-6550 as well. (See
http://list.sipfoundry.org/archive/sipx-dev/msg19585.html.)
-Paul
________________________________
From: [email protected]
[mailto:[email protected]] On Behalf Of Mircea Mihai
Carasel
Sent: September 7, 2009 7:15 PM
To: [email protected]
Subject: [sipX-dev] XX-6450: Extract Counterpath phone
provisioning into itsown process
Hi,
I made some progress on XX-6450, but there are still some issues
that I would like to share on the list.
Currently, I was able to use two different jetty configuration
files for sipXconfig and cmcprov webapps
I also was able to individually start sipXconfig or cmcprov in a
jetty instance.
However, I wasn't able to start both apps in two different jetty
instances.
1. Independently configure webapp security/policies
I am thinking if we really need to have two jetty instances
running in the same JVM, since each webapp configuration
comes in Jetty using: <Call name="addListener">.
So, even if we have only one jetty instance per JVM, looks like
we independently define webapp security/policies
sipXconfig:
<Call name="addListener">
<Arg>
<New class="org.mortbay.http.SslListener">
<Set name="Port">8443</Set>
<Set name="Keystore"><SystemProperty
name="jetty.conf.dir"/>/ssl/ssl-web.keystore</Set>
<Set name="Password">changeit</Set>
<Set name="KeyPassword">changeit</Set>
<Set name="PoolName">P1</Set>
<Set name="MinThreads">20</Set>
<Set name="MaxThreads">200</Set>
<Set name="lowResources">50</Set>
<Set name="MaxIdleTimeMs">30000</Set>
<Set name="LowResourcePersistTimeMs">2000</Set>
<Set name="acceptQueueSize">0</Set>
<Set name="algorithm"><SystemProperty
name="jetty.x509.algorithm"/></Set>
<Set name="protocol">SSLv3</Set>
</New>
</Arg>
</Call>
cmcprov:
<Call name="addListener">
<Arg>
<New class="org.mortbay.http.SocketListener">
<Set name="Port">12000</Set>
<Set name="PoolName">P2</Set>
<Set name="MinThreads">20</Set>
<Set name="MaxThreads">200</Set>
</New>
</Arg>
</Call>
2.Starting each app on a different node in the cluster
a)Jetty is started by sipxconfig.sh as follows:
exec $JavaCmd \
$SystemProps \
$JavaOpts \
$TrustStoreOpts \
$KeyStoreOpts \
-classpath "$Classpath" \
org.mortbay.jetty.Server
@sipxpbx.conf.dir@/sipxconfig-jetty.xml
b)For starting cmcprov we should call on a different cluster
something like:
exec $JavaCmd \
$SystemProps \
$JavaOpts \
$TrustStoreOpts \
$KeyStoreOpts \
-classpath "$Classpath" \
org.mortbay.jetty.Server
@sipxpbx.conf.dir@/cmcprov-jetty.xml
c)If we start sipXconfig and cmcprov in the same cluster (one
Jetty instance):
exec $JavaCmd \
$SystemProps \
$JavaOpts \
$TrustStoreOpts \
$KeyStoreOpts \
-classpath "$Classpath" \
org.mortbay.jetty.Server
@sipxpbx.conf.dir@/sipxconfig-jetty.xml
@sipxpbx.conf.dir@/cmcprov-jetty.xml
Please share your thoughts
Regards,
Mircea
_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/
