[Users] I cannot login

[Daniel-Constantin Mierla]

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.
>>>
>>>
>>>
>>> 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 at vpbx2.elmit.com -a test000
>>> -s sip:800000 at vpbx2.elmit.com:5062 -Hvpbx2.elmit.com -vv
>>>
>>> New message with Via-Line:
>>> OPTIONS sip:800000 at vpbx2.elmit.com:5062 SIP/2.0
>>> Via: SIP/2.0/UDP vpbx2.elmit.com:3763;rport
>>> From: <sip:sipsak at vpbx2.elmit.com:3763>
>>> To: <sip:800000 at vpbx2.elmit.com:5062>
>>> Call-ID: 646310771 at vpbx2.elmit.com
>>> CSeq: 1 OPTIONS
>>> Contact: <sip:sipsak at vpbx2.elmit.com:3763>
>>> Content-Length: 0
>>> Max-Forwards: 70
>>> User-Agent: sipsak 0.8.9_pre
>>> Accept: text/plain
>>>
>>>
>>> ** request **
>>> OPTIONS sip:800000 at vpbx2.elmit.com:5062 SIP/2.0
>>> Via: SIP/2.0/UDP vpbx2.elmit.com:3763;rport
>>> From: <sip:sipsak at vpbx2.elmit.com:3763>
>>> To: <sip:800000 at vpbx2.elmit.com:5062>
>>> Call-ID: 646310771 at vpbx2.elmit.com
>>> CSeq: 1 OPTIONS
>>> Contact: <sip:sipsak at 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
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>>
>
>