[Users] I cannot login

List overview All Threads
Download

newer

older

[Serusers] problems compiling

[Serusers] RE: PAID SUPPORT...

Ronald Wiplinger

20 Oct 2005 20 Oct '05

9:16 a.m.

I tried sipsak: C:\Documents and Settings\user\My Documents\sipsak>sipsak-0.8.8.exe -U -C sip:80 0000(a)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(a)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(a)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(a)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(a)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(a)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(a)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

Show replies by date

Bogdan-Andrei Iancu

20 Oct 20 Oct

11:59 a.m.

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. regards, bogdan Ronald Wiplinger wrote:

...

Ronald Wiplinger

1:06 p.m.

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:

-- Ronald Wiplinger (CEO of ELMIT) http://www.elmit.com http://voip.elmit.com http://e-paper.elmit.com Tel. (M) +886.939.775.516 (O) +886.2.2835.7765 (ENUM) or FWD 511208 - I'm a SpamCon Foundation Member, #694, Verify it at http://www.spamcon.org PS: Spam prevention! Our system is protected with a spam prevention program. If you send us an e-mail, our system will send you a confirmation message back. Just reply to this confirmation message please. After receiving this confirmation message, our system will send the hold message (one) and all future messages (after the received confirmation message) to me without asking you again.

Bogdan-Andrei Iancu

3:19 p.m.

Hi, this is rather strange - can you post the error messages generated by openser at startup?? (see syslog) 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.

Ronald Wiplinger

5:44 p.m.

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.

Daniel-Constantin Mierla

21 Oct 21 Oct

12:59 p.m.

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 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)

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.

Ronald Wiplinger

1:17 p.m.

Daniel-Constantin Mierla wrote:

...

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)

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

1:36 p.m.

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

...

Daniel-Constantin Mierla wrote:

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.

...

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)

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 >

Ronald Wiplinger

2:10 p.m.

Daniel-Constantin Mierla wrote:

...

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

Daniel-Constantin Mierla wrote:

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(a)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(a)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?

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

9:42 p.m.

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. 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:

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.

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 >>> >> >> >> > >

Ronald Wiplinger

11:30 p.m.

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.

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

22 Oct 22 Oct

1:16 p.m.

On 10/21/05 22:30, Ronald Wiplinger wrote:

...

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.

then watch the network traffic (using ngrep or ethereal) to see where the sip messages are going. Cheers, Daniel

...

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.

> > 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 >>>>> >>>> >>>> >>>> >>> >>> >> >> >> > >

6958

days inactive

6960

days old

sr-users@lists.kamailio.org

Manage subscription

11 comments

3 participants

tags (0)

participants (3)

Bogdan-Andrei Iancu
Daniel-Constantin Mierla
Ronald Wiplinger