Bogdan-Andrei Iancu wrote:

Hi Ronald,

to find why your authentication fails, run openser in debug mode (debug=7) and look into the logs for hints. If you have doubts, just post the log.

Hi,

with:

debug=7 # debug level (cmd line: -dddddddddd) #fork=yes #log_stderror=no # (cmd line: -E)

/* Uncomment these lines to enter debugging mode */ fork=no log_stderror=yes /* */

in openser.cfg openser does not start at all. The picture shows:

vpbx2:/usr/local/etc/openser # openserctl start

Starting OpenSER :

Thanks for your help!

bye

Ronald Wiplinger

regards, bogdan

Ronald Wiplinger wrote:

...

I tried sipsak:

C:\Documents and Settings\user\My Documents\sipsak>sipsak-0.8.8.exe -U -C sip:80 0000@vpbx.elmit.com -a rest000 -s sip:800000@vpbx.elmit.com:5062 -Hvpbx.elmit.com warning: redirects are not expected in USRLOC. disableing

request: REGISTER sip:vpbx.elmit.com:5062 SIP/2.0 Authorization: Digest username="800000", uri="sip:vpbx.elmit.com:5062", algorith m=MD5, realm="vpbx.elmit.com", nonce="435724cfa071bd7b4ef9bd25c01b4c5dc020aca3", response="62e960c0de81fa17af1e53a78156bb78" Via: SIP/2.0/UDP vpbx.elmit.com:3652;rport From: sip:800000@vpbx.elmit.com:5062 To: sip:800000@vpbx.elmit.com:5062 Call-ID: 1856953657@vpbx.elmit.com CSeq: 2 REGISTER Contact: sip:800000@vpbx.elmit.com Expires: 15 Content-Length: 0 Max-Forwards: 70 User-Agent: sipsak 0.8.9_pre

response: SIP/2.0 401 Unauthorized Via: SIP/2.0/UDP vpbx.elmit.com:3652;rport=3652;received=192.168.250.108 From: sip:800000@vpbx.elmit.com:5062 To: sip:800000@vpbx.elmit.com:5062;tag=2560d490c3265ff35995c6bbde62a7c3.9f22

Call-ID: 1856953657@vpbx.elmit.com CSeq: 2 REGISTER WWW-Authenticate: Digest realm="vpbx.elmit.com", nonce="435724cfa071bd7b4ef9bd25 c01b4c5dc020aca3" Server: OpenSer (1.0.0-pre0 (x86_64/linux)) Content-Length: 0 Warning: 392 192.168.250.20:5062 "Noisy feedback tells: pid=22704 req_src_ip=19 2.168.250.108 req_src_port=3652 in_uri=sip:vpbx.elmit.com:5062 out_uri=sip:vpbx. elmit.com:5062 via_cnt==1"

error: authorization failed request already contains (Proxy-) Authorization, but received 40[1|7], see above

Another try without -U but with -vv

C:\Documents and Settings\user\My Documents\sipsak>sipsak-0.8.8.exe -C sip:80000 0@vpbx.elmit.com -a rest000 -s sip:800000@vpbx.elmit.com:5062 -Hvpbx.elmit.com - vv New message with Via-Line: OPTIONS sip:800000@vpbx.elmit.com:5062 SIP/2.0 Via: SIP/2.0/UDP vpbx.elmit.com:3731;rport From: sip:sipsak@vpbx.elmit.com:3731 To: sip:800000@vpbx.elmit.com:5062 Call-ID: 763778098@vpbx.elmit.com CSeq: 1 OPTIONS Contact: sip:sipsak@vpbx.elmit.com:3731 Content-Length: 0 Max-Forwards: 70 User-Agent: sipsak 0.8.9_pre Accept: text/plain

** request ** OPTIONS sip:800000@vpbx.elmit.com:5062 SIP/2.0 Via: SIP/2.0/UDP vpbx.elmit.com:3731;rport From: sip:sipsak@vpbx.elmit.com:3731 To: sip:800000@vpbx.elmit.com:5062 Call-ID: 763778098@vpbx.elmit.com CSeq: 1 OPTIONS Contact: sip:sipsak@vpbx.elmit.com:3731 Content-Length: 0 Max-Forwards: 70 User-Agent: sipsak 0.8.9_pre Accept: text/plain

