Started a new thread to keep things separated...
Here it is:
Primary:
[r...@gssipx02 ~]# yum list | grep stunnel
Bad id for repo: CentOS5 base, byte = 7
Bad id for repo: CentOS5 updates, byte = 7
stunnel.i386 4.26-1 installed
[r...@gssipx02 ~]# ps aux | grep stunnel
500 376 0.0 0.1 6800 3836 ? Sl Jun07 0:43
/usr/sbin/stunnel /tmp/stunnel-config.364.0
500 377 0.0 0.0 5196 740 ? S Jun07 0:00
/usr/sbin/stunnel /tmp/stunnel-config.364.0
500 378 0.0 0.0 5196 496 ? S Jun07 0:00
/usr/sbin/stunnel /tmp/stunnel-config.364.0
500 379 0.0 0.0 5196 496 ? S Jun07 0:00
/usr/sbin/stunnel /tmp/stunnel-config.364.0
500 380 0.0 0.0 5196 496 ? S Jun07 0:00
/usr/sbin/stunnel /tmp/stunnel-config.364.0
500 381 0.0 0.0 5196 496 ? S Jun07 0:00
/usr/sbin/stunnel /tmp/stunnel-config.364.0
root 879 0.0 0.0 3924 680 pts/0 S+ 17:41 0:00 grep
stunnel
[r...@gssipx02 ~]#
Secondary:
[r...@gmsipx02 ~]# yum list | grep stunnel
Bad id for repo: CentOS5 base, byte = 7
Bad id for repo: CentOS5 updates, byte = 7
stunnel.i386 4.26-1 installed
[r...@gmsipx02 ~]# ps aux | grep stunnel
root 8005 0.0 0.0 3920 684 pts/0 S+ 17:45 0:00 grep
stunnel
500 25608 0.0 0.0 5448 2264 ? S May26 1:04
/usr/sbin/stunnel /etc/sipxpbx/sipxcallresolver-agent-config
500 25611 0.0 0.0 5128 540 ? S May26 0:02
/usr/sbin/stunnel /etc/sipxpbx/sipxcallresolver-agent-config
500 25612 0.0 0.0 5128 400 ? S May26 0:00
/usr/sbin/stunnel /etc/sipxpbx/sipxcallresolver-agent-config
500 25613 0.0 0.0 5128 400 ? S May26 0:00
/usr/sbin/stunnel /etc/sipxpbx/sipxcallresolver-agent-config
500 25614 0.0 0.0 5128 400 ? S May26 0:00
/usr/sbin/stunnel /etc/sipxpbx/sipxcallresolver-agent-config
500 25615 0.0 0.0 5128 400 ? S May26 0:00
/usr/sbin/stunnel /etc/sipxpbx/sipxcallresolver-agent-config
[r...@gmsipx02 ~]#
> ----- Message from Josh Patten <jpat...@co.brazos.tx.us> on Wed, 23
> That is probably because stunnel isn't running correctly. I've
> experienced this as well.
>
> Do me a favor and return the output of the following commands on all
> your servers:
>
> yum list | grep stunnel
>
> ps aux | grep stunnel
> Josh Patten
> Assistant Network Administrator
> Brazos County IT Dept.
> (979) 361-4676
>
> On 6/23/2010 10:28 AM, Paul Scheepens wrote:
>
> > ----- Message from Douglas Hubler <dhub...@ezuce.com> on Wed, 23
> Jun 2010 09:54:16 -0400 -----
> >
> > On Wed, Jun 23, 2010 at 8:56 AM, Staffan Kerker
<ietf-li...@kerker.se>wrote:
> > > OK, good to know. Voicemail is not a critical application, basic SIP
> > > routing/registration and SIP trunking is. I'll disable the voicemail
> > > feature.
> >
> > for other's benefit others, voicemail would work fine. tui into
> > voicemail would be fine, it's just web ui into voicemail would rely on
> > nfs and the issues related to that.
> >
>
> One thing I noticed is that I don't get CDR records of calls where
> calling and called party are
> both on a secondary server. Maybe a problem in my setup, but if not
> then there won't be any CDR's
> in this setup.
>
>
> _______________________________________________
> sipx-users mailing list sipx-users@list.sipfoundry.org
> List Archive: http://list.sipfoundry.org/archive/sipx-users
> Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
> sipXecs IP PBX -- http://www.sipfoundry.org/
> _______________________________________________
> sipx-users mailing list sipx-users@list.sipfoundry.org
> List Archive: http://list.sipfoundry.org/archive/sipx-users
> Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
> sipXecs IP PBX -- http://www.sipfoundry.org/
_______________________________________________
sipx-users mailing list sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/
