[Users] Problem with openser.cfg

[Klaus Darilion]

li gh wrote:
> Thank you!
> The local user is 1001 at proxy1 <mailto:1001 at proxy1>, calling 
> sip:2001 at proxy2,
> so the SIP signaling should be relayed to proxy2 by proxy1,
> but I cannot capture any SIP packet from proxy1 to proxy2.

Put log statements into openser.cfg and watch them in syslog. This will 
give you details what is going wrong. make sure proxy1 is able to 
resolve "proxy2" to the corresponding IP address (DNS).

> When I call another user also registered to proxy1
> (e.g. sip:1004 at proxy1), there is no problem.
> 
> How to "start it manually" ? Just type "openser stop" then "openser start"?
> Or by other ways? I have no idea.

just "openser" as root will start openser. Then you can use "ps 
-Alf|grep openser" to find out the PID of the openser processes. To stop 
openser manually, find the lowest PID and kill openser with "kill PID" 
(replace PID with the value)

regards
klaus


>  
> Thank you very much!
> Best regards.
>  
> On 4/24/06, *Klaus Darilion* <klaus.mailinglists at pernau.at 
> <mailto:klaus.mailinglists at pernau.at>> wrote:
> 
>     How do you call? sip:2001 at proxy2 ? or sip:2001 at proxy1?
> 
>     Use "ngrep port 5060" to debug SIP signaling
> 
>     You have to start it manually (no startup scripts).
> 
>     Better set log_stderror to "no" and watch the log messages in syslog.
> 
>     e.g. on debian syslog is senet to /var/log/messages. Some Linus
>     distributions use other file names but it should be easily to figure
>     that out:
> 
>     tail -f /var/log/messages
> 
>     regards
>     klaus
> 
>