message received: SIP/2.0 404 Not Found Via: SIP/2.0/UDP vpbx.elmit.com:3731;rport=3731;received=192.168.250.108 From: sip:sipsak@vpbx.elmit.com:3731 To: sip:800000@vpbx.elmit.com:5062;tag=2560d490c3265ff35995c6bbde62a7c3.e6e1

Call-ID: 763778098@vpbx.elmit.com CSeq: 1 OPTIONS Server: OpenSer (1.0.0-pre0 (x86_64/linux)) Content-Length: 0 Warning: 392 192.168.250.20:5062 "Noisy feedback tells: pid=22702 req_src_ip=19 2.168.250.108 req_src_port=3731 in_uri=sip:800000@vpbx.elmit.com:5062 out_uri=si p:800000@vpbx.elmit.com:5062 via_cnt==1"

** reply received after 11.000 ms ** SIP/2.0 404 Not Found final received

C:\Documents and Settings\user\My Documents\sipsak>

Any ideas?

bye

Ronald Wiplinger

---

Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users

Bogdan-Andrei Iancu wrote:

Hi,

this is rather strange - can you post the error messages generated by openser at startup?? (see syslog)

With debug it DOES NOT START, no messages in /var/log/messages It hangs at the line: Starting OpenSER :

Without debug the only message during startup is: Oct 20 21:41:00 vpbx /usr/local/sbin/openser[3882]: Maxfwd module- initializing

bye

Ronald Wiplinger

regards, bogdan

Ronald Wiplinger wrote:

...

Bogdan-Andrei Iancu wrote:

...

Hi Ronald,

to find why your authentication fails, run openser in debug mode (debug=7) and look into the logs for hints. If you have doubts, just post the log.

Hi,

with:

debug=7 # debug level (cmd line: -dddddddddd) #fork=yes #log_stderror=no # (cmd line: -E)

/* Uncomment these lines to enter debugging mode */ fork=no log_stderror=yes /* */

in openser.cfg openser does not start at all. The picture shows:

vpbx2:/usr/local/etc/openser # openserctl start

Starting OpenSER :

Thanks for your help!

bye

Ronald Wiplinger

Daniel-Constantin Mierla wrote:

Hello Ronald,

please use the init.d script to start/stop openser. You can find it in packaging subdirectory, there are directories for different distributions and inside of some is a file named openser.init.

Otherwise try starting it from command line: /usr/local/sbin/openser -f /usr/local/etc/openser/openser.cfg

I used openserctl start and it seems it is different. With your line above I could start openser in debug mode, however, there is still no log file about it.

During startup and shutdown many lines flashed through the screen, as well during CTRL C to stop it. While I try to use sipsak, there was no extra line on the screen either.

I use SuSE, which init script should I use?

bye

Ronald Wiplinger

Cheers, Daniel

On 10/20/05 16:44, Ronald Wiplinger wrote:

...

Bogdan-Andrei Iancu wrote:

...

Hi,

this is rather strange - can you post the error messages generated by openser at startup?? (see syslog)

With debug it DOES NOT START, no messages in /var/log/messages It hangs at the line: Starting OpenSER :

Without debug the only message during startup is: Oct 20 21:41:00 vpbx /usr/local/sbin/openser[3882]: Maxfwd module- initializing

bye

Ronald Wiplinger

...

regards, bogdan

Ronald Wiplinger wrote:

...

Bogdan-Andrei Iancu wrote:

...

Hi Ronald,

to find why your authentication fails, run openser in debug mode (debug=7) and look into the logs for hints. If you have doubts, just post the log.

Hi,

with:

debug=7 # debug level (cmd line: -dddddddddd) #fork=yes #log_stderror=no # (cmd line: -E)

/* Uncomment these lines to enter debugging mode */ fork=no log_stderror=yes /* */

in openser.cfg openser does not start at all. The picture shows:

vpbx2:/usr/local/etc/openser # openserctl start

Starting OpenSER :

Thanks for your help!

bye

Ronald Wiplinger

