[Asterisk-Dev] Re: TDMoE + kernel badness

2005-11-08 Thread Fabio Ferrari
Here is a patch to try to solve problems related to:
Badness in local_bh_enable at kernel/softirq.c on 2.6.X

Basically I posphoned the dev_queue_xmit to after the spin_unlock_irqrestore.

Regards,
Fabio Ferrari


alts
Description: Binary data
___
Asterisk-Dev mailing list
Asterisk-Dev@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-dev
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev

[Asterisk-Dev] Current HEAD: res_config_odbc.c compilation failure

2005-11-08 Thread Patrick
Hi all,

I hope this is not considered a -users question. If so please accept my
apologies for the noise. Compilation of cvs HEAD from about two hours
ago fails in res_config_odbc.c with the following messages:

gcc  -pipe  -Wall -Wstrict-prototypes -Wmissing-prototypes
-Wmissing-declarations -g  -Iinclude -I../include -D_REENTRANT
-D_GNU_SOURCE  -O6 -march=k8 -DZAPTEL_OPTIMIZATIONS -m64
-fomit-frame-pointer   -DZAPATA_MOH -DOPENSSL_NO_KRB5 -fPIC   -c -o
res_config_odbc.o res_config_odbc.c
In file included from res_config_odbc.c:36:
../include/asterisk/file.h:52: error: syntax error before '*' token
../include/asterisk/file.h:52: warning: function declaration isn't a
prototype
../include/asterisk/file.h:53: error: syntax error before '*' token
../include/asterisk/file.h:53: warning: function declaration isn't a
prototype
res_config_odbc.c: In function 'realtime_odbc':
res_config_odbc.c:98: warning: implicit declaration of function
'snprintf'
res_config_odbc.c:98: warning: incompatible implicit declaration of
built-in function 'snprintf'
res_config_odbc.c:105: warning: pointer targets in passing argument 2 of
'SQLPrepare' differ in signedness
res_config_odbc.c:149: warning: pointer targets in passing argument 3 of
'SQLDescribeCol' differ in signedness
res_config_odbc.c: In function 'realtime_multi_odbc':
res_config_odbc.c:242: warning: incompatible implicit declaration of
built-in function 'snprintf'
res_config_odbc.c:251: warning: pointer targets in passing argument 2 of
'SQLPrepare' differ in signedness
res_config_odbc.c:303: warning: pointer targets in passing argument 3 of
'SQLDescribeCol' differ in signedness
res_config_odbc.c: In function 'update_odbc':
res_config_odbc.c:370: warning: incompatible implicit declaration of
built-in function 'snprintf'
res_config_odbc.c:378: warning: pointer targets in passing argument 2 of
'SQLPrepare' differ in signedness
res_config_odbc.c: In function 'config_odbc':
res_config_odbc.c:448: warning: incompatible implicit declaration of
built-in function 'snprintf'
make[1]: *** [res_config_odbc.o] Error 1

Any suggestions for a quick fix?

Thanks and regards,
Patrick

___
Asterisk-Dev mailing list
Asterisk-Dev@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-dev
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev


Re: [Asterisk-Dev] Current HEAD: res_config_odbc.c compilation failure

2005-11-08 Thread BJ Weschke
 Please post a bug for this in bugs.digium.com.

