Re: [OpenSER-Users] TLS problem.

Dear Klaus, Its working when I set alias=10.11.57.197! Thank you very much. BR -fengbin On 1/11/08, Klaus Darilion <[EMAIL PROTECTED]> wrote: > > Maybe this is caused by only listening to TLS socket, but not UDP/TCP. > > Workaround 1: try adding: alias=10.11.57.197 to the config > > Workaround 2:

Re: [OpenSER-Users] TLS problem.

Maybe this is caused by only listening to TLS socket, but not UDP/TCP. Workaround 1: try adding: alias=10.11.57.197 to the config Workaround 2: try what happens if you listen to other ports to: listen = udp:10.11.57.197:5060 listen = tcp:10.11.57.197:5060 listen = tls:10.11.57.197:5061 regards

Re: [OpenSER-Users] TLS problem.

you have to load the xlog module fengbin schrieb: > Dear,Klaus, > > There is an error of " not found" while I put that phrase > > > On 1/11/08, *Klaus Darilion* <[EMAIL PROTECTED] > > wrote: > > Hi Fengbin! > > Cc'ed to the openser list ... > > fengb

Re: [OpenSER-Users] TLS problem.

Dear,Klaus, There is an error of " not found" while I put that phrase On 1/11/08, Klaus Darilion <[EMAIL PROTECTED]> wrote: > > Hi Fengbin! > > Cc'ed to the openser list ... > > fengbin schrieb: > > Hi,Klaus, > > > > How to use NULL cipher? Only setting in Openser is ok? I mean do I need > > to

Re: [OpenSER-Users] TLS problem.

Hi Fengbin! Cc'ed to the openser list ... fengbin schrieb: > Hi,Klaus, > > How to use NULL cipher? Only setting in Openser is ok? I mean do I need > to set NULL cipher at client site? Usually the NULL cipher is not enabled (for security reasons). You have to enable it on both sides, the serve

Re: [OpenSER-Users] TLS problem.

Hi,Klaus Thank you for your reply. The enclosed is the config file ,the pcap between client and server and the log on the openser 's console. Could you please take a look at them for me? THX BR On 1/10/08, Klaus Darilion <[EMAIL PROTECTED]> wrote: > > Can you show us the REGISTER request? (both,

Re: [OpenSER-Users] TLS problem.

The capture file is not helpful, as it is encrypted. You could use NULL cipher to have plaintext inside the TLS connection to inspect the incoming SIP message, or add xlog("L_ERR","message buffer: $mb"); to see the whole incoming SIP request. regards klaus fengbin schrieb: > Hi,Klaus > Thank y

Re: [OpenSER-Users] TLS problem.

Hi,Christian Thank you for your reply :-) I checked the config file and found that in my config file fork is yes. My fault on pasting the configure in my last email. So it means it seem not to be related to fork. BTW,do you mean the TLS-tutorial "http://www.openser.org/docs/tls.html"; ? if not ,can

Re: [OpenSER-Users] TLS problem.

Can you show us the REGISTER request? (both, port 5060 and port 5061). Further show use your openser config regards klaus fengbin schrieb: > > Hi,all > I met a strange problem while I am testing TLS connection between > minisip and openser. > The following is my openser.cfg (part of that) > >

Re: [OpenSER-Users] TLS problem.

Hi, it is recommended to enable multi-process mode in the config-file for an adequate function of OpenSER with TLS (fork=yes). Your log shows that OpenSER is not able to open the Socket for TLS, which is, as far as I know, due to the fact that no child process could have been started for that

[OpenSER-Users] TLS problem.

Hi,all I met a strange problem while I am testing TLS connection between minisip and openser. The following is my openser.cfg (part of that) . fork=no log_stderror=yes # Uncomment this to prevent the blacklisting of temporary not available destinations #disable_dns_blacklist=yes # # Unco