asterisk users - Nov 2006 - email etiquette (was: Re: Unicall MFC problems in 0.0.3+asterisk 1.2)

It's bad enough that people insert long config/log files/dumps into
messages to this list, though it's convenient. But when people include
the entire redundant content in a quote in reply, it's really a waste.
The digest messages are hard enough to navigate, even with an intro
index, before making 95% of their content a redundant quoted dump.  I
know we've all got lots of bandwidth and storage, but these dumps just
make a haystack in which to find the occasional needle of useful
content.

	Please consider storing long machine input/output data at a URL, then
emailing just a link to it.


On Mon, 2006-11-20 at 07:55 -0700,
asterisk-users-request@lists.digium.com wrote:
> Date: Mon, 20 Nov 2006 10:20:19 -0300
> From: "Facundo Ameal" <fameal@gmail.com>
> Subject: Re: [Asterisk-Users] Unicall MFC problems in 0.0.3+asterisk
>         1.2
> To: "Asterisk Users Mailing List - Non-Commercial Discussion"
>         <asterisk-users@lists.digium.com>
> Message-ID:
>         <a563d36f0611200520h391f034asb9ced19e3ebeb6a3@mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> 
> That issue is because the extensions does not exist. Check DNIS digits
> in unicall.conf
> 
> On 4/25/06, Guillermo Freige <gfreige@hotmail.com> wrote:
> > Hi Steve and everyone
> > I have a very strange problem with an old 1st gen TDM410P card
I've
> been
> > using in the production machine (10-15K calls/day) without problem
> with
> > Asterisk 1.0.7+Unicall 0.0.2.
> > When I switched to Asterisk 1.2 and Unicall 0.0.3 (even in 1.2.7.1
> and
> > pre9), span 3 handled mfc signalling awfully. Spans 1,2 and 4 worked
> fine.
> > I've tested it in both 2.4 and 2.6 linux kernels in a Debian 3.1
> > distribution, and in 2 different servers, with 2 different E1 telco
> lines,
> > with the same results. 2nd gen cards work just fine in every span.
> > This is the log from a couple of incoming calls. The right ANI/DNIS
> were
> > 2214291350 and 0200.
> >
> > Apr 25 11:08:17 WARNING[18731] chan_unicall.c: MFC/R2 UniCall/79
> <-
> > 0001  [1/       1/Idle          /Idle         ]
> > Apr 25 11:08:17 WARNING[18731] chan_unicall.c: MFC/R2 UniCall/79
> Detected
> > Apr 25 11:08:17 WARNING[18731] chan_unicall.c: MFC/R2 UniCall/79
> Making a
> > new call with CRN 32769
> > Apr 25 11:08:17 WARNING[18731] chan_unicall.c: MFC/R2 UniCall/79
> 1101  -> 
-- 

(C) Matthew Rubenstein

Like http://pastebin.com/

Matthew Rubenstein wrote:
> 	It's bad enough that people insert long config/log files/dumps into
> messages to this list, though it's convenient. But when people include
> the entire redundant content in a quote in reply, it's really a waste.
> The digest messages are hard enough to navigate, even with an intro
> index, before making 95% of their content a redundant quoted dump.  I
> know we've all got lots of bandwidth and storage, but these dumps just
> make a haystack in which to find the occasional needle of useful
> content.
> 
> 	Please consider storing long machine input/output data at a URL, then
> emailing just a link to it.

On Mon, Nov 20, 2006 at 12:57:24PM -0500, Matthew Rubenstein
wrote:
> 	Please consider storing long machine input/output data at a URL, then
> emailing just a link to it.
And, if you don't have such a place handy, check out www.pastebin.com,
which is quite useful for such stuff.

Though, of course, it *does* reduce the usefulness of the list archive,
since it times out.  But, as Matt says, at the *least*, please learn
how to clip your quotes, folks.

Cheers,
-- jra
-- 
Jay R. Ashworth                                                jra@baylink.com
Designer                          Baylink                             RFC 2100
Ashworth & Associates        The Things I Think                       
'87 e24
St Petersburg FL USA      http://baylink.pitas.com             +1 727 647 1274

	"That's women for you; you divorce them, and 10 years later,
	  they stop having sex with you."  -- Jennifer Crusie; _Fast_Women_