Re: [asterisk-users] Treating T1 as trunk in/out, not individual lines
Ditto what Lyle said. It is in the D channel. Your zaptel & zapata configs tell Asterisk what signaling you are using so look there. Google PRI or ISDN and zaptel to see example .conf files. On 10/27/07, Michelle Dupuis <[EMAIL PROTECTED]> wrote: > > Ok..so how would the CALLED and CALLERID ID be presented to Asterisk when > using PRI signaling. > > 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-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 PRI over T1 signaling, how would I pass the CALLED and CALLER > info across the channels so each side knows what to do? Is there something > in the PRI protocol you can point me to for figuring this out? > > Thanks, > MD > > -- > > ___ > --Bandwidth and Colocation Provided by http://www.api-digital.com-- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: >http://lists.digium.com/mailman/listinfo/asterisk-users > > That's what the D channel is for. A PRI is a primary rate ISDN. B > channels carry voice, D channel handles the information & signalling in > ISDN. > > Lyle > > > ___ > --Bandwidth and Colocation Provided by http://www.api-digital.com-- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Treating T1 as trunk in/out, not individual lines
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> exten => s,1,GotoIf($["${CALLERID(number)}" = "248xxx" ]?2:3)
>
> That works, of course, but there's also the traditional
> ex-gf-function:
>
> exten => s/248XXX,1,NoOp(Matched 248...)
> exten => s/X!,1,NoOp(Didn't match)
You can just as easily do the default without any match at all, i.e.
exten => s/248XXX,1,NoOp(Matched 248...)
exten => s,1,NoOp(Didn't match)
Looks cleaner, too.
--
Tilghman
___
--Bandwidth and Colocation Provided by http://www.api-digital.com--
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Treating T1 as trunk in/out, not individual lines
> "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)
That works, of course, but there's also the traditional
ex-gf-function:
exten => s/248XXX,1,NoOp(Matched 248...)
exten => s/X!,1,NoOp(Didn't match)
/Benny
___
--Bandwidth and Colocation Provided by http://www.api-digital.com--
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
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 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. ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Treating T1 as trunk in/out, not individual lines
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 Essential Liberty to purchase a little Temporary
Safety, deserve neither Liberty nor Safety."
___
--Bandwidth and Colocation Provided by http://www.api-digital.com--
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Treating T1 as trunk in/out, not individual lines
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'? > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Doug Lytle > Sent: Saturday, 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 > > 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 that would match against 734. > I have the following in my PRI context: > > exten => _734XXX,1,Gosub(check_blacklist,s,1) > exten => _734XXX,2,NoOP(Caller not blacklisted) exten => > _734XXX,3,Gosub(get_name,s,1) exten => > _734XXX,4,Goto(incoming,s,1) > > > Doug > > -- > > Ben Franklin quote: > > "Those who would give up Essential Liberty to purchase a > little Temporary Safety, deserve neither Liberty nor Safety." > > > > ___ > --Bandwidth and Colocation Provided by http://www.api-digital.com-- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: >http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Treating T1 as trunk in/out, not individual lines
The same as any other zap channel does. That is part of the magic of the zaptel drivers. Lyle Michelle Dupuis wrote: > Ok..so how would the CALLED and CALLERID ID be presented to Asterisk > when using PRI signaling. > > 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-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 PRI over T1 signaling, how would I pass the CALLED and >> CALLER info across the channels so each side knows what to do? >> Is there something in the PRI protocol you can point me to for >> figuring this out? >> >> Thanks, >> MD >> >> >> ___ >> --Bandwidth and Colocation Provided by http://www.api-digital.com-- >> >> asterisk-users mailing list >> To UNSUBSCRIBE or update options visit: >>http://lists.digium.com/mailman/listinfo/asterisk-users > That's what the D channel is for. A PRI is a primary rate ISDN. > B channels carry voice, D channel handles the information & > signalling in ISDN. > > Lyle > > > > ___ > --Bandwidth and Colocation Provided by http://www.api-digital.com-- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: >http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
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 > 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 that would match against 734. I have the following in my PRI context: exten => _734XXX,1,Gosub(check_blacklist,s,1) exten => _734XXX,2,NoOP(Caller not blacklisted) exten => _734XXX,3,Gosub(get_name,s,1) exten => _734XXX,4,Goto(incoming,s,1) Doug -- Ben Franklin quote: "Those who would give up Essential Liberty to purchase a little Temporary Safety, deserve neither Liberty nor Safety." ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Treating T1 as trunk in/out, not individual lines
Ok..so how would the CALLED and CALLERID ID be presented to Asterisk when using PRI signaling. 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-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 PRI over T1 signaling, how would I pass the CALLED and CALLER info across the channels so each side knows what to do? Is there something in the PRI protocol you can point me to for figuring this out? Thanks, MD _ ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users That's what the D channel is for. A PRI is a primary rate ISDN. B channels carry voice, D channel handles the information & signalling in ISDN. Lyle ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
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 PRI over T1 signaling, how would I pass the CALLED and CALLER > info across the channels so each side knows what to do? Is there > something in the PRI protocol you can point me to for figuring this out? > > Thanks, > MD > > > ___ > --Bandwidth and Colocation Provided by http://www.api-digital.com-- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: >http://lists.digium.com/mailman/listinfo/asterisk-users That's what the D channel is for. A PRI is a primary rate ISDN. B channels carry voice, D channel handles the information & signalling in ISDN. Lyle ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
