Re: [asterisk-users] Treating T1 as trunk in/out, not individual lines

2007-10-29 Thread Brian Hutchinson
List - Non-Commercial Discussion > *Subject:* Re: [asterisk-users] Treating T1 as trunk in/out, not > individual lines > > Michelle Dupuis wrote: > > I'm tying a Nortel option 61 to asterisk via T1. I don't want to split > each of the t1 channels out into

Re: [asterisk-users] Treating T1 as trunk in/out, not individual lines

2007-10-28 Thread Tilghman Lesher
On Saturday 27 October 2007 14:35:55 Benny Amorsen wrote: > > "DL" == Doug Lytle <[EMAIL PROTECTED]> writes: > > DL> Michelle Dupuis wrote: > >> Ok - that's great. I see how the destination number will match to > >> the exten value, but how do I access the from number '248xxx'? > > DL> exte

Re: [asterisk-users] Treating T1 as trunk in/out, not individual lines

2007-10-27 Thread Benny Amorsen
> "DL" == Doug Lytle <[EMAIL PROTECTED]> writes: DL> Michelle Dupuis wrote: >> Ok - that's great. I see how the destination number will match to >> the exten value, but how do I access the from number '248xxx'? >> DL> exten => s,1,GotoIf($["${CALLERID(number)}" = "248xxx" ]?2:3) Tha

Re: [asterisk-users] Treating T1 as trunk in/out, not individual lines

2007-10-27 Thread Eric "ManxPower" Wieling
Michelle Dupuis wrote: > Ok..so how would the CALLED and CALLERID ID be presented to Asterisk when > using PRI signaling. The CALLING and CALLED numbers are sent automatically during the call setup. CALLING NAME is usually sent right after the call setup happens. ___

Re: [asterisk-users] Treating T1 as trunk in/out, not individual lines

2007-10-27 Thread Doug Lytle
Michelle Dupuis wrote: > Ok - that's great. I see how the destination number will match to the exten > value, but how do I access the from number '248xxx'? > exten => s,1,GotoIf($["${CALLERID(number)}" = "248xxx" ]?2:3) Doug -- Ben Franklin quote: "Those who would give up Essent

Re: [asterisk-users] Treating T1 as trunk in/out, not individual lines

2007-10-27 Thread Michelle Dupuis
October 27, 2007 9:44 AM > To: Asterisk Users Mailing List - Non-Commercial Discussion > Subject: Re: [asterisk-users] Treating T1 as trunk in/out, > not individual lines > > Michelle Dupuis wrote: > > Ok..so how would the CALLED and CALLERID ID be presented to > Asterisk >

Re: [asterisk-users] Treating T1 as trunk in/out, not individual lines

2007-10-27 Thread Lyle Giese
> Mike > > > *From:* [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] *On Behalf Of > *Lyle Giese > *Sent:* Friday, October 26, 2007 5:54 PM > *To:* Asterisk Users Mailing List - Non-Commercial Discussion > *Subject:* Re: [asterisk-use

Re: [asterisk-users] Treating T1 as trunk in/out, not individual lines

2007-10-27 Thread Doug Lytle
Michelle Dupuis wrote: > Ok..so how would the CALLED and CALLERID ID be presented to Asterisk > when using PRI signaling. > When you are using a PRI, you'll see something like: Accepting call from '248xxx' to '734xxx' on channel 0/1, span 1 So, for the inbound, you'd have an entry tha

Re: [asterisk-users] Treating T1 as trunk in/out, not individual lines

2007-10-27 Thread Michelle Dupuis
: Re: [asterisk-users] Treating T1 as trunk in/out, not individual lines Michelle Dupuis wrote: I'm tying a Nortel option 61 to asterisk via T1. I don't want to split each of the t1 channels out into individual lines (tied to a specific extension) - so a trunk in and out. Assuming P

Re: [asterisk-users] Treating T1 as trunk in/out, not individual lines

2007-10-26 Thread Lyle Giese
Michelle Dupuis wrote: > I'm tying a Nortel option 61 to asterisk via T1. I don't want to > split each of the t1 channels out into individual lines (tied to a > specific extension) - so a trunk in and out. > > Assuming PRI over T1 signaling, how would I pass the CALLED and CALLER > info across t