I hope I'm not just completely lost, but the symptoms seem to indicate
some sort of SSL distribution problem.
Using ps I see the following command lines:
/bin/sh /usr/local/src/yxa/build/incomingproxy -d -c_ssl
/usr/local/etc/cert.comb -s_ssl /usr/local/etc/cert.comb
/usr/local/lib/erlang/erts-
Peter Krnjevic wrote:
> I hope I'm not just completely lost, but the symptoms seem to indicate
> some sort of SSL distribution problem.
> Using ps I see the following command lines:
>
>
>
FYI - if Fredrik doesn't answer emails for a little while its
because he just became a father. This is a pe
Hi List,
We are trying to connect many SIP UAs through a SIP proxy to a Tekelec
switch. The tricky part is that the Tekelec provides a VPRI service that
expects either a UA or SBC and the SIP dialog with a proxy is somewhat
different. The first and likely not the only differnce is that UAs don'
Hmm, looks like I've done something with my SSL keys though whatever I
try doens't seem to make a difference. I'm particularly puzzled because
it was sort of working yesterday.
-Peter
___
Yxa-devel mailing list
Yxa-devel@lists.su.se
https://lists.su.se
Oops, the first few lines on startup (missing from last post) are:
2007-09-11 17:22:26.300 normal<0.167.0>:NOT starting tls listener on
port 5061, no SSL server certificate specified (see README)
2007-09-11 17:22:26.301 normal<0.167.0>:NOT starting tls listener on
port 5061, no SSL server certif
Googling shows others having problems with SSL distribution, though I
don't know enough yet to know if the causes are the same.
In the meantime, since both Yxa and Yaws are running on the same server,
simply disabling SSL did the trick.
Long-term though, I need to find a solution so if you have a
