"The Call Resolver establishes SSL connections to these databases and resolves the call state events into a single CDR database on the Master Server."
Whether it can go back in time and sync records when it comes back on-line I'm not sure... From: Vikas Sharma [mailto:[EMAIL PROTECTED] Sent: Monday, October 13, 2008 6:34 AM To: Picher, Michael Cc: sipxusers Subject: Re: [sipx-users] CSE on dist-server in high availability hi but i got a document in which some call-resolver settings are given. but dint work for me. i am pasting that below Call Resolver High Availability (HA) setup In an HA environment, call state event logging to a database is done by proxies running on separate machines, with the Call Resolver located on the Master Server. The Call Resolver establishes SSL connections to these databases and resolves the call state events into a single CDR database on the Master Server. There are a number of configuration steps that must be performed before the Call Resolver can operate on distributed databases. The first step is to follow all of the instructions given in the 'High Availability Setup Guide'. Most important for the subsequent Call Resolver configuration is the creation and installation of SSL certificates on the Master Server and the Distributed Server. The name of the Certificate Authority file (caname.crt in the High Availability Setup Guide) is one of the configuration parameters needed by the Call Resolver. Call Resolver setup on the Master Server Two configuration parameters in /etc/sipxpbx/callresolver-config.in have to be added to enable the Call Resolver to establish SSL connections to distributed databases : SIP_CALLRESOLVER_CSE_HOSTS : {comma-delimited list of host names and port numbers} SIP_CALLRESOLVER_CSE_CA : {name of the Certificate authority file caname.crt} The Call Resolver uses stunnel to establish SSL connections to remote databases. Stunnel is an SSL-encrypting socket wrapper that provides SSL support to applications by forwarding connections on local ports to another instance of stunnel running on a remote machine. 'localhost' must be specified as part of the list of host names if a CSE database is running on the local machine, otherwise the Call Resolver will not connect to the local CSE database. If no port is specified it will default to the standard PostgreSQL port 5432. The following example has the Call Resolver running on the Master Server master.example.com and the Distributed Server running on distrib.example.com. The Call Resolver will connect to the database on the Distributed Server on port 5433. The name of the Certificate Authority file is 'ca.example.com.crt'. SIP_CALLRESOLVER_CSE_HOSTS : localhost, distrib.example.com:5433 SIP_CALLRESOLVER_CSE_CA : ca.example.com.crt More than one Distributed Server can be specified. SIP_CALLRESOLVER_CSE_HOSTS : localhost, distrib1.example.com:5433, distrib2.example.com:5434 SIP_CALLRESOLVER_CSE_CA : ca.example.com.crt Note that the ports specified can be any unused ports on the Master Server. The local PostgreSQL database is using its default port 5432, so 5433 and 5434 are unused but 'PostgreSQL-like' ports). The specified ports do not describe any real connections to distributed systems, they are only used for forwarding local connections on these ports to the distributed machines. The port numbers must be unique, no two host names can have the same port number. Distributed Server setup Because the web UI can only configure proxies on the Master Server the configuration files on the Distributed server need to be edited manually. To enable call state event logging manually edit the file /etc/sipxpbx/sipXproxy-config.in to include the line SIPX_PROXY_CALL_STATE_DB : ${CALLRESOLVER_CALL_STATE_DB} in order to enable call state logging to the database. Since the Call Resolver is not running on the Distributed Server there is no need to configure it. The Distributed Server still must be configured to accept SSL connections from the Call Resolver running on the Master Server to allow the Call Resolver to retrieve call state events. The following example uses the Certificate Authority file 'ca.example.com.crt' to set up the Distributed Server. As root from the command line enter the command sipxha-distrib.sh --setup ca.example.com.crt and the Distributed Server should be set up to accept SSL connections to its database. --------------------------- more over i dint get sipxha-distrib.sh file. if i add two given lines in this file /etc/sipxpbx/callresolver-config.in of master server. call-resolver fails everytime. One more thing, can anyone give me a example zone(dns) file for master and dist-server. I am not able to configure DNS in write way. How the named.conf of both machines looks alike? please help. Thnax On Mon, Oct 13, 2008 at 3:54 PM, Picher, Michael <[EMAIL PROTECTED]> wrote: I think you lose CDR if in failover. Same with Media Services (no Auto Attendant / VoiceMail). Mike From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Vikas Sharma Sent: Friday, October 10, 2008 7:37 AM To: sipxusers Subject: [sipx-users] CSE on dist-server in high availability hi all i have implemented high availability in sipx 3.10.2. Call is routed through the dist-server if master is unavailable. Every thing is fine now as i want. Now there is no data base in dist-server i think. not even cse. If master is unavailable, calling is through dist-server where the calls details are? How it is added in final cdr on master when master become available? What necessary setting / installations do i require now (on both server)? Do i require to install cse/cdrs (database) on dist-server? if yes, how it is installed? please help me out thanx -- vikas sharma -- vikas sharma
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
