[VoIP] extensions.conf unhandled extensions

Fri Feb 15 16:45:11 CST 2008

Over in the UK, Au and NZ  we've gone down a different avenue to you guys in 
the US. We use the old public STD (DDD) dialling codes and tones to recreate 
the telephone networks as they were many years ago. A number of us have the 
original public exchanges from that era which we are connecting to CNET 
using their original STD(DDD) dialling codes.  We've also set up the local 
dialling codes between exchanges that existed at the time where applicable.

Hence we've developed a way of giving the correct tones that the public 
network would have given at the time that STD/DDD was introduced.    If you 
are dialling into a 'heritage' exchange you get 'number unobtainable' tone 
and the same applies now applies if you dial another number on the Asterisk 
box. We didn't have recorded messages until much later.

Hence the little macros :-)   We are now working on creating a few 'manual' 
exchanges.  Just in the process of recording the voices of  the original 
operators from the original manual exchanges :-)   That bit gets harder as 
the last manual exchange in the UK went automatic in 1976!

Ian Jolly

----- Original Message ----- 
From: "Donald Froula" <dfroula at sbcglobal.net>
To: <jnovack at stromberg-carlson.org>; "Voice Over IP Tandem for Analog 
Switches" <voip at ckts.info>
Sent: Friday, February 15, 2008 4:33 PM
Subject: Re: [VoIP] extensions.conf unhandled extensions

>I use the following to provide a readback of any
> number that does not resolve in the context:
>
> exten => _X.,1,Answer
> exten => _X.,2,Playback(the-number-u-dialed)
> exten => _X.,3,SayDigits(${EXTEN},f)
> exten => _X.,4,Playback(T-is-not-available)
> exten => _X.,5,HangUp
>
> It's especially helpful for users of ProjectMF trying
> to get their MF tone levels adjusted correctly.
>
> Don
>
> --- John Novack <novackster at gmail.com> wrote:
>
>> I simply transferred what Ian sent me.
>> He is correct, his dialplan made my head hurt!!
>> I wonder if there is a piece missing to generate the
>> special tones. It
>> has been some time now, and the memory fades quickly
>> these days.
>> Ian,  if Mad MArk has his router configured, you can
>> access with PuTTY
>> and PSFTP if something needs to be added or changed.
>> AstLinux is born with SSH user "root" and password
>> "astlinux" and the
>> web interface user "admin" and password "astlinux"
>> If Mark has changed it then he will have to let you
>> know.
>> Pretty exciting to be able to support him half way
>> around the world!
>>
>> John Novack
>>
>>
>> Ian Jolly wrote:
>> > Hi Mark
>> >
>> > I'm puzzled as the lines to deal with the
>> unallocated numbers were in
>> > the configs I wrote.
>> >
>> > The way the US guys approach things are different
>> from ours.  Quite a
>> > few of the US guys just use CNET as somewhere to
>> use an Asterisk and
>> > hence are not trying to reproduce the system as it
>> was in the days
>> > when our old exchanges were in use. Hence their
>> use of Asterisk in its
>> > unaltered form.  The 'catch all' should have been
>> at the end of the
>> > two contexts - [Aulocal] and [fromcnet] . Maybe
>> you didn't spot them
>> > but I did  comment them as 'Nu tone on spare
>> numbers'
>> >
>> > exten => _X.,1,Macro(AUNUtone)  ; NU Tone on spare
>> numbers
>> >
>> > Have you got a list of the relays in your final
>> selector (i.e. A, B,
>> > CD, E , F, G. etc) and any details of labels or
>> other markings on the
>> > selector. Does it have two or three pairs of
>> wipers on the main shaft?
>> >
>> > regards
>> >
>> > Ian
>> >
>> >
>> > ----- Original Message ----- From: "Mad Mark"
>> <madmanmarkau at hotmail.com>
>> > To: "VOIP" <voip at ckts.info>
>> > Sent: Thursday, February 14, 2008 10:43 AM
>> > Subject: [VoIP] extensions.conf unhandled
>> extensions
>> >
>> >
>> >>
>> >> I've been looking over the extensions.conf in my
>> *box (Asterisk 1.2)
>> >> and I can't tell how to trap unhandled
>> extensions.
>> >>
>> >> I've backed up my entire * config, and have been
>> having a play
>> >> learning how the extensions file works. It's
>> quite simple in reality,
>> >> but I haven't found a way to trap all extensions
>> that don't match any
>> >> of the pattern matching done in the file. Is
>> there a special context
>> >> or extension name for unhandled extensions? Any
>> help?
>> >>
>> >> I also had a play with my line finder switch last
>> night. Spent three
>> >> hours desoldering all the terminals - 210 of
>> them, or thereabouts.
>> >> Strangly, I didn't find it tedious. I actually
>> found it quite
>> >> relaxing and theraputic. I've cleaned and tinned
>> all connections and
>> >> repaired a couple of things like bent supports
>> for the return
>> >> springs, oiled it and cleaned the terminal bank.
>> It's in top working
>> >> order now, and I'm one step closer to building my
>> exchange. I should
>> >> be getting a suitable power supply in a few days,
>> so I'll be able to
>> >> see my equipment come to life for the first time
>> in 40 years.
>> >
>>
> ------------------------------------------------------------------------
>> >
>> > _______________________________________________
>> > VoIP mailing list
>> > VoIP at ckts.info
>> > http://lists.ckts.info/mailman/listinfo/voip
>> > Project Web Page: http://www.ckts.info/
>> >
>>
>> -- 
>> Dog is my co-pilot
>>
>> _______________________________________________
>> VoIP mailing list
>> VoIP at ckts.info
>> http://lists.ckts.info/mailman/listinfo/voip
>> Project Web Page: http://www.ckts.info/
>>
>
> _______________________________________________
> VoIP mailing list
> VoIP at ckts.info
> http://lists.ckts.info/mailman/listinfo/voip
> Project Web Page: http://www.ckts.info/ 