Hello Scott,
Thank you for your reply. Here is a Syslog dump of a Repro restart.
There were no errors in the terminal it was launched in.
http://paste.debian.net/243232/
This was launched using all of the changes from here
http://www.rtcquickstart.org/sip-proxy-installation/repro except for
EnumSuffixes, which was left blank.
There is no sign of Repro in "ps aux" or "netstat --listen" from the
restart with those changes.
Regards,
mmm
On 03/20/2013 05:51 PM, Scott Godin wrote:
Are there any errors in the log file or console window
that you launched in?
Scott
On Tue, Mar 19, 2013 at 4:23 PM, Mike <mmm@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
wrote:
Dear
Resiprocate-Users,
I am setting up Resiprocate for the first time and I am
having some
difficulties configuring Repro. I followed these
instructions
http://www.rtcquickstart.org/sip-proxy-installation/repro
Repro works fine under the default settings but enabling TLS
per those
instructions breaks access to the web interface. I have
obviously tried
to access the web interface with http and https. Of the
suggested
changes, only specifying the IP address does not cause the
web interface
to break. I have tested after making all of the changes and
various
combinations thereof to try and track down the culprit to no
avail.
I have the server setup using a self signed certificate
instead of
CACert. BIND is handled on a separate server.
There are no errors being thrown by Repro (other than the
standard http
web timeout).
Kind regards,
mmm
_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/
|