[pstn-local]
; Next, check for numbers that are available “locally” out of
; my analog line connected to the house. In area code 503,
; you must dial an area code in front of all numbers, and
; a “1″ is not possible in front of local numbers. Annoying.
;
; Thus, this rule matches “15035551212″ but will dial “5035551212″
;
; If the first line (DIALOUTANALOG) is busy, then fail over
; and dial out the iconnecthere SIP peer. This ensures harmony
; in the household when She is one one line and I require the phone. ![]()
;
; Note that the iconnect Dial doesn’t strip the first digit, since
; we need the single “1″ prefix in those outbound calls.
;
; The list is duplicated for area code “971″, which is an overlay
; for 503
;
exten => _1503.,1,Dial(${DIALOUTANALOG}/${EXTEN:1})
exten => _1503.,2,Macro(fastbusy)
exten => _1503.,102,Macro(dialiconnect,${EXTEN},70)
exten => _1971.,1,Dial(${DIALOUTANALOG}/${EXTEN:1})
exten => _1971.,2,Macro(fastbusy)
exten => _1971.,102,Macro(dialiconnect,${EXTEN},70)
[pstn-local-toll]
; Well, what about calls that are long distance in my local (503) area?
; I handle this by dialing them as “115035551212″ and the system will
; then match and remove the first “1″ digit. Ugly, but it works.
;
; The question is, of course, “should these go via iconnect”? I don’t
; have the costs in front of me, but I may well remove this whole logic
; path once I figure it out.
;
; Ex: This rule will match ’115036661313″ and will dial “15036661313″
;
; Again, fail over to iconnect peer if analog busy, but this time
; we’re going to strip the first digit, since “11″ is not a valid
; prefix for iconnecthere calls.
;
; If there is some “other” type of error, dump to a fast busy.
;
; The list is duplicated for area code “971″, which is an overlay
; for 503.
;
;
exten => _11503.,1,Dial(${DIALOUTANALOG}/${EXTEN:1})
exten => _11503.,2,Macro(fastbusy)
exten => _11503.,102,Macro(dialiconnect,${EXTEN:1},70)
exten => _11971.,1,Dial(${DIALOUTANALOG}/${EXTEN:1})
exten => _11971.,2,Macro(fastbusy)
exten => _11971.,102,Macro(dialiconnect,${EXTEN:1},70)
[toll-free]
; Dial toll-free numbers (800, 877, 888, 866, 855) from the analog line
; and roll over to iconnect peer if analog is busy.
;
; In case of “other” type of error, dump to a fast busy.
;
exten => _1888.,1,Dial(${DIALOUTANALOG}/${EXTEN})
exten => _1888.,2,Macro(fastbusy)
exten => _1888.,102,Macro(dialiconnect,${EXTEN},70)
exten => _1877.,1,Dial(${DIALOUTANALOG}/${EXTEN})
exten => _1877.,2,Macro(fastbusy)
exten => _1877.,102,Macro(dialiconnect,${EXTEN},70)
exten => _1866.,1,Dial(${DIALOUTANALOG}/${EXTEN})
exten => _1866.,2,Macro(fastbusy)
exten => _1866.,102,Macro(dialiconnect,${EXTEN},70)
exten => _1855.,1,Dial(${DIALOUTANALOG}/${EXTEN})
exten => _1855.,2,Macro(fastbusy)
exten => _1855.,102,Macro(dialiconnect,${EXTEN},70)
exten => _1800.,1,Dial(${DIALOUTANALOG}/${EXTEN})
exten => _1800.,2,Macro(fastbusy)
exten => _1800.,102,Macro(dialiconnect,${EXTEN},70)
[coloco-local]
; I do consulting for Coloco, Inc. (http://www.coloco.com/) for VOIP
; (also known as Baltimore Washington Telephone Inc.) based in Laurel, MD.
; They sell server co-location, IP bandwidth, and they have an SS7 switch
; located in the same room as the servers, making PRI cross-connects
; very well-priced for inbound and outbound calling. Quite a few call
; centers and dial service providers have their equipment located there.
;
; So I have several gateway machines there running both Asterisk as well
; as just Cisco 3640′s running with the T1 VOIP interface cards. I use
; these as experimental gateways, and for working on customer problems.
;
; Now, this is the list of area codes that should be shunted out the SIP
; gateway in Laurel. The area codes of 301, 410, 703, and 240 are “local”
; to the gateway in Laurel, so I select them manually.
;
; See “sip.conf” for details on how I set up the “coloco” SIP peer
;
; If the dial to Coloco fails, then jump to iconnect.
;
; If iconnect fails, dump to fast busy.
;
; I really should put some announcements in between call spillovers
; so that I can tell when my call is going one way or the other, but
; I’m not certain that would be tremendously useful. Maybe later…
;
; If you have no other SIP peers that have visibility into local
; area codes, feel free to comment these lines out entirely.
;
;
; 301 is Suburban MD, DC Metro
exten => _1301.,1,Dial(SIP/${EXTEN}@coloco)
exten => _1301.,2,Macro(dialiconnect,${EXTEN},70)
exten => _1301.,3,Macro(fastbusy)
; 410 is Baltimore Metro and Eastern Shore, MD
exten => _1410.,1,Dial(SIP/${EXTEN}@coloco)
exten => _1410.,2,Macro(dialiconnect,${EXTEN},70)
exten => _1410.,3,Macro(fastbusy)
; 703 is Northern Virgina, DC Metro
exten => _1703.,1,Dial(SIP/${EXTEN}@coloco)
exten => _1703.,2,Macro(dialiconnect,${EXTEN},70)
exten => _1703.,3,Macro(fastbusy)
; 240 is Suburban MD, DC Metro overlay
exten => _1240.,1,Dial(SIP/${EXTEN}@coloco)
exten => _1240.,2,Macro(dialiconnect,${EXTEN},70)
exten => _1240.,3,Macro(fastbusy)
; 202 is Washington DC
exten => _1202.,1,Dial(SIP/${EXTEN}@coloco)
exten => _1202.,2,Macro(dialiconnect,${EXTEN},70)
exten => _1202.,3,Macro(fastbusy)
[iaxtel-out]
; This dials users on the Gnophone IAX server. Since they
; so conveniently have all their users in the “700″ area code,
; I put this in my section that deals with dialing non-prefixed
; “long distance” calls, even though the channel used is an IAX
; connection. See http://x.linux-support.net/directory/ to
; sign up.
;
; The 700 area code is actually allocated in the NANPA, but I don’t
; think I’ll be ringing up any defense department or FEMA locations
; in the near future, so overlap is OK as far as I’m concerned.
;
; The configs for the IAX channel sessions are located in the file
; /etc/asterisk/iax.conf
;
; For some reason,
exten => _1700NXXXXXX,1,SetCallerID(${MYIAXTELNUMBER})
exten => _1700NXXXXXX,2,SetCIDName(${MYNAME})
exten => _1700NXXXXXX,3,Dial(IAX/${IAXINFO}@iaxtel.com/${EXTEN}@iaxtel)


