Up to Discussions in OpenSBC

This Question is Answered

1 "correct" answer available (4 pts) 2 "helpful" answers available (2 pts)
3 Replies Last post: Feb 14, 2008 5:02 AM by tyv  
Click to view tyv's profile  
tyv
3 posts since
Feb 5, 2008

Feb 5, 2008 3:24 AM

OpeтSBC ceases to work

Good day!

OpeSBC it is configured and correctly works in b2bUpperReg Mode. But there is a serious problem, which reason for me is not known. At a plenty of requests REGISTER (for example at input wrong password in UA) OpenSBC ceases to work - any more does not write messages to log, answers from OpenSBC no more send. EventQueue reaches nearby 150-200. Process does not take off. I restart process, but the problem repeats. The more requests to OpenSBC, than the more quickly OpenSBC will break.

How to solve this problem?

#uname -a
Linux classV 2.6.18-8.el5 #1 SMP Fri Jan 26 14:15:21 EST 2007 i686 i686 i386 GNU/Linu

Last messages in log:
333925:23:34.062 INF: CID=0x0e6f *** UPPER REGISTRATION ENABLE *** for sip:6563630554@192.168.1.105
333925:23:34.079 INF: CID=0x0e6f Event: Setting UA Core Proxy to handle event REGISTER
333925:23:34.299 INF: CID=0x0e6f Event: Setting UA Core Proxy to handle event REGISTER
333925:23:34.299 INF: CID=0x0e6f Session CREATED
333925:23:34.299 INF: CID=0x0e6f *** CREATED *** PROXY Session MDZmNDAwNDI1NDEyYmYzNDc5MDhlMjZmYmE1OWJhZDk.
333925:23:34.304 INF: CID=0x0e6f Routing REGISTER for URI sip:6563630554@192.168.1.105
333925:23:34.305 PWL: CID=0x0000 -->> From: sip:6563630554@192.168.1.105 Target: REGISTER sip:6563630554@192.168.1.105:5060
333925:23:34.305 INF: CID=0x0e6f *** UPPER REGISTRATION ENABLE *** for sip:6563630554@192.168.1.105
333925:23:34.970 INF: CID=0x0e6f Event: Setting UA Core Proxy to handle event REGISTER
333925:23:34.975 INF: CID=0x0e6f *** DESTROYED *** PROXY Session MDZmNDAwNDI1NDEyYmYzNDc5MDhlMjZmYmE1OWJhZDk.
333925:23:34.976 INF: CID=0x0e6f PROXY: Session DESTROYED
333925:23:34.977 INF: CID=0x0e6f *** DESTROYED *** PROXY Session MDZmNDAwNDI1NDEyYmYzNDc5MDhlMjZmYmE1OWJhZDk.
333925:23:34.977 INF: CID=0x0e6f PROXY: Session DESTROYED
333925:23:35.194 INF: CID=0x0e6f Event: Setting UA Core Proxy to handle event REGISTER
333925:23:35.194 INF: CID=0x0e6f Session CREATED
333925:23:35.194 INF: CID=0x0e6f *** CREATED *** PROXY Session MDZmNDAwNDI1NDEyYmYzNDc5MDhlMjZmYmE1OWJhZDk.
333925:23:35.198 INF: CID=0x0e6f Routing REGISTER for URI sip:6563630554@192.168.1.105
333925:23:35.198 PWL: CID=0x0000 -->> From: sip:6563630554@192.168.1.105 Target: REGISTER sip:6563630554@192.168.1.105:5060
333925:23:35.199 INF: CID=0x0e6f *** UPPER REGISTRATION ENABLE *** for sip:6563630554@192.168.1.105
333925:23:35.220 INF: CID=0x0e6f Event: Setting UA Core Proxy to handle event REGISTER
333925:23:35.439 INF: CID=0x0e6f Event: Setting UA Core Proxy to handle event REGISTER
333925:23:35.440 INF: CID=0x0e6f Session CREATED
333925:23:35.440 INF: CID=0x0e6f *** CREATED *** PROXY Session MDZmNDAwNDI1NDEyYmYzNDc5MDhlMjZmYmE1OWJhZDk.
333925:23:35.444 INF: CID=0x0e6f Routing REGISTER for URI sip:6563630554@192.168.1.105
333925:23:35.444 PWL: CID=0x0000 -->> From: sip:6563630554@192.168.1.105 Target: REGISTER sip:6563630554@192.168.1.105:5060
333925:23:35.445 INF: CID=0x0e6f *** UPPER REGISTRATION ENABLE *** for sip:6563630554@192.168.1.105
333925:23:35.463 INF: CID=0x0e6f Event: Setting UA Core Proxy to handle event REGISTER
333925:23:35.467 INF: CID=0x0e6f *** DESTROYED *** PROXY Session MDZmNDAwNDI1NDEyYmYzNDc5MDhlMjZmYmE1OWJhZDk.
333925:23:35.467 INF: CID=0x0e6f PROXY: Session DESTROYED
333925:23:35.468 INF: CID=0x0e6f *** DESTROYED *** PROXY Session MDZmNDAwNDI1NDEyYmYzNDc5MDhlMjZmYmE1OWJhZDk.
333925:23:35.468 INF: CID=0x0e6f PROXY: Session DESTROYED
333925:23:35.682 INF: CID=0x0e6f Event: Setting UA Core Proxy to handle event REGISTER
333925:23:35.683 INF: CID=0x0e6f Session CREATED
333925:23:35.683 INF: CID=0x0e6f *** CREATED *** PROXY Session MDZmNDAwNDI1NDEyYmYzNDc5MDhlMjZmYmE1OWJhZDk.
333925:23:35.691 INF: CID=0x0e6f Routing REGISTER for URI sip:6563630554@192.168.1.105
333925:23:35.692 PWL: CID=0x0000 -->> From: sip:6563630554@192.168.1.105 Target: REGISTER sip:6563630554@192.168.1.105:5060
333925:23:35.692 INF: CID=0x0e6f *** UPPER REGISTRATION ENABLE *** for sip:6563630554@192.168.1.105
333925:23:35.694 INF: CID=0x0e66 Event: Setting UA Core Proxy to handle event REGISTER
333925:23:35.695 INF: CID=0x0e66 Session CREATED
333925:23:35.696 INF: CID=0x0e66 *** CREATED *** PROXY Session MjliMjEwMGU3ZmM3YTQ3MTJiOGJlZGY0MjYzZDdkOTA.