On 11/8/05, Patrick [EMAIL PROTECTED] wrote:
 Hi all,

 I hope this is not considered a -users question. If so please accept my
 apologies for the noise. Compilation of cvs HEAD from about two hours
 ago fails in res_config_odbc.c with the following messages:

 gcc  -pipe  -Wall -Wstrict-prototypes -Wmissing-prototypes
 -Wmissing-declarations -g  -Iinclude -I../include -D_REENTRANT
 -D_GNU_SOURCE  -O6 -march=k8 -DZAPTEL_OPTIMIZATIONS -m64
 -fomit-frame-pointer   -DZAPATA_MOH -DOPENSSL_NO_KRB5 -fPIC   -c -o
 res_config_odbc.o res_config_odbc.c
 In file included from res_config_odbc.c:36:
 ../include/asterisk/file.h:52: error: syntax error before '*' token
 ../include/asterisk/file.h:52: warning: function declaration isn't a
 prototype
 ../include/asterisk/file.h:53: error: syntax error before '*' token
 ../include/asterisk/file.h:53: warning: function declaration isn't a
 prototype
 res_config_odbc.c: In function 'realtime_odbc':
 res_config_odbc.c:98: warning: implicit declaration of function
 'snprintf'
 res_config_odbc.c:98: warning: incompatible implicit declaration of
 built-in function 'snprintf'
 res_config_odbc.c:105: warning: pointer targets in passing argument 2 of
 'SQLPrepare' differ in signedness
 res_config_odbc.c:149: warning: pointer targets in passing argument 3 of
 'SQLDescribeCol' differ in signedness
 res_config_odbc.c: In function 'realtime_multi_odbc':
 res_config_odbc.c:242: warning: incompatible implicit declaration of
 built-in function 'snprintf'
 res_config_odbc.c:251: warning: pointer targets in passing argument 2 of
 'SQLPrepare' differ in signedness
 res_config_odbc.c:303: warning: pointer targets in passing argument 3 of
 'SQLDescribeCol' differ in signedness
 res_config_odbc.c: In function 'update_odbc':
 res_config_odbc.c:370: warning: incompatible implicit declaration of
 built-in function 'snprintf'
 res_config_odbc.c:378: warning: pointer targets in passing argument 2 of
 'SQLPrepare' differ in signedness
 res_config_odbc.c: In function 'config_odbc':
 res_config_odbc.c:448: warning: incompatible implicit declaration of
 built-in function 'snprintf'
 make[1]: *** [res_config_odbc.o] Error 1

 Any suggestions for a quick fix?

 Thanks and regards,
 Patrick

 ___
 Asterisk-Dev mailing list
 Asterisk-Dev@lists.digium.com
 http://lists.digium.com/mailman/listinfo/asterisk-dev
 To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev

___
Asterisk-Dev mailing list
Asterisk-Dev@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-dev
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev


Re: [Asterisk-Dev] Current HEAD: res_config_odbc.c compilation failure

2005-11-08 Thread Patrick
http://bugs.digium.com/view.php?id=5653

On Tue, 2005-11-08 at 09:38 -0500, BJ Weschke wrote:
  Please post a bug for this in bugs.digium.com.
 
 On 11/8/05, Patrick [EMAIL PROTECTED] wrote:
  Hi all,
 
  I hope this is not considered a -users question. If so please accept my
  apologies for the noise. Compilation of cvs HEAD from about two hours
  ago fails in res_config_odbc.c with the following messages:
 
  gcc  -pipe  -Wall -Wstrict-prototypes -Wmissing-prototypes
  -Wmissing-declarations -g  -Iinclude -I../include -D_REENTRANT
  -D_GNU_SOURCE  -O6 -march=k8 -DZAPTEL_OPTIMIZATIONS -m64
  -fomit-frame-pointer   -DZAPATA_MOH -DOPENSSL_NO_KRB5 -fPIC   -c -o
  res_config_odbc.o res_config_odbc.c
  In file included from res_config_odbc.c:36:
  ../include/asterisk/file.h:52: error: syntax error before '*' token
  ../include/asterisk/file.h:52: warning: function declaration isn't a
  prototype
  ../include/asterisk/file.h:53: error: syntax error before '*' token
  ../include/asterisk/file.h:53: warning: function declaration isn't a
  prototype
  res_config_odbc.c: In function 'realtime_odbc':
  res_config_odbc.c:98: warning: implicit declaration of function
  'snprintf'
  res_config_odbc.c:98: warning: incompatible implicit declaration of
  built-in function 'snprintf'
  res_config_odbc.c:105: warning: pointer targets in passing argument 2 of
  'SQLPrepare' differ in signedness
  res_config_odbc.c:149: warning: pointer targets in passing argument 3 of
  'SQLDescribeCol' differ in signedness
  res_config_odbc.c: In function 'realtime_multi_odbc':
  res_config_odbc.c:242: warning: incompatible implicit declaration of
  built-in function 'snprintf'
  res_config_odbc.c:251: warning: pointer targets in passing argument 2 of
  'SQLPrepare' differ in signedness
  res_config_odbc.c:303: warning: pointer targets in passing argument 3 of
  'SQLDescribeCol' differ in signedness
  res_config_odbc.c: In function 'update_odbc':
  res_config_odbc.c:370: warning: incompatible implicit declaration of
  built-in function 'snprintf'
  res_config_odbc.c:378: warning: pointer targets in passing argument 2 of
  'SQLPrepare' differ in signedness
  res_config_odbc.c: In function 'config_odbc':
  res_config_odbc.c:448: warning: incompatible implicit declaration of
  built-in function 'snprintf'
  make[1]: *** [res_config_odbc.o] Error 1
 
  Any suggestions for a quick fix?
 
  Thanks and regards,
  Patrick
 
  ___
  Asterisk-Dev mailing list
  Asterisk-Dev@lists.digium.com
  http://lists.digium.com/mailman/listinfo/asterisk-dev
  To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
 
 ___
 Asterisk-Dev mailing list
 Asterisk-Dev@lists.digium.com
 http://lists.digium.com/mailman/listinfo/asterisk-dev
 To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
