I have a problem with asterisk, receive these errors, after that phones are not registered and I need to restart asterisk.
[Sep 6 10:39:44] ERROR[2521] ais/clm.c: Could not initialize cluster membership service: Try Again [Sep 6 10:39:44] WARNING[2521] chan_sip.c: sip.conf: Different 'nat' settings between [general] and section [gw_20_patton]. See /usr/share/doc/asterisk/README.Debian.gz (global='Always' peer/user='RFC3581')
gw_20_patton on the gemeinschaft has nat = no, the same like in [general] on the /opt/gemeinschaft/etc/asterisk/sip.conf
> I have a problem with asterisk, receive these errors, after that phones
> are not registered and I need to restart asterisk.
> [Sep 6 10:39:44] ERROR[2521] ais/clm.c: Could not initialize cluster
> membership service: Try Again
> [Sep 6 10:39:44] WARNING[2521] chan_sip.c: sip.conf: Different 'nat'
> settings between [general] and section [gw_20_patton]. See
> /usr/share/doc/asterisk/README.Debian.gz (global='Always'
> peer/user='RFC3581')
> gw_20_patton on the gemeinschaft has nat = no, the same like in
> [general] on the /opt/gemeinschaft/etc/asterisk/sip.conf
> Please help
> Thanks
> --
> To unsubscribe from this group, send email to
> gs3-users+unsubscribe@googlegroups.com
> Diese Mailingliste wird kostenlos von Usern f r User betrieben. Unter
> http://www.amooma.de bekommen Sie schnellen kommerziellen Support und
> Consulting vom Hersteller von Gemeinschaft.
> Remove all keys from your phones that use BLF or EXTENSION.
> After restarting the phones go to the asterisk CLI and type:
> core show hints
> "Watchers" should now be 0 everywhere.
> Try it for a few days. If your problem has vanished, I am right and you > have small problem.
> There is way to backport Gemeinschaft to asterisk 1.4, but it is a bit > of work.
> I am suporting many Gemeinschaft installations and a vanishing chan_sip > was allways related to this deadlock.
> Greets
> Sascha
> Am 06.09.12 11:34, schrieb Michal Meyza: > > Hello
> > I have a problem with asterisk, receive these errors, after that phones > > are not registered and I need to restart asterisk.
> > [Sep 6 10:39:44] ERROR[2521] ais/clm.c: Could not initialize cluster > > membership service: Try Again > > [Sep 6 10:39:44] WARNING[2521] chan_sip.c: sip.conf: Different 'nat' > > settings between [general] and section [gw_20_patton]. See > > /usr/share/doc/asterisk/README.Debian.gz (global='Always' > > peer/user='RFC3581')
> > gw_20_patton on the gemeinschaft has nat = no, the same like in > > [general] on the /opt/gemeinschaft/etc/asterisk/sip.conf
> > Please help
> > Thanks
> > -- > > To unsubscribe from this group, send email to > > gs3-users+...@googlegroups.com <javascript:>
> > Diese Mailingliste wird kostenlos von Usern f�r User betrieben. Unter > > http://www.amooma.de bekommen Sie schnellen kommerziellen Support und > > Consulting vom Hersteller von Gemeinschaft.
are you sure these messages are not related to this problem?
[Sep 6 10:39:44] ERROR[2521] ais/clm.c: Could not initialize cluster membership service: Try Again
[Sep 6 10:39:44] WARNING[2521] chan_sip.c: sip.conf: Different 'nat' settings between [general] and section [gw_20_patton]. See /usr/share/doc/asterisk/README.Debian.gz (global='Always' peer/user='RFC3581')
each time after phones unregistered we have these errors...
W dniu czwartek, 6 września 2012 12:42:15 UTC+2 użytkownik Michal Meyza napisał:
>> Remove all keys from your phones that use BLF or EXTENSION.
>> After restarting the phones go to the asterisk CLI and type:
>> core show hints
>> "Watchers" should now be 0 everywhere.
>> Try it for a few days. If your problem has vanished, I am right and you >> have small problem.
>> There is way to backport Gemeinschaft to asterisk 1.4, but it is a bit >> of work.
>> I am suporting many Gemeinschaft installations and a vanishing chan_sip >> was allways related to this deadlock.
>> Greets
>> Sascha
>> Am 06.09.12 11:34, schrieb Michal Meyza: >> > Hello
>> > I have a problem with asterisk, receive these errors, after that phones >> > are not registered and I need to restart asterisk.
>> > [Sep 6 10:39:44] ERROR[2521] ais/clm.c: Could not initialize cluster >> > membership service: Try Again >> > [Sep 6 10:39:44] WARNING[2521] chan_sip.c: sip.conf: Different 'nat' >> > settings between [general] and section [gw_20_patton]. See >> > /usr/share/doc/asterisk/README.Debian.gz (global='Always' >> > peer/user='RFC3581')
>> > gw_20_patton on the gemeinschaft has nat = no, the same like in >> > [general] on the /opt/gemeinschaft/etc/asterisk/sip.conf
>> > Please help
>> > Thanks
>> > -- >> > To unsubscribe from this group, send email to >> > gs3-users+...@googlegroups.com
>> > Diese Mailingliste wird kostenlos von Usern f�r User betrieben. Unter >> > http://www.amooma.de bekommen Sie schnellen kommerziellen Support und >> > Consulting vom Hersteller von Gemeinschaft.
> are you sure these messages are not related to this problem?
> [Sep 6 10:39:44] ERROR[2521] ais/clm.c: Could not initialize cluster
> membership service: Try Again
Does not matter, because it is not used.
> [Sep 6 10:39:44] WARNING[2521] chan_sip.c: sip.conf: Different 'nat'
> settings between [general] and section [gw_20_patton]. See
> /usr/share/doc/asterisk/README.Debian.gz (global='Always'
> peer/user='RFC3581')
This is only a warning and I have never seen a crashing chan_sip because of nat settings (yet).
> each time after phones unregistered we have these errors...
To be really sure without disabeling BLF, you must compile asterisk with debug symbols to make a backtrace.
That is a lot of work and depending on your hardware and call per minute it will be horrible slow.
I can not run asterisk 1.6 with debug symbols on my Dual QuadCore Xeon with 600 phones and a few thousand calls a day. After half an hour asterisk is so dead slow, that the PBX is unusable.
If your hardware is fast enough, you can compile asterisk with debug symbols and make a backtrace after chan_sip has vanished.
> Am 06.09.12 12:52, schrieb Michal Meyza: > > are you sure these messages are not related to this problem?
> > [Sep 6 10:39:44] ERROR[2521] ais/clm.c: Could not initialize cluster > > membership service: Try Again
> Does not matter, because it is not used.
> > [Sep 6 10:39:44] WARNING[2521] chan_sip.c: sip.conf: Different 'nat' > > settings between [general] and section [gw_20_patton]. See > > /usr/share/doc/asterisk/README.Debian.gz (global='Always' > > peer/user='RFC3581')
> This is only a warning and I have never seen a crashing chan_sip because > of nat settings (yet).
> > each time after phones unregistered we have these errors...
> To be really sure without disabeling BLF, you must compile asterisk with > debug symbols to make a backtrace.
> That is a lot of work and depending on your hardware and call per minute > it will be horrible slow.
> I can not run asterisk 1.6 with debug symbols on my Dual QuadCore Xeon > with 600 phones and a few thousand calls a day. After half an hour > asterisk is so dead slow, that the PBX is unusable.
> If your hardware is fast enough, you can compile asterisk with debug > symbols and make a backtrace after chan_sip has vanished.
> Or you can say: I go back to 1.4 without testing.
> so, when we set "Line" instead of BLF and Extension.. that will solve
> our problem?
To be honest, I don't know what the Snom does with "line".
In Gemeinschaft there are two Options that make sense.
1. Extension/BLF (depending on Firmware version)
That is to monitor another extension, pickup that extension when it is ringing or call that extension. Both options make a subscription to the hint of that extension on the asterisk.
-> deadlock bug
2. External destination
That option just dials the number an nothing more. No monitoring, no pickup and so on.
There is no way to monitor another extension without having possible deadlocks.
> Am 06.09.12 13:37, schrieb Michal Meyza: > > so, when we set "Line" instead of BLF and Extension.. that will solve > > our problem?
> To be honest, I don't know what the Snom does with "line".
> In Gemeinschaft there are two Options that make sense.
> 1. Extension/BLF (depending on Firmware version)
> That is to monitor another extension, pickup that extension when it is > ringing or call that extension. Both options make a subscription to the > hint of that extension on the asterisk.
> -> deadlock bug
> 2. External destination
> That option just dials the number an nothing more. No monitoring, no > pickup and so on.
> There is no way to monitor another extension without having possible > deadlocks.
> Remove all keys from your phones that use BLF or EXTENSION.
> After restarting the phones go to the asterisk CLI and type:
> core show hints
> "Watchers" should now be 0 everywhere.
> Try it for a few days. If your problem has vanished, I am right and you > have small problem.
> There is way to backport Gemeinschaft to asterisk 1.4, but it is a bit > of work.
> I am suporting many Gemeinschaft installations and a vanishing chan_sip > was allways related to this deadlock.
> Greets
> Sascha
> Am 06.09.12 11:34, schrieb Michal Meyza: > > Hello
> > I have a problem with asterisk, receive these errors, after that phones > > are not registered and I need to restart asterisk.
> > [Sep 6 10:39:44] ERROR[2521] ais/clm.c: Could not initialize cluster > > membership service: Try Again > > [Sep 6 10:39:44] WARNING[2521] chan_sip.c: sip.conf: Different 'nat' > > settings between [general] and section [gw_20_patton]. See > > /usr/share/doc/asterisk/README.Debian.gz (global='Always' > > peer/user='RFC3581')
> > gw_20_patton on the gemeinschaft has nat = no, the same like in > > [general] on the /opt/gemeinschaft/etc/asterisk/sip.conf
> > Please help
> > Thanks
> > -- > > To unsubscribe from this group, send email to > > gs3-users+...@googlegroups.com <javascript:>
> > Diese Mailingliste wird kostenlos von Usern f�r User betrieben. Unter > > http://www.amooma.de bekommen Sie schnellen kommerziellen Support und > > Consulting vom Hersteller von Gemeinschaft.
