|
  |
| Author |
Message |
jimijani1982
Brekeke Member
Joined: 12 Dec 2006
Posts: 17
|
 Posted: Thu Mar 12, 2009 3:40 am Post subject: ssl support & max number of users allowed in sip server |
 |
|
1. Brekeke Product Name and version: brekekee sip server standard
2. Java version: 1.6
3. OS type and the version: xp/vista
4. UA (phone), gateway or other hardware/software involved:sjphone
5. Select your network pattern from http://www.brekeke-sip.com/bbs/network/networkpatterns.html :
6. Your problem:2 question
1. does sip server / pbx has ssl support
2. what is the max number of users that can be added to a sip server ( i.e user id & password ) , eg , if i set up a brekekee sip server for a bank , and i need a sip account for every account holder . how can i add say 1 milltion users ? |
|
| Back to top |
|
hope
Brekeke Master Guru
Joined: 15 Jan 2008
Posts: 862
|
|
| Back to top |
|
jimijani1982
Brekeke Member
Joined: 12 Dec 2006
Posts: 17
|
| Posted: Fri Mar 13, 2009 2:54 am Post subject: |
|
|
maybe i was not able to explain my first question ,
i was talking w.r.t communication b/w the 2 ends . i.e 2 sip agents . what security can be added such any even if anyone catches the packet through some sniffer , he get every thing encripted . |
|
| Back to top |
|
Mike
Support Team
Joined: 07 Mar 2005
Posts: 731
Location: Sunny San Mateo
|
| Posted: Fri Mar 13, 2009 2:34 pm Post subject: |
|
|
Hi ALL,
>1. does sip server / pbx has ssl support
We are planning to implement it in future versions.
> 2. what is the max number of users that can be added to a sip server ( i.e user id & password ) ,
Unlimited. It depends on database.
> how can i add say 1 milltion users ?
I recommend that you access the database directly.
Please refer the document below.
http://www.brekeke-sip.com/download/bss/v2_1/3rd_party_database_en.pdf
Thanks |
|
| Back to top |
|
KentC
Brekeke Guru
Joined: 09 Dec 2011
Posts: 108
Location: rw-rw-rw-
|
| Posted: Sun Sep 28, 2014 9:54 pm Post subject: |
|
|
Here is my guide to setup Brekeke Sip Server v.2.4.8.6 [XP/Windows Server 2003 R2] w/ SSL for admintool [EASY TO FOLLOW]
NOTES TAKEN FROM HERE:
http://wiki.brekeke.com/wiki/Connect-to-the-BSS-Admintool-with-SSL
KENT C. TUTORIAL:
"HOW TO MAKE BREKEKE SIP SERVER SSL CERTIFICATE FOR ADMINTOOL"
STEP ONE:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
GO TO THE FOLLOWING PATH: C:\Program Files\Java\jre6\bin>
cd C:\
C:\>cd "Program Files"
C:\Program Files>cd Java
C:\Program Files\Java>cd jre6
C:\Program Files\Java\jre6>cd bin
RUN THE JAVA KEYTOOL CMD PROMPT TOOL IN COMMAND PROMPT:
C:\Program Files\Java\jre6\bin>keytool -genkey -alias tomcat -keyalg RSA
Enter keystore password:
Re-enter new password:
What is your first and last name?
[Unknown]: Brekeke
What is the name of your organizational unit?
[Unknown]: Brekeke
What is the name of your organization?
[Unknown]: Brekeke
What is the name of your City or Locality?
[Unknown]: US
What is the name of your State or Province?
[Unknown]: US
What is the two-letter country code for this unit?
[Unknown]: US
Is CN=Brekeke, OU=Brekeke, O=Brekeke, L=US, ST=US, C=US correct?
[no]: yes
Enter key password for <tomcat>
(RETURN if same as keystore password):
Re-enter new password:
C:\Program Files\Java\jre6\bin> exit
STEP TWO:
REPLACE SERVER.XML DEFAULT FILE WITH THE FOLLOWING [SELECT ALL / COPY / PASTE] - I'VE UNCOMMENTED THE SSL PORT 8443 HERE
My path on XP = C:\Program Files\Brekeke\proxy\conf
| Code: |
<!-- Example Server Configuration File -->
<!-- Note that component elements are nested corresponding to their
parent-child relationships with each other -->
<!-- A "Server" is a singleton element that represents the entire JVM,
which may contain one or more "Service" instances. The Server
listens for a shutdown command on the indicated port.
Note: A "Server" is not itself a "Container", so you may not
define subcomponents such as "Valves" or "Loggers" at this level.
-->
<Server port="28005" shutdown="SHUTDOWN">
<!-- Comment these entries out to disable JMX MBeans support used for the
administration web application -->
<Listener className="org.apache.catalina.core.AprLifecycleListener" />
<Listener className="org.apache.catalina.mbeans.ServerLifecycleListener" />
<Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" />
<Listener className="org.apache.catalina.storeconfig.StoreConfigLifecycleListener"/>
<!-- Global JNDI resources -->
<GlobalNamingResources>
<!-- Test entry for demonstration purposes -->
<Environment name="simpleValue" type="java.lang.Integer" value="30"/>
<!-- Editable user database that can also be used by
UserDatabaseRealm to authenticate users -->
<Resource name="UserDatabase" auth="Container"
type="org.apache.catalina.UserDatabase"
description="User database that can be updated and saved"
factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
pathname="conf/tomcat-users.xml" />
</GlobalNamingResources>
<!-- A "Service" is a collection of one or more "Connectors" that share
a single "Container" (and therefore the web applications visible
within that Container). Normally, that Container is an "Engine",
but this is not required.
Note: A "Service" is not itself a "Container", so you may not
define subcomponents such as "Valves" or "Loggers" at this level.
-->
<!-- Define the Tomcat Stand-Alone Service -->
<Service name="Catalina">
<!-- A "Connector" represents an endpoint by which requests are received
and responses are returned. Each Connector passes requests on to the
associated "Container" (normally an Engine) for processing.
By default, a non-SSL HTTP/1.1 Connector is established on port 8080.
You can also enable an SSL HTTP/1.1 Connector on port 8443 by
following the instructions below and uncommenting the second Connector
entry. SSL support requires the following steps (see the SSL Config
HOWTO in the Tomcat 5 documentation bundle for more detailed
instructions):
* If your JDK version 1.3 or prior, download and install JSSE 1.0.2 or
later, and put the JAR files into "$JAVA_HOME/jre/lib/ext".
* Execute:
%JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA (Windows)
$JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA (Unix)
with a password value of "changeit" for both the certificate and
the keystore itself.
By default, DNS lookups are enabled when a web application calls
request.getRemoteHost(). This can have an adverse impact on
performance, so you can disable it by setting the
"enableLookups" attribute to "false". When DNS lookups are disabled,
request.getRemoteHost() will return the String version of the
IP address of the remote client.
-->
<!-- Define a non-SSL HTTP/1.1 Connector on port 28080 -->
<Connector
port="8080" maxHttpHeaderSize="8192"
maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
enableLookups="false" redirectPort="8443" acceptCount="100"
connectionTimeout="20000" disableUploadTimeout="true" />
<!-- Note : To disable connection timeouts, set connectionTimeout value
to 0 -->
<!-- Note : To use gzip compression you could set the following properties :
compression="on"
compressionMinSize="2048"
noCompressionUserAgents="gozilla, traviata"
compressableMimeType="text/html,text/xml"
-->
<!-- Define a SSL HTTP/1.1 Connector on port 8443 -->
<Connector protocol="HTTP/1.1" port="8443" maxHttpHeaderSize="8192"
maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
enableLookups="false" disableUploadTimeout="true"
acceptCount="100" scheme="https" secure="true"
clientAuth="false" sslProtocol="TLS" />
-->
<!-- Define an AJP 1.3 Connector on port 28009 -->
<Connector port="28009"
enableLookups="false" redirectPort="8443" protocol="AJP/1.3" />
<!-- Define a Proxied HTTP/1.1 Connector on port 28082 -->
<!-- See proxy documentation for more information about using this. -->
<!--
<Connector port="28082"
maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
enableLookups="false" acceptCount="100" connectionTimeout="20000"
proxyPort="80" disableUploadTimeout="true" />
-->
<!-- An Engine represents the entry point (within Catalina) that processes
every request. The Engine implementation for Tomcat stand alone
analyzes the HTTP headers included with the request, and passes them
on to the appropriate Host (virtual host). -->
<!-- You should set jvmRoute to support load-balancing via AJP ie :
<Engine name="Standalone" defaultHost="localhost" jvmRoute="jvm1">
-->
<!-- Define the top level container in our container hierarchy -->
<Engine name="Catalina" defaultHost="localhost">
<!-- The request dumper valve dumps useful debugging information about
the request headers and cookies that were received, and the response
headers and cookies that were sent, for all requests received by
this instance of Tomcat. If you care only about requests to a
particular virtual host, or a particular application, nest this
element inside the corresponding <Host> or <Context> entry instead.
For a similar mechanism that is portable to all Servlet 2.4
containers, check out the "RequestDumperFilter" Filter in the
example application (the source for this filter may be found in
"$CATALINA_HOME/webapps/examples/WEB-INF/classes/filters").
Request dumping is disabled by default. Uncomment the following
element to enable it. -->
<!--
<Valve className="org.apache.catalina.valves.RequestDumperValve"/>
-->
<!-- Because this Realm is here, an instance will be shared globally -->
<!-- This Realm uses the UserDatabase configured in the global JNDI
resources under the key "UserDatabase". Any edits
that are performed against this UserDatabase are immediately
available for use by the Realm. -->
<Realm className="org.apache.catalina.realm.UserDatabaseRealm"
resourceName="UserDatabase"/>
<!-- Comment out the old realm but leave here for now in case we
need to go back quickly -->
<!--
<Realm className="org.apache.catalina.realm.MemoryRealm" />
-->
<!-- Replace the above Realm with one of the following to get a Realm
stored in a database and accessed via JDBC -->
<!--
<Realm className="org.apache.catalina.realm.JDBCRealm"
driverName="org.gjt.mm.mysql.Driver"
connectionURL="jdbc:mysql://localhost/authority"
connectionName="test" connectionPassword="test"
userTable="users" userNameCol="user_name" userCredCol="user_pass"
userRoleTable="user_roles" roleNameCol="role_name" />
-->
<!--
<Realm className="org.apache.catalina.realm.JDBCRealm"
driverName="oracle.jdbc.driver.OracleDriver"
connectionURL="jdbc:oracle:thin:@ntserver:1521:ORCL"
connectionName="scott" connectionPassword="tiger"
userTable="users" userNameCol="user_name" userCredCol="user_pass"
userRoleTable="user_roles" roleNameCol="role_name" />
-->
<!--
<Realm className="org.apache.catalina.realm.JDBCRealm"
driverName="sun.jdbc.odbc.JdbcOdbcDriver"
connectionURL="jdbc:odbc:CATALINA"
userTable="users" userNameCol="user_name" userCredCol="user_pass"
userRoleTable="user_roles" roleNameCol="role_name" />
-->
<!-- Define the default virtual host
Note: XML Schema validation will not work with Xerces 2.2.
-->
<Host name="localhost" appBase="webapps"
unpackWARs="true" autoDeploy="true" liveDeploy="false"
xmlValidation="false" xmlNamespaceAware="false">
<!-- Defines a cluster for this node,
By defining this element, means that every manager will be changed.
So when running a cluster, only make sure that you have webapps in there
that need to be clustered and remove the other ones.
A cluster has the following parameters:
className = the fully qualified name of the cluster class
name = a descriptive name for your cluster, can be anything
mcastAddr = the multicast address, has to be the same for all the nodes
mcastPort = the multicast port, has to be the same for all the nodes
mcastBindAddr = bind the multicast socket to a specific address
mcastTTL = the multicast TTL if you want to limit your broadcast
mcastSoTimeout = the multicast readtimeout
mcastFrequency = the number of milliseconds in between sending a "I'm alive" heartbeat
mcastDropTime = the number a milliseconds before a node is considered "dead" if no heartbeat is received
tcpThreadCount = the number of threads to handle incoming replication requests, optimal would be the same amount of threads as nodes
tcpListenAddress = the listen address (bind address) for TCP cluster request on this host,
in case of multiple ethernet cards.
auto means that address becomes
InetAddress.getLocalHost().getHostAddress()
tcpListenPort = the tcp listen port
tcpSelectorTimeout = the timeout (ms) for the Selector.select() method in case the OS
has a wakup bug in java.nio. Set to 0 for no timeout
printToScreen = true means that managers will also print to std.out
expireSessionsOnShutdown = true means that
useDirtyFlag = true means that we only replicate a session after setAttribute,removeAttribute has been called.
false means to replicate the session after each request.
false means that replication would work for the following piece of code: (only for SimpleTcpReplicationManager)
<%
HashMap map = (HashMap)session.getAttribute("map");
map.put("key","value");
%>
replicationMode = can be either 'pooled', 'synchronous' or 'asynchronous'.
* Pooled means that the replication happens using several sockets in a synchronous way. Ie, the data gets replicated, then the request return. This is the same as the 'synchronous' setting except it uses a pool of sockets, hence it is multithreaded. This is the fastest and safest configuration. To use this, also increase the nr of tcp threads that you have dealing with replication.
* Synchronous means that the thread that executes the request, is also the
thread the replicates the data to the other nodes, and will not return until all
nodes have received the information.
* Asynchronous means that there is a specific 'sender' thread for each cluster node,
so the request thread will queue the replication request into a "smart" queue,
and then return to the client.
The "smart" queue is a queue where when a session is added to the queue, and the same session
already exists in the queue from a previous request, that session will be replaced
in the queue instead of replicating two requests. This almost never happens, unless there is a
large network delay.
-->
<!--
When configuring for clustering, you also add in a valve to catch all the requests
coming in, at the end of the request, the session may or may not be replicated.
A session is replicated if and only if all the conditions are met:
1. useDirtyFlag is true or setAttribute or removeAttribute has been called AND
2. a session exists (has been created)
3. the request is not trapped by the "filter" attribute
The filter attribute is to filter out requests that could not modify the session,
hence we don't replicate the session after the end of this request.
The filter is negative, ie, anything you put in the filter, you mean to filter out,
ie, no replication will be done on requests that match one of the filters.
The filter attribute is delimited by ;, so you can't escape out ; even if you wanted to.
filter=".*\.gif;.*\.js;" means that we will not replicate the session after requests with the URI
ending with .gif and .js are intercepted.
The deployer element can be used to deploy apps cluster wide.
Currently the deployment only deploys/undeploys to working members in the cluster
so no WARs are copied upons startup of a broken node.
The deployer watches a directory (watchDir) for WAR files when watchEnabled="true"
When a new war file is added the war gets deployed to the local instance,
and then deployed to the other instances in the cluster.
When a war file is deleted from the watchDir the war is undeployed locally
and cluster wide
-->
<!--
<Cluster className="org.apache.catalina.cluster.tcp.SimpleTcpCluster"
managerClassName="org.apache.catalina.cluster.session.DeltaManager"
expireSessionsOnShutdown="false"
useDirtyFlag="true"
notifyListenersOnReplication="true">
<Membership
className="org.apache.catalina.cluster.mcast.McastService"
mcastAddr="228.0.0.4"
mcastPort="45564"
mcastFrequency="500"
mcastDropTime="3000"/>
<Receiver
className="org.apache.catalina.cluster.tcp.ReplicationListener"
tcpListenAddress="auto"
tcpListenPort="24001"
tcpSelectorTimeout="100"
tcpThreadCount="6"/>
<Sender
className="org.apache.catalina.cluster.tcp.ReplicationTransmitter"
replicationMode="pooled"
ackTimeout="15000"/>
<Valve className="org.apache.catalina.cluster.tcp.ReplicationValve"
filter=".*\.gif;.*\.js;.*\.jpg;.*\.htm;.*\.html;.*\.txt;"/>
<Deployer className="org.apache.catalina.cluster.deploy.FarmWarDeployer"
tempDir="/tmp/war-temp/"
deployDir="/tmp/war-deploy/"
watchDir="/tmp/war-listen/"
watchEnabled="false"/>
</Cluster>
-->
<!-- Normally, users must authenticate themselves to each web app
individually. Uncomment the following entry if you would like
a user to be authenticated the first time they encounter a
resource protected by a security constraint, and then have that
user identity maintained across *all* web applications contained
in this virtual host. -->
<!--
<Valve className="org.apache.catalina.authenticator.SingleSignOn" />
-->
<!-- Access log processes all requests for this virtual host. By
default, log files are created in the "logs" directory relative to
$CATALINA_HOME. If you wish, you can specify a different
directory with the "directory" attribute. Specify either a relative
(to $CATALINA_HOME) or absolute path to the desired directory.
-->
<!--
<Valve className="org.apache.catalina.valves.AccessLogValve"
directory="logs" prefix="localhost_access_log." suffix=".txt"
pattern="common" resolveHosts="false"/>
-->
<!-- Access log processes all requests for this virtual host. By
default, log files are created in the "logs" directory relative to
$CATALINA_HOME. If you wish, you can specify a different
directory with the "directory" attribute. Specify either a relative
(to $CATALINA_HOME) or absolute path to the desired directory.
This access log implementation is optimized for maximum performance,
but is hardcoded to support only the "common" and "combined" patterns.
-->
<!--
<Valve className="org.apache.catalina.valves.FastCommonAccessLogValve"
directory="logs" prefix="localhost_access_log." suffix=".txt"
pattern="common" resolveHosts="false"/>
-->
</Host>
</Engine>
</Service>
</Server>
|
***SAVE/CLOSE TO SERVER.XML***
***SINCE I USED THE FOLLOWING INSTALLER***
sip2_4_8_6.exe [WINDOWS XP]
***IT COMES WITH TOMCAT5 SO YOU CAN SKIP CONFIGURING TOMCAT SECTION OF SSL INSTRUCTIONS***
HERE IS THE TOMCAT 5 PATH DIR:
C:\Program Files\Brekeke\proxy\bin
STEP THREE:
Reboot Server. Then load web browser to "https://IP:8443/proxy/gate" to access SSL login for Brekeke Sip Server. [/b][/u][/code] |
|
| Back to top |
|
taitan
Brekeke Master Guru
Joined: 15 Mar 2008
Posts: 237
|
| Posted: Mon Sep 29, 2014 12:16 pm Post subject: |
|
|
KentC,
Thank you for sharing the information!. |
|
| Back to top |
|
KentC
Brekeke Guru
Joined: 09 Dec 2011
Posts: 108
Location: rw-rw-rw-
|
| Posted: Sun Oct 12, 2014 11:10 pm Post subject: |
|
|
| taitan wrote: |
KentC,
Thank you for sharing the information!. |
You're very welcome! Forgive me but I wanted to try the CentOS Linux version of this install!
Brekeke Wiki Link:
http://wiki.brekeke.com/wiki/Connect-to-the-BSS-Admintool-with-SSL
Below is the steps I've taken to make this work that has more detail then the Brekeke Wiki [Which is still an excellent guide btw] to make this work:
CentOS 5.X Linux:
Step 1.
[root@ ~]# locate keytool
/usr/java/jdk1.6.0_26/bin/keytool
/usr/java/jdk1.6.0_26/jre/bin/keytool <- Used this one over the other
Step 2.
type "/usr/java/jdk1.6.0_26/jre/bin/keytool -genkey -alias tomcat -keyalg RSA"
specify a password value as "changeit" [Use same password for certificate] [This is important step]
".keystore" file will be created by default in "/root" or "/home" directory 1st choice / 2nd choice dir path found
Type "ls -A" or "ls -A | egrep '^\.'" to find keystore file.
Step 3.
I'm using the following [apache-tomcat-7.0.30] in /usr/local
nano <brekeke_install_dir> /conf/server.xml [tomcat]
Uncomment the "SSL HTTP/1.1 Connector" entry and check what port is used for SSL in this section.
If you change the SSL port in this section to other #, please change the [redirectPort] # under " Define a non-SSL HTTP/1.1 Connector on port 8080 " to the same port
IMPORTANT:
You just copy/paste the example below and edit the redirect port to match.
For tomcat6 or later, set protocol as following sample: <- this worked for me by putting the text below inside the .conf file [copy/paste in SecureCRT]
<Connector port="8443" protocol="org.apache.coyote.http11.Http11Protocol" SSLEnabled="true" maxThreads="150" scheme="https" secure="true" clientAuth="false" sslProtocol="TLS" />
Step 4.
Restart your machine. Then open web browser to "https://brekeke_server_address:ssl_port/sip"
We now have tomcat with SSL login access on port 8443!! Super!
Kent C. |
|
| Back to top |
|
|
|
|
|