___
Asterisk-Dev mailing list
Asterisk-Dev@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-dev
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev


[Asterisk-Dev] How to start?

2005-11-08 Thread Isack Waserman
Hello All,
I am new to all of this.
I want to devlope a C application using the asterisk API.
I also want to (try) writ my own hardware driver for Asterisk.
Is it possible?
what steps i should take in order to start?
Thanks in advance
Isack
___
Asterisk-Dev mailing list
Asterisk-Dev@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-dev
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev


Re: [Asterisk-Dev] How to start?

2005-11-08 Thread BJ Weschke
 Welcome!

 You can go here for some initial information about the Asterisk architecture:
 http://www.digium.com/downloads/AstriconEurope2005Tutorial.pdf

 And once you're ready, you can visit this link for information on how
to contribute:
 http://www.asterisk.org/developers

On 11/8/05, Isack Waserman [EMAIL PROTECTED] wrote:
 Hello All,
 I am new to all of this.
 I want to devlope a C application using the asterisk API.
 I also want to (try) writ my own hardware driver for Asterisk.
 Is it possible?
 what steps i should take in order to start?
 Thanks in advance
 Isack
 ___
 Asterisk-Dev mailing list
 Asterisk-Dev@lists.digium.com
 http://lists.digium.com/mailman/listinfo/asterisk-dev
 To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev

___
Asterisk-Dev mailing list
Asterisk-Dev@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-dev
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev


[Asterisk-Dev] [OTAnn] Feedback

2005-11-08 Thread shenanigans
I was interested in getting feedback from current mail group users.We have mirrored your mail list in a new application that provides a more aggregated and safe environment which utilizes the power of broadband.Roomity.com v 1.5 is a web 2.01 community webapp. Our newest version adds broadcast video and social networking such as favorite authors and an html editor.It?s free to join and any feedback would be appreciated.S.Broadband interface (RIA) + mail box saftey = Asterisk_Developers_List.roomity.com*Your* clubs, no sign up to read, ad supported; try broadband internet. ~~1131470377249~~___
Asterisk-Dev mailing list
Asterisk-Dev@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-dev
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev

Re: [Asterisk-Dev] Asterisk or Polycom Bug? - Message waiting

2005-11-08 Thread Rod Dorman
On Monday, November 7, 2005, 18:25:08, Will McCown wrote:
   ...
 The bad news it that the light remains lit even if there are no
 new messages (as I pretty much expected).  So, it appears that if
 the polycom gets a message-summary with Messages-Waiting: no
 then it ignores the rest of the message and sets all of the counts
 to zero.  Reading the RFC I can see how this might be considered
 the correct behavior.

My  take  on RFC 3842 is that Messages-Waiting: is a 'new' messages flag
only  and  the  presence of 'old' messages are only communicated via the
xxx-Message: lines.

In particular 3.11. Rate of Notifications where it has the phrase
...which do not affect the overall message waiting state
(e.g., there are still new messages).

-- 
[EMAIL PROTECTED] The avalanche has already started, it is too
Rod Dorman  late for the pebbles to vote. – Ambassador Kosh

___
Asterisk-Dev mailing list
Asterisk-Dev@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-dev
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev


Re: [Asterisk-Dev] [OTAnn] Feedback

2005-11-08 Thread Matt Riddell
shenanigans wrote:
 I was interested in getting feedback from current mail group users.

This is really pushing it now.  That's three times.

-- 
Cheers,

Matt Riddell
___

http://www.sineapps.com/news.php (Daily Asterisk News - html)
http://freevoip.gedameurope.com (Free Asterisk Voip Community)
http://www.sineapps.com/rssfeed.php (Daily Asterisk News - rss)

___
Asterisk-Dev mailing list
Asterisk-Dev@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-dev
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev


[Asterisk-Dev] Patch to allow Dial() to ignore call forward

2005-11-08 Thread John Lange
When dialing a group of phones it is often desirable to have Asterisk
ignore any 302 Redirect requests it might receive.

For example: after hours a business may want the general number to ring
multiple extensions so that anyone thats still around can answer it.
However, one of those people may have set their phone to call-forward to
their voicemail or cell phone.

The following patch applies against 1.0.9 and adds another option to the
Dial command.

i tells asterisk to ignore any 302 Redirects and continue on dialing
the rest of the extensions.

Brief example: phone at 2000 is set to forward.