Daniel-Constantin Mierla wrote:

On 10/21/05 12:17, Ronald Wiplinger wrote:

...

Daniel-Constantin Mierla wrote:

...

Hello Ronald,

please use the init.d script to start/stop openser. You can find it in packaging subdirectory, there are directories for different distributions and inside of some is a file named openser.init.

Otherwise try starting it from command line: /usr/local/sbin/openser -f /usr/local/etc/openser/openser.cfg

I used openserctl start and it seems it is different. With your line above I could start openser in debug mode, however, there is still no log file about it.

During startup and shutdown many lines flashed through the screen, as well during CTRL C to stop it. While I try to use sipsak, there was no extra line on the screen either.

Add log_stderror=yes in the configuration script and you should get all the debug messages on the screen. Then watch when you send the sip messages with sipsak.

It has this line, ... In sipsak I get now the error:

C:\Documents and Settings\user\My Documents\sipsak>sipsak-0.8.8.exe -C sip:800000@vpbx2.elmit.com -a test000 -s sip:800000@vpbx2.elmit.com:5062 -Hvpbx2.elmit.com -vv

New message with Via-Line: OPTIONS sip:800000@vpbx2.elmit.com:5062 SIP/2.0 Via: SIP/2.0/UDP vpbx2.elmit.com:3763;rport From: sip:sipsak@vpbx2.elmit.com:3763 To: sip:800000@vpbx2.elmit.com:5062 Call-ID: 646310771@vpbx2.elmit.com CSeq: 1 OPTIONS Contact: sip:sipsak@vpbx2.elmit.com:3763 Content-Length: 0 Max-Forwards: 70 User-Agent: sipsak 0.8.9_pre Accept: text/plain

** request ** OPTIONS sip:800000@vpbx2.elmit.com:5062 SIP/2.0 Via: SIP/2.0/UDP vpbx2.elmit.com:3763;rport From: sip:sipsak@vpbx2.elmit.com:3763 To: sip:800000@vpbx2.elmit.com:5062 Call-ID: 646310771@vpbx2.elmit.com CSeq: 1 OPTIONS Contact: sip:sipsak@vpbx2.elmit.com:3763 Content-Length: 0 Max-Forwards: 70 User-Agent: sipsak 0.8.9_pre Accept: text/plain

message received: socket error: Connection reset by peer

bye

Ronald Wiplinger

...

I use SuSE, which init script should I use?

You have to use "packaging/rpm/openser.init.SuSE" - copy it in /etc/init.d and you can use it all the time from there. Since I am not using suse, I hope you do not have anything to change inside the file (e.g., paths or names).

Cheers, Daniel

...

bye

Ronald Wiplinger

...

Cheers, Daniel

On 10/20/05 16:44, Ronald Wiplinger wrote:

...

Bogdan-Andrei Iancu wrote:

...

Hi,

this is rather strange - can you post the error messages generated by openser at startup?? (see syslog)

With debug it DOES NOT START, no messages in /var/log/messages It hangs at the line: Starting OpenSER :

Without debug the only message during startup is: Oct 20 21:41:00 vpbx /usr/local/sbin/openser[3882]: Maxfwd module- initializing

bye

Ronald Wiplinger

...

regards, bogdan

Ronald Wiplinger wrote:

...

Bogdan-Andrei Iancu wrote:

> Hi Ronald, > > to find why your authentication fails, run openser in debug mode > (debug=7) and look into the logs for hints. If you have doubts, > just post the log. >

Hi,

with:

debug=7 # debug level (cmd line: -dddddddddd) #fork=yes #log_stderror=no # (cmd line: -E)

/* Uncomment these lines to enter debugging mode */ fork=no log_stderror=yes /* */

in openser.cfg openser does not start at all. The picture shows:

vpbx2:/usr/local/etc/openser # openserctl start

Starting OpenSER :

Thanks for your help!

bye

Ronald Wiplinger

Daniel-Constantin Mierla wrote:

Please post the debug messages from openser, those are relevant for your problem. I do not know what is the error handling and meaning in sipsak.

That is the point, there is no message, ... it seems that these two are not talking to each other.

bye

Ronald Wiplinger

Cheers, Daniel

