[VoIP] Upgrading my Server & Asterisk 1.4 Troubles

[Lee Spenadel]

Here's what I implemented when I upgraded to 1.4

Lee


;*************************************************************************
[macro-dialcnet]
;
; Collectors' Network
;
exten => s,1,Set(E164NETWORKS=std.ckts.info)
;
; Check to see if ARG1 is preceded by a "+"
exten => s,2,GotoIf($[ ${ARG1:0:1} = "+"]?startloop) ;  ; Skip next line if
it already is prefixed by a plus; 
							; Otherwise, add one
to the beginning.
exten => s,3,Set(ARG1=+${ARG1})
exten =>
s,4(startloop),Set(ENUM=${ENUMLOOKUP(${ARG1},ALL,,1,std.ckts.info)})
;exten =>
s,4(startloop),Set(ENUM=${ENUMLOOKUP(${ARG1}.std.ckts.info,ALL,,std.ckts.inf
o)})
;
; Sanity check the return, make sure there's something in there.
; If not, send it to CONTINUE.
exten => s,5,GotoIf($[${LEN(${ENUM})} = 0 ]?continue) ; ; If the return
includes the word SIP, go to SIPURI 
exten => s,6,GotoIf($[${ENUM:0:3} = sip ]?sipuri) ; ; Otherwise, if the
return includes the word IAX, go to IAXURI 
exten => s,7,GotoIf($[${ENUM:0:3} = iax ]?iaxuri) ; ; And, if the return
includes the word H323, send it to H323URI 
exten => s,8,GotoIf($[${ENUM:0:3} = h32 ]?h323uri) ; ; If we're here, it's
not a protocol we know about. Let's increment the pointer 
							; and if it's more
than ENUMCOUNT, we know we've run out of options.
;
; This is the generic CANT BE ROUTED spot 
exten => s,9(continue),Macro(invalid-office-code,${ARG1}) 
exten => s,10,Wait(5) 
exten => s,11,Hangup ; ; If the prefix is 'sip:'...
exten => s,12(sipuri),Set(DIALSTR=SIP/${ENUM:5})
exten => s,13,Goto(dodial)
;
; If it's IAX2...
exten => s,14(iaxuri),Set(DIALSTR=IAX2/${ENUM:5})
exten => s,15,Goto(dodial)
;
; Or even if it's H323.
exten => s,16(h323uri),Set(DIALSTR=H323/${ENUM:5})
;
; And this is where we end up if we actually CAN route the call.
exten => s,17(dodial),Dial(${DIALSTR})
exten => s,18,Hangup
exten => s,118,Busy
;*************************************************************************

-----Original Message-----
From: voip-bounces at ckts.info [mailto:voip-bounces at ckts.info] On Behalf Of
Dimitri Ressetar
Sent: Saturday, March 08, 2008 8:26 PM
To: voip at ckts.info
Subject: [VoIP] Upgrading my Server & Asterisk 1.4 Troubles

Hi everyone!

I've had my switch offline for quite a while, and I'm doing a lot of
upgrades to it. I got a T1 interface card and a 24 FXS channel bank, so
I can actually plug in real phones to my Asterisk system! I've also
completely upgraded the server, it is now a Celeron 2.5 GHz with 768MB
of RAM (much better than my P2 300 MHz).

Right now, I'm running into the problem many of you have already run
into upgrading to Asterisk 1.4 -- ENUM support. I know that the 1.2
version won't work, but do we have a relatively standardized version of
cnet ENUM dialing for 1.4? I've been able to update the rest of my
dialplan to 1.4 without much trouble, but I don't know how ENUM and ENUM
dialing in Asterisk work. I'm not even sure if I used the original
example from the ckts.info website, I might have copied the one from an
old version of TrixBox, back before I switched to coding my own dialplan.

Maybe there should be a page somewhere on the ckts.info website with all
the info that each Cnet Office needs to know...the basic ENUM, IAX, SIP,
and CallerID configurations to work on the network, as well as the usual
test line numbering, etc. Just a thought.

Thanks in advance to anyone who can help!
-Dimitri Ressetar
_______________________________________________
VoIP mailing list
VoIP at ckts.info
http://lists.ckts.info/mailman/listinfo/voip
Project Web Page: http://www.ckts.info/