extensions.conf:

exten = 2000,1,Dial(SIP/2000SIP/2002,20,i)

CLI output:

-- Executing Dial(SIP/2001-eece, SIP/2000SIP/2002|20|i) in new stack
-- Called 2000
-- Called 2002
-- SIP/2002-d46a is ringing
-- Got SIP response 302 Moved Temporarily back from 192.168.1.101
-- Now forwarding SIP/2001-eece to 'Local/[EMAIL PROTECTED]' (thanks to 
SIP/2000-d08d)
-- Forwarding SIP/2001-eece to 'Local/[EMAIL PROTECTED]' prevented by dial 
option 'i'
Nov  8 11:34:19 NOTICE[27509]: app_dial.c:240 wait_for_answer: Unable to create 
local channel for call forward to 'Local/[EMAIL PROTECTED]'
  == Spawn extension (from-sip, 2000, 1) exited non-zero on 'SIP/2001-eece'

-- 
John Lange
OpenIT ltd. www.Open-IT.ca (204) 885 0872
VoIP, Web services, Linux Consulting, Server Co-Location
--- asterisk-1.0.9/apps/app_dial.c	2005-05-11 20:43:36.0 -0500
+++ asterisk-1.0.9.modified/apps/app_dial.c	2005-11-08 11:46:11.0 -0600
@@ -59,6 +59,7 @@
   This application returns -1 if the originating channel hangs up, or if the\n
 call is bridged and either of the parties in the bridge terminate the call.\n
 The option string may contain zero or more of the following characters:\n
+  'i' -- Asterisk will ignore any 302 REDIRECT it gets from the phone.\n
   't' -- allow the called user transfer the calling user by hitting #.\n
   'T' -- allow the calling user to transfer the call by hitting #.\n
   'f' -- Forces callerid to be set as the extension of the line \n