Best regards,
Yuriy.
Guest
Guest
1. Feb 5, 2008 6:34 AM in response to: tyv
Re: [OpenSBC] OpeтSBC ceases to work
Hi Yuriy,

There have been recent patches in CVS that concerned a deadlock between
register authentication and the mutex guarding the Local Domain Accounts
items. If your problem still persists, feel free to send me the logs
at joegen@opensipstack.org so I can take a look.

Joegen

Yuriy wrote:
Good day!

OpeSBC it is configured and correctly works in b2bUpperReg Mode. But there is a serious problem, which reason for me is not known. At a plenty of requests REGISTER (for example at input wrong password in UA) OpenSBC ceases to work - any more does not write messages to log, answers from OpenSBC no more send. EventQueue reaches nearby 150-200. Process does not take off. I restart process, but the problem repeats. The more requests to OpenSBC, than the more quickly OpenSBC will break.

How to solve this problem?

#uname -a
Linux classV 2.6.18-8.el5 #1 SMP Fri Jan 26 14:15:21 EST 2007 i686 i686 i386 GNU/Linu

Last messages in log:
333925:23:34.062 INF: CID=0x0e6f *** UPPER REGISTRATION ENABLE *** for sip:6563630554@192.168.1.105
333925:23:34.079 INF: CID=0x0e6f Event: Setting UA Core Proxy to handle event REGISTER
333925:23:34.299 INF: CID=0x0e6f Event: Setting UA Core Proxy to handle event REGISTER
333925:23:34.299 INF: CID=0x0e6f Session CREATED
333925:23:34.299 INF: CID=0x0e6f *** CREATED *** PROXY Session MDZmNDAwNDI1NDEyYmYzNDc5MDhlMjZmYmE1OWJhZDk.
333925:23:34.304 INF: CID=0x0e6f Routing REGISTER for URI sip:6563630554@192.168.1.105
333925:23:34.305 PWL: CID=0x0000 -->> From: sip:6563630554@192.168.1.105 Target: REGISTER sip:6563630554@192.168.1.105:5060
333925:23:34.305 INF: CID=0x0e6f *** UPPER REGISTRATION ENABLE *** for sip:6563630554@192.168.1.105
333925:23:34.970 INF: CID=0x0e6f Event: Setting UA Core Proxy to handle event REGISTER
333925:23:34.975 INF: CID=0x0e6f *** DESTROYED *** PROXY Session MDZmNDAwNDI1NDEyYmYzNDc5MDhlMjZmYmE1OWJhZDk.
333925:23:34.976 INF: CID=0x0e6f PROXY: Session DESTROYED
333925:23:34.977 INF: CID=0x0e6f *** DESTROYED *** PROXY Session MDZmNDAwNDI1NDEyYmYzNDc5MDhlMjZmYmE1OWJhZDk.
333925:23:34.977 INF: CID=0x0e6f PROXY: Session DESTROYED
333925:23:35.194 INF: CID=0x0e6f Event: Setting UA Core Proxy to handle event REGISTER
333925:23:35.194 INF: CID=0x0e6f Session CREATED
333925:23:35.194 INF: CID=0x0e6f *** CREATED *** PROXY Session MDZmNDAwNDI1NDEyYmYzNDc5MDhlMjZmYmE1OWJhZDk.
333925:23:35.198 INF: CID=0x0e6f Routing REGISTER for URI sip:6563630554@192.168.1.105
333925:23:35.198 PWL: CID=0x0000 -->> From: sip:6563630554@192.168.1.105 Target: REGISTER sip:6563630554@192.168.1.105:5060
333925:23:35.199 INF: CID=0x0e6f *** UPPER REGISTRATION ENABLE *** for sip:6563630554@192.168.1.105
333925:23:35.220 INF: CID=0x0e6f Event: Setting UA Core Proxy to handle event REGISTER
333925:23:35.439 INF: CID=0x0e6f Event: Setting UA Core Proxy to handle event REGISTER
333925:23:35.440 INF: CID=0x0e6f Session CREATED
333925:23:35.440 INF: CID=0x0e6f *** CREATED *** PROXY Session MDZmNDAwNDI1NDEyYmYzNDc5MDhlMjZmYmE1OWJhZDk.
333925:23:35.444 INF: CID=0x0e6f Routing REGISTER for URI sip:6563630554@192.168.1.105
333925:23:35.444 PWL: CID=0x0000 -->> From: sip:6563630554@192.168.1.105 Target: REGISTER sip:6563630554@192.168.1.105:5060
333925:23:35.445 INF: CID=0x0e6f *** UPPER REGISTRATION ENABLE *** for sip:6563630554@192.168.1.105
333925:23:35.463 INF: CID=0x0e6f Event: Setting UA Core Proxy to handle event REGISTER
333925:23:35.467 INF: CID=0x0e6f *** DESTROYED *** PROXY Session MDZmNDAwNDI1NDEyYmYzNDc5MDhlMjZmYmE1OWJhZDk.
333925:23:35.467 INF: CID=0x0e6f PROXY: Session DESTROYED
333925:23:35.468 INF: CID=0x0e6f *** DESTROYED *** PROXY Session MDZmNDAwNDI1NDEyYmYzNDc5MDhlMjZmYmE1OWJhZDk.
333925:23:35.468 INF: CID=0x0e6f PROXY: Session DESTROYED
333925:23:35.682 INF: CID=0x0e6f Event: Setting UA Core Proxy to handle event REGISTER
333925:23:35.683 INF: CID=0x0e6f Session CREATED
333925:23:35.683 INF: CID=0x0e6f *** CREATED *** PROXY Session MDZmNDAwNDI1NDEyYmYzNDc5MDhlMjZmYmE1OWJhZDk.
333925:23:35.691 INF: CID=0x0e6f Routing REGISTER for URI sip:6563630554@192.168.1.105
333925:23:35.692 PWL: CID=0x0000 -->> From: sip:6563630554@192.168.1.105 Target: REGISTER sip:6563630554@192.168.1.105:5060
333925:23:35.692 INF: CID=0x0e6f *** UPPER REGISTRATION ENABLE *** for sip:6563630554@192.168.1.105
333925:23:35.694 INF: CID=0x0e66 Event: Setting UA Core Proxy to handle event REGISTER
333925:23:35.695 INF: CID=0x0e66 Session CREATED
333925:23:35.696 INF: CID=0x0e66 *** CREATED *** PROXY Session MjliMjEwMGU3ZmM3YTQ3MTJiOGJlZGY0MjYzZDdkOTA.

Best regards,
Yuriy.
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Opensipstack-osbcdevel mailing list
Opensipstack-osbcdevel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensipstack-osbcdevel
Click to view tyv's profile  
tyv
3 posts since
Feb 5, 2008
2. Feb 8, 2008 9:40 AM in response to: Guest
Re: [OpenSBC] OpeтSBC ceases to work
Joegen, I sent you the letter with logs.

I'll try to install OpenSBC under Debian. May be It can help me...
Click to view tyv's profile  
tyv
3 posts since
Feb 5, 2008
3. Feb 14, 2008 5:02 AM in response to: tyv
Re: [OpenSBC] OpeтSBC ceases to work
After full reinstall OpenSBC it works without break some hours.
May be upgrade from cvs really fixed problem.

Actions

More Like This