On 10/21/05 13:10, Ronald Wiplinger wrote:

...

Daniel-Constantin Mierla wrote:

...

On 10/21/05 12:17, Ronald Wiplinger wrote:

...

Daniel-Constantin Mierla wrote:

...

Hello Ronald,

please use the init.d script to start/stop openser. You can find it in packaging subdirectory, there are directories for different distributions and inside of some is a file named openser.init.

Otherwise try starting it from command line: /usr/local/sbin/openser -f /usr/local/etc/openser/openser.cfg

I used openserctl start and it seems it is different. With your line above I could start openser in debug mode, however, there is still no log file about it.

During startup and shutdown many lines flashed through the screen, as well during CTRL C to stop it. While I try to use sipsak, there was no extra line on the screen either.

Add log_stderror=yes in the configuration script and you should get all the debug messages on the screen. Then watch when you send the sip messages with sipsak.

It has this line, ... In sipsak I get now the error:

C:\Documents and Settings\user\My Documents\sipsak>sipsak-0.8.8.exe -C sip:800000@vpbx2.elmit.com -a test000 -s sip:800000@vpbx2.elmit.com:5062 -Hvpbx2.elmit.com -vv

New message with Via-Line: OPTIONS sip:800000@vpbx2.elmit.com:5062 SIP/2.0 Via: SIP/2.0/UDP vpbx2.elmit.com:3763;rport From: sip:sipsak@vpbx2.elmit.com:3763 To: sip:800000@vpbx2.elmit.com:5062 Call-ID: 646310771@vpbx2.elmit.com CSeq: 1 OPTIONS Contact: sip:sipsak@vpbx2.elmit.com:3763 Content-Length: 0 Max-Forwards: 70 User-Agent: sipsak 0.8.9_pre Accept: text/plain

** request ** OPTIONS sip:800000@vpbx2.elmit.com:5062 SIP/2.0 Via: SIP/2.0/UDP vpbx2.elmit.com:3763;rport From: sip:sipsak@vpbx2.elmit.com:3763 To: sip:800000@vpbx2.elmit.com:5062 Call-ID: 646310771@vpbx2.elmit.com CSeq: 1 OPTIONS Contact: sip:sipsak@vpbx2.elmit.com:3763 Content-Length: 0 Max-Forwards: 70 User-Agent: sipsak 0.8.9_pre Accept: text/plain

message received: socket error: Connection reset by peer

bye

Ronald Wiplinger

...

...

I use SuSE, which init script should I use?

You have to use "packaging/rpm/openser.init.SuSE" - copy it in /etc/init.d and you can use it all the time from there. Since I am not using suse, I hope you do not have anything to change inside the file (e.g., paths or names).

Cheers, Daniel

...

bye

Ronald Wiplinger

...

Cheers, Daniel

On 10/20/05 16:44, Ronald Wiplinger wrote:

...

Bogdan-Andrei Iancu wrote:

> Hi, > > this is rather strange - can you post the error messages > generated by openser at startup?? (see syslog)

With debug it DOES NOT START, no messages in /var/log/messages It hangs at the line: Starting OpenSER :

Without debug the only message during startup is: Oct 20 21:41:00 vpbx /usr/local/sbin/openser[3882]: Maxfwd module- initializing

bye

Ronald Wiplinger

> regards, > bogdan > > Ronald Wiplinger wrote: > >> Bogdan-Andrei Iancu wrote: >> >>> Hi Ronald, >>> >>> to find why your authentication fails, run openser in debug >>> mode (debug=7) and look into the logs for hints. If you have >>> doubts, just post the log. >>> >> >> Hi, >> >> with: >> >> debug=7 # debug level (cmd line: -dddddddddd) >> #fork=yes >> #log_stderror=no # (cmd line: -E) >> >> /* Uncomment these lines to enter debugging mode */ >> fork=no >> log_stderror=yes >> /* */ >> >> in openser.cfg openser does not start at all. >> The picture shows: >> >> vpbx2:/usr/local/etc/openser # openserctl start >> >> Starting OpenSER : >> >> >> Thanks for your help! >> >> >> bye >> >> Ronald Wiplinger >> > > >