Re: [Astlinux-users] Minimal modules.conf ( was Re: Astlinux 0.6.3 Warning & Error's)

2009-03-07 Thread Cleveland Electronic Services 
Hi All

 

While Googling for some other information I came across this thread hope it
help someone in the future.

 

http://www.voip-info.org/wiki/view/Asterisk+Slimming

 

Cheers

 

Cleve 

 

 

From: John Novack [mailto:jnov...@stromberg-carlson.org] 
Sent: Sunday, 8 March 2009 12:36 AM
To: AstLinux Users Mailing List
Subject: Re: [Astlinux-users] Minimal modules.conf ( was Re: Astlinux 0.6.3
Warning & Error's)

 

Post away You don't need my permission!!
One puzzle I never solved is the need to load the macro application. I know
my use of the 1.2 version  is unusual, and wonder if something else I said
to no load caused that, but never explored it. 
The systems I have built use the macro quite a bit, so the problem
immediately 
became obvious

John Novack


Cleveland Electronic Services wrote:




Hi John,

 

Thanks once again for the useful information, I used some of your examples
below to get rid of some more untoward stuff showing up on the logs, now my
logs are nice and clean. I am writing up a document as I go through as it is
a bit of a learning curve since 0.4.8 would you mind if I add this
information to it with a link to this post?

 

Thanks

 

Cheers

 

Cleve 

 

From: John Novack [mailto:jnov...@stromberg-carlson.org] 
Sent: Friday, 6 March 2009 1:34 PM
To: AstLinux Users Mailing List; thely...@gmail.com
Subject: [Astlinux-users] Minimal modules.conf ( was Re: Astlinux 0.6.3
Warning & Error's)

 

This is for Astlinux 0.5  a late version of Asterisk 1.2
Your results may vary
You may have to add to the list for 1.4

Tom Lynn wrote:;
[modules]
autoload=yes
;
; If you want, load the GTK console right away.  
; Don't load the KDE console since
; it's not as sophisticated right now.
;
noload => pbx_gtkconsole.so
;load => pbx_gtkconsole.so
noload => pbx_kdeconsole.so
;
; Intercom application is obsoleted by
; chan_oss.  Don't load it.
;
noload => app_intercom.so
;
; Explicitly load the chan_modem.so early on to be sure
; it loads before any of the chan_modem_* 's afte rit
;
noload => chan_modem.so
noload => res_musiconhold.so
;
;
; Load either OSS or ALSA, not both
; By default, load OSS only (automatically) and do not load ALSA
;
noload => chan_modem_i4l.so
noload => chan_modem_bestdata.so
noload => chan_modem_aopen.so
noload => chan_mgcp.so
noload => chan_alsa.so
noload => chan_oss.so
noload => chan_skinny.so
noload => chan_misdn.so
noload => res_odbc.so
noload => cdr_odbc.so
noload => cdr_pgsql.so
noload => chan_sccp.so
noload => app_alarmreceiver.so
noload => app_realtime.so
noload => cdr_addon_mysql.so
noload => codec_g729c.so
noload => format_g729c.so
noload => pbx_dundi.so
noload => pbx_ael.so
load => app_macro.so
;
Not sure why I needed to add the last line.




 

On Thu, Mar 5, 2009 at 8:12 AM, John Novack 
wrote:



Darrick Hartman wrote: 


<mailto:%21&%21AAAYABneuvYbYkZAnTIuaCUoikvCgAAAEOhflI78U
MdKs/gxroo96b8ba...@clevelandelectronicservices.com>

Message-ID: <3a248f9d4dd820e398a51733736c4...@localhost>
X-Sender: dhart...@djhsolutions.com
Received: from rrcs-74-87-125-110.west.biz.rr.com [74.87.125.110] with
HTTP/1.1
(POST); Thu, 05 Mar 2009 09:49:36 -0600
User-Agent: RoundCube Webmail/0.1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
 
Cleve,
 
You can either ignore the warnings or disable the modules that are trying to
load (that you're not using).  
 
If you look at /etc/asterisk/modules.conf, you'll see several modules
listed.
 
In your case, you would want to noload res_smdi.so and chan_misdn.so since
it doesn't look like you're using those.
 
  

I no load a whole host of unused modules.
Somewhere, many moons ago, I found a posting on one of the lists that had
suggestions. If modules.conf is set to "autoload" then one can no load
these, as well as skinny, mgcp, musiconhold if you aren't using it and a
raft of others.
Anyone interested I can post my "minimal" load.
Also on some versions, I found that the application macro wasn't loading,
and had to specify that to load. Never figured out why.
 






Not sure why you're seeing RED ALARM for dahdi (which is really zaptel, but
Digium made the change to call it dahdi even if we're still using zaptel...)
 
  

In my experience, if FXO ports on a TDM400 aren't connected to a CO to see
battery, they will give a RED alarm.

John Novack 







Darrick
 
On Fri, 6 Mar 2009 01:47:36 +1100, "Cleveland Electronic Services"
 <mailto:i...@clevelandelectronicservices.com>
 wrote:
  

Hi All.
 
I am seeing a lot of this in my logs, any ideas how to fix it.
 
Mar  6 00:39:18 pbx local0.warn asterisk[1462]: WARNING[1462]:
res_smdi.c:1335 in load_module: No SMDI interfaces are available to


listen
  

on, not starting SMDI listener.
Mar  6 00:39:1

Re: [Astlinux-users] Minimal modules.conf ( was Re: Astlinux 0.6.3 Warning & Error's)

2009-03-07 Thread John Novack 

Post away You don't need my permission!!
One puzzle I never solved is the need to load the macro application. I 
know my use of the 1.2 version  is unusual, and wonder if something else 
I said to no load caused that, but never explored it.
The systems I have built use the macro quite a bit, so the problem 
immediately

became obvious

John Novack


Cleveland Electronic Services wrote:


Hi John,

 

Thanks once again for the useful information, I used some of your 
examples below to get rid of some more untoward stuff showing up on 
the logs, now my logs are nice and clean. I am writing up a document 
as I go through as it is a bit of a learning curve since 0.4.8 would 
you mind if I add this information to it with a link to this post?


 


Thanks

 


Cheers

 


*Cleve*

 


*From:* John Novack [mailto:jnov...@stromberg-carlson.org]
*Sent:* Friday, 6 March 2009 1:34 PM
*To:* AstLinux Users Mailing List; thely...@gmail.com
*Subject:* [Astlinux-users] Minimal modules.conf ( was Re: Astlinux 
0.6.3 Warning & Error's)


 


This is for Astlinux 0.5  a late version of Asterisk 1.2
Your results may vary
You may have to add to the list for 1.4

Tom Lynn wrote:;
[modules]
autoload=yes
;
; If you want, load the GTK console right away. 
; Don't load the KDE console since

; it's not as sophisticated right now.
;
noload => pbx_gtkconsole.so
;load => pbx_gtkconsole.so
noload => pbx_kdeconsole.so
;
; Intercom application is obsoleted by
; chan_oss.  Don't load it.
;
noload => app_intercom.so
;
; Explicitly load the chan_modem.so early on to be sure
; it loads before any of the chan_modem_* 's afte rit
;
noload => chan_modem.so
noload => res_musiconhold.so
;
;
; Load either OSS or ALSA, not both
; By default, load OSS only (automatically) and do not load ALSA
;
noload => chan_modem_i4l.so
noload => chan_modem_bestdata.so
noload => chan_modem_aopen.so
noload => chan_mgcp.so
noload => chan_alsa.so
noload => chan_oss.so
noload => chan_skinny.so
noload => chan_misdn.so
noload => res_odbc.so
noload => cdr_odbc.so
noload => cdr_pgsql.so
noload => chan_sccp.so
noload => app_alarmreceiver.so
noload => app_realtime.so
noload => cdr_addon_mysql.so
noload => codec_g729c.so
noload => format_g729c.so
noload => pbx_dundi.so
noload => pbx_ael.so
load => app_macro.so
;
Not sure why I needed to add the last line.

 

On Thu, Mar 5, 2009 at 8:12 AM, John Novack 
mailto:jnov...@stromberg-carlson.org>> 
wrote:




Darrick Hartman wrote:

mailto:rkba...@clevelandelectronicservices.com>> 

 
<mailto:%21&%21AAAYABneuvYbYkZAnTIuaCUoikvCgAAAEOhflI78UMdKs/gxroo96b8ba...@clevelandelectronicservices.com>
Message-ID: <3a248f9d4dd820e398a51733736c4...@localhost>
X-Sender: dhart...@djhsolutions.com <mailto:dhart...@djhsolutions.com>
Received: from rrcs-74-87-125-110.west.biz.rr.com 
<http://rrcs-74-87-125-110.west.biz.rr.com> [74.87.125.110] with HTTP/1.1
(POST); Thu, 05 Mar 2009 09:49:36 -0600
User-Agent: RoundCube Webmail/0.1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
 
Cleve,
 
You can either ignore the warnings or disable the modules that are trying to load (that you're not using).  
 
If you look at /etc/asterisk/modules.conf, you'll see several modules listed.
 
In your case, you would want to noload res_smdi.so and chan_misdn.so since it doesn't look like you're using those.
 
  


I no load a whole host of unused modules.
Somewhere, many moons ago, I found a posting on one of the lists that 
had suggestions. If modules.conf is set to "autoload" then one can no 
load these, as well as skinny, mgcp, musiconhold if you aren't using 
it and a raft of others.

Anyone interested I can post my "minimal" load.
Also on some versions, I found that the application macro wasn't 
loading, and had to specify that to load. Never figured out why.





Not sure why you're seeing RED ALARM for dahdi (which is really zaptel, but 
Digium made the change to call it dahdi even if we're still using zaptel...)
 
  

In my experience, if FXO ports on a TDM400 aren't connected to a CO to 
see battery, they will give a RED alarm.


John Novack




Darrick
 
On Fri, 6 Mar 2009 01:47:36 +1100, "Cleveland Electronic Services"

 
<mailto:i...@clevelandelectronicservices.com> wrote:
  


Hi All.

 


I am seeing a lot of this in my logs, any ideas how to fix it.

 


Mar  6 00:39:18 pbx local0.warn asterisk[1462]: WARNING[1462]:

res_smdi.c:1335 in load_module: No SMDI interfaces are available to




listen
  


on, not starting SMDI listener.

Mar  6 00:39:18 pbx local0.err asterisk[1462]: ERROR[1462]:

codec_dahdi.c:419 in find_transcoders: Failed to open /dev/zap/transcode:

No

such file or directory

M

Re: [Astlinux-users] Minimal modules.conf ( was Re: Astlinux 0.6.3 Warning & Error's)

2009-03-06 Thread Cleveland Electronic Services 
Hi John,

 

Thanks once again for the useful information, I used some of your examples
below to get rid of some more untoward stuff showing up on the logs, now my
logs are nice and clean. I am writing up a document as I go through as it is
a bit of a learning curve since 0.4.8 would you mind if I add this
information to it with a link to this post?

 

Thanks

 

Cheers

 

Cleve 

 

From: John Novack [mailto:jnov...@stromberg-carlson.org] 
Sent: Friday, 6 March 2009 1:34 PM
To: AstLinux Users Mailing List; thely...@gmail.com
Subject: [Astlinux-users] Minimal modules.conf ( was Re: Astlinux 0.6.3
Warning & Error's)

 

This is for Astlinux 0.5  a late version of Asterisk 1.2
Your results may vary
You may have to add to the list for 1.4

Tom Lynn wrote:;
[modules]
autoload=yes
;
; If you want, load the GTK console right away.  
; Don't load the KDE console since
; it's not as sophisticated right now.
;
noload => pbx_gtkconsole.so
;load => pbx_gtkconsole.so
noload => pbx_kdeconsole.so
;
; Intercom application is obsoleted by
; chan_oss.  Don't load it.
;
noload => app_intercom.so
;
; Explicitly load the chan_modem.so early on to be sure
; it loads before any of the chan_modem_* 's afte rit
;
noload => chan_modem.so
noload => res_musiconhold.so
;
;
; Load either OSS or ALSA, not both
; By default, load OSS only (automatically) and do not load ALSA
;
noload => chan_modem_i4l.so
noload => chan_modem_bestdata.so
noload => chan_modem_aopen.so
noload => chan_mgcp.so
noload => chan_alsa.so
noload => chan_oss.so
noload => chan_skinny.so
noload => chan_misdn.so
noload => res_odbc.so
noload => cdr_odbc.so
noload => cdr_pgsql.so
noload => chan_sccp.so
noload => app_alarmreceiver.so
noload => app_realtime.so
noload => cdr_addon_mysql.so
noload => codec_g729c.so
noload => format_g729c.so
noload => pbx_dundi.so
noload => pbx_ael.so
load => app_macro.so
;
Not sure why I needed to add the last line.



 

On Thu, Mar 5, 2009 at 8:12 AM, John Novack 
wrote:



Darrick Hartman wrote: 


<mailto:%21&%21AAAYABneuvYbYkZAnTIuaCUoikvCgAAAEOhflI78U
MdKs/gxroo96b8ba...@clevelandelectronicservices.com>

Message-ID: <3a248f9d4dd820e398a51733736c4...@localhost>
X-Sender: dhart...@djhsolutions.com
Received: from rrcs-74-87-125-110.west.biz.rr.com [74.87.125.110] with
HTTP/1.1
(POST); Thu, 05 Mar 2009 09:49:36 -0600
User-Agent: RoundCube Webmail/0.1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
 
Cleve,
 
You can either ignore the warnings or disable the modules that are trying to
load (that you're not using).  
 
If you look at /etc/asterisk/modules.conf, you'll see several modules
listed.
 
In your case, you would want to noload res_smdi.so and chan_misdn.so since
it doesn't look like you're using those.
 
  

I no load a whole host of unused modules.
Somewhere, many moons ago, I found a posting on one of the lists that had
suggestions. If modules.conf is set to "autoload" then one can no load
these, as well as skinny, mgcp, musiconhold if you aren't using it and a
raft of others.
Anyone interested I can post my "minimal" load.
Also on some versions, I found that the application macro wasn't loading,
and had to specify that to load. Never figured out why.
 





Not sure why you're seeing RED ALARM for dahdi (which is really zaptel, but
Digium made the change to call it dahdi even if we're still using zaptel...)
 
  

In my experience, if FXO ports on a TDM400 aren't connected to a CO to see
battery, they will give a RED alarm.

John Novack 






Darrick
 
On Fri, 6 Mar 2009 01:47:36 +1100, "Cleveland Electronic Services"
 <mailto:i...@clevelandelectronicservices.com>
 wrote:
  

Hi All.
 
I am seeing a lot of this in my logs, any ideas how to fix it.
 
Mar  6 00:39:18 pbx local0.warn asterisk[1462]: WARNING[1462]:
res_smdi.c:1335 in load_module: No SMDI interfaces are available to


listen
  

on, not starting SMDI listener.
Mar  6 00:39:18 pbx local0.err asterisk[1462]: ERROR[1462]:
codec_dahdi.c:419 in find_transcoders: Failed to open /dev/zap/transcode:
No
such file or directory
Mar  6 00:39:18 pbx local0.warn asterisk[1462]: WARNING[1462]:
chan_sip.c:16731 in set_insecure_flags: insecure=very at line 170 is
deprecated; use insecure=port,invite instead
Mar  6 00:39:18 pbx local0.err asterisk[1462]: ERROR[1462]:
chan_misdn.c:5053 in load_module: Unable to initialize mISDN
Mar  6 00:39:18 pbx local0.warn asterisk[1462]: WARNING[1462]:
chan_dahdi.c:3787 in handle_alarms: Detected alarm on channel 1: Red


Alarm
  

Mar  6 00:39:18 pbx local0.warn asterisk[1462]: WARNING[1462]:
chan_dahdi.c:3787 in handle_alarms: Detected alarm on channel 2: Red


Alarm
 
 

--
Op

[Astlinux-users] Minimal modules.conf ( was Re: Astlinux 0.6.3 Warning & Error's)

2009-03-05 Thread John Novack 

This is for Astlinux 0.5  a late version of Asterisk 1.2
Your results may vary
You may have to add to the list for 1.4

Tom Lynn wrote:;
[modules]
autoload=yes
;
; If you want, load the GTK console right away. 
; Don't load the KDE console since

; it's not as sophisticated right now.
;
noload => pbx_gtkconsole.so
;load => pbx_gtkconsole.so
noload => pbx_kdeconsole.so
;
; Intercom application is obsoleted by
; chan_oss.  Don't load it.
;
noload => app_intercom.so
;
; Explicitly load the chan_modem.so early on to be sure
; it loads before any of the chan_modem_* 's afte rit
;
noload => chan_modem.so
noload => res_musiconhold.so
;
;
; Load either OSS or ALSA, not both
; By default, load OSS only (automatically) and do not load ALSA
;
noload => chan_modem_i4l.so
noload => chan_modem_bestdata.so
noload => chan_modem_aopen.so
noload => chan_mgcp.so
noload => chan_alsa.so
noload => chan_oss.so
noload => chan_skinny.so
noload => chan_misdn.so
noload => res_odbc.so
noload => cdr_odbc.so
noload => cdr_pgsql.so
noload => chan_sccp.so
noload => app_alarmreceiver.so
noload => app_realtime.so
noload => cdr_addon_mysql.so
noload => codec_g729c.so
noload => format_g729c.so
noload => pbx_dundi.so
noload => pbx_ael.so
load => app_macro.so
;
Not sure why I needed to add the last line.


On Thu, Mar 5, 2009 at 8:12 AM, John Novack 
mailto:jnov...@stromberg-carlson.org>> 
wrote:




Darrick Hartman wrote:


mailto:rkba...@clevelandelectronicservices.com>> 

 

Message-ID: <3a248f9d4dd820e398a51733736c4...@localhost>
X-Sender: dhart...@djhsolutions.com 
Received: from rrcs-74-87-125-110.west.biz.rr.com 
 [74.87.125.110] with HTTP/1.1
(POST); Thu, 05 Mar 2009 09:49:36 -0600
User-Agent: RoundCube Webmail/0.1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit

Cleve,

You can either ignore the warnings or disable the modules that are trying to load (that you're not using).  


If you look at /etc/asterisk/modules.conf, you'll see several modules 
listed.

In your case, you would want to noload res_smdi.so and chan_misdn.so since 
it doesn't look like you're using those.

  

I no load a whole host of unused modules.
Somewhere, many moons ago, I found a posting on one of the lists
that had suggestions. If modules.conf is set to "autoload" then
one can no load these, as well as skinny, mgcp, musiconhold if you
aren't using it and a raft of others.
Anyone interested I can post my "minimal" load.
Also on some versions, I found that the application macro wasn't
loading, and had to specify that to load. Never figured out why.



Not sure why you're seeing RED ALARM for dahdi (which is really zaptel, but 
Digium made the change to call it dahdi even if we're still using zaptel...)

  

In my experience, if FXO ports on a TDM400 aren't connected to a
CO to see battery, they will give a RED alarm.

John Novack



Darrick

On Fri, 6 Mar 2009 01:47:36 +1100, "Cleveland Electronic Services"
 
 wrote:
  

Hi All.

I am seeing a lot of this in my logs, any ideas how to fix it.

Mar  6 00:39:18 pbx local0.warn asterisk[1462]: WARNING[1462]:
res_smdi.c:1335 in load_module: No SMDI interfaces are available to


listen
  

on, not starting SMDI listener.
Mar  6 00:39:18 pbx local0.err asterisk[1462]: ERROR[1462]:
codec_dahdi.c:419 in find_transcoders: Failed to open /dev/zap/transcode:
No
such file or directory
Mar  6 00:39:18 pbx local0.warn asterisk[1462]: WARNING[1462]:
chan_sip.c:16731 in set_insecure_flags: insecure=very at line 170 is
deprecated; use insecure=port,invite instead
Mar  6 00:39:18 pbx local0.err asterisk[1462]: ERROR[1462]:
chan_misdn.c:5053 in load_module: Unable to initialize mISDN
Mar  6 00:39:18 pbx local0.warn asterisk[1462]: WARNING[1462]:
chan_dahdi.c:3787 in handle_alarms: Detected alarm on channel 1: Red


Alarm
  

Mar  6 00:39:18 pbx local0.warn asterisk[1462]: WARNING[1462]:
chan_dahdi.c:3787 in handle_alarms: Detected alarm on channel 2: Red


Alarm



--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
___
Astlinux-users mailing list
Astlinux-users@lists.sour