@@ -106,6 +107,7 @@
 struct localuser {
 	struct ast_channel *chan;
 	int stillgoing;
+int allowforward;
 	int allowredirect_in;
 	int allowredirect_out;
 	int ringbackonly;
@@ -228,8 +230,13 @@
 	/* Before processing channel, go ahead and check for forwarding */
 	if (option_verbose  2)
 		ast_verbose(VERBOSE_PREFIX_3 Now forwarding %s to '%s/%s' (thanks to %s)\n, in-name, tech, stuff, o-chan-name);
-	/* Setup parameters */
-	o-chan = ast_request(tech, in-nativeformats, stuff);
+if (!o-allowforward) {
+ast_verbose(VERBOSE_PREFIX_3 Forwarding %s to '%s/%s' prevented by dial option 'i'\n, in-name, tech, stuff);
+o-chan = NULL;
+} else {
+	   /* Setup parameters */
+	   o-chan = ast_request(tech, in-nativeformats, stuff);
+}
 	if (!o-chan) {
 		ast_log(LOG_NOTICE, Unable to create local channel for call forward to '%s/%s'\n, tech, stuff);
 		o-stillgoing = 0;
@@ -440,6 +447,7 @@
 	int allowdisconnect_in=0;
 	int allowdisconnect_out=0;
 	int noforwardhtml=0;
+int allowforward=1;
 	int hasmacro = 0;
 	int privacy=0;
 	int announce=0;
@@ -722,6 +730,15 @@
 		}
 		memset(tmp, 0, sizeof(struct localuser));
 		if (transfer) {
+			if (strchr(transfer, 'i')) {
+allowforward = tmp-allowforward = 0;
+			if (option_verbose  5)
+ast_verbose(VERBOSE_PREFIX_3 Dial option prevent forwarding set 'On'\n);
+} else {
+allowforward = tmp-allowforward = 1;
+			if (option_verbose  5)
+ast_verbose(VERBOSE_PREFIX_3 Dial option prevent forwarding set 'Off'\n);
+}
 			if (strchr(transfer, 't'))
 tmp-allowredirect_in = 1;
 elsetmp-allowredirect_in = 0;
@@ -788,7 +805,11 @@
 ast_verbose(VERBOSE_PREFIX_3 Forwarding %s to '%s/%s' (thanks to %s)\n, chan-name, tech, stuff, tmp-chan-name);
 			/* Setup parameters */
 			ast_hangup(tmp-chan);
-			tmp-chan = ast_request(tech, chan-nativeformats, stuff);
+if (!tmp-allowforward) {
+ast_verbose(VERBOSE_PREFIX_3 Forwarding %s to '%s/%s' prevented by dial option 'i'\n, chan-name, tech, stuff);
+} else {
+			tmp-chan = ast_request(tech, chan-nativeformats, stuff);
+}
 			if (!tmp-chan) {
 ast_log(LOG_NOTICE, Unable to create local channel for call forward to '%s/%s'\n, tech, stuff);
 free(tmp);
___
Asterisk-Dev mailing list
Asterisk-Dev@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-dev
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev

Re: [Asterisk-Dev] Patch to allow Dial() to ignore call forward

2005-11-08 Thread Jared Smith
On Tue, 2005-11-08 at 11:57 -0600, John Lange wrote:
 The following patch applies against 1.0.9 and adds another option to the
 Dial command.

Would you please add this patch to the bug tracker, and if possible,
create one against CVS HEAD?  Asterisk 1.2 is getting quite close to
being released, and new features are no longer being added to the 1.0.x
series.  Note that you'll also need to send in a signed disclaimer if
you want your patch considered for inclusion within Asterisk itself.

-Jared

___
Asterisk-Dev mailing list
Asterisk-Dev@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-dev
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev


Re: [Asterisk-Dev] Patch to allow Dial() to ignore call forward

2005-11-08 Thread Tilghman Lesher
On Tuesday 08 November 2005 11:57, John Lange wrote:
 The following patch applies against 1.0.9 and adds another option to
 the Dial command.

snip

Please post your patch (and all patches henceforward) to
http://bugs.digium.com.  Patches sent to the -devel list are not
considered for submission.

-- 
Tilghman
___
Asterisk-Dev mailing list
Asterisk-Dev@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-dev
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev


[Asterisk-Dev] say.c cleanup

2005-11-08 Thread Luigi Rizzo
i am working on cleaning up asterisk/say.c and i need a bit
of advice.

The idea is to provide, for each supported language, a descriptor
with roughly these fields:
struct _lang_sw {
char *language;

int initialized;/* 0 at beginning */
say_number_full_f   *say_number_full;
say_enumeration_full_f  *say_enumeration_full;
say_date_f  *say_date;
say_date_with_format_f  *say_date_with_format;
say_time_f  *say_time;
say_datetime_f  *say_datetime;
say_datetime_from_now_f *say_datetime_from_now;
};

where the various say_*_f fields are pointers to the language-specific
functions, and fallback to some default language for not-implemented
methods.
As a first step everything will be in one file, later maybe
i will implement languages as loadable modules.

The above list of function is derived from the current code. However,
i think there is a lot of redudancy that needs to be removed.  E.g.
all the say_date/time function right now are written from scratch,
whereas they could be implemented as calls to say_date_with_format_*()
with a specific format.  I have no idea on what is the spec for
ast_say_datetime_from_now(),

comments/suggestions anyone ?

also i would need people to review the code for the various
languages as submitting the change as a patch is simply hopeless,
basically the entire file is being rewritten/reorganized.

cheers
luigi
___
Asterisk-Dev mailing list
Asterisk-Dev@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-dev
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev


[Asterisk-Dev] chan_bluetooth

2005-11-08 Thread Sven Boeckelmann
Hi all,

can someone tell me what the latest status of chan_bluetooth/chan_bt is?
I've been playing around with the 'latest' sources from crazygeek. 
But I noticed that there are also some other people working on it. 
So here's what I've been asking myself:

What is chan_bt, is it just another name for chan_bluetooth?
Are there any developers working on other bluetooth channel solutions?

Thanks!

Sven

___
Asterisk-Dev mailing list
Asterisk-Dev@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-dev
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev


[Asterisk-Dev] asterisk.spec and the redhat dir

2005-11-08 Thread Jason Pyeron


Who is the maintainer for the RedHat aspects of *?
or is it abandoned?


--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
-   -
- Jason Pyeron  PD Inc. http://www.pdinc.us -
- Partner  Sr. Manager 7 West 24th Street #100 -
- +1 (443) 269-1555 Baltimore, Maryland 21218   -
-   -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

This message is for the designated recipient only and may contain 
privileged, proprietary, or otherwise private information. If you 
have received it in error, purge the message from your system and 
notify the sender immediately.  Any other use of the email by you 
is prohibited.

___
Asterisk-Dev mailing list
Asterisk-Dev@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-dev
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-dev


Re: [Asterisk-Dev] asterisk.spec and the redhat dir

2005-11-08 Thread Kevin P. Fleming

Jason Pyeron wrote:


Who is the maintainer for the RedHat aspects of *?
or is it abandoned?


Nobody in particular. Jeffrey Ollie was posting some patches this 
summer, but I haven't seen much from him lately.

___
Asterisk-Dev mailing list
Asterisk-Dev@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-dev
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-dev