<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
The same as any other zap channel does. That is part of the magic of
the zaptel drivers.<br>
<br>
Lyle<br>
<br>
Michelle Dupuis wrote:
<blockquote cite="mid002a01c8189d$553d1e20$65fe1fac@ocg.ca" type="cite">
<meta http-equiv="Content-Type" content="text/html; ">
<meta content="MSHTML 6.00.6000.16544" name="GENERATOR">
<div dir="ltr" align="left"><span class="687052813-27102007"><font
color="#0000ff" face="Arial" size="2">Ok..so how would the CALLED and
CALLERID ID be presented to Asterisk when using PRI signaling.</font></span></div>
<div dir="ltr" align="left"><span class="687052813-27102007"></span> </div>
<div dir="ltr" align="left"><span class="687052813-27102007"><font
color="#0000ff" face="Arial" size="2">Mike</font></span></div>
<br>
<blockquote
style="border-left: 2px solid rgb(0, 0, 255); padding-left: 5px; margin-left: 5px; margin-right: 0px;">
<div class="OutlookMessageHeader" dir="ltr" align="left"
lang="en-us">
<hr tabindex="-1"> <font face="Tahoma" size="2"><b>From:</b>
<a class="moz-txt-link-abbreviated" href="mailto:asterisk-users-bounces@lists.digium.com">asterisk-users-bounces@lists.digium.com</a>
[<a class="moz-txt-link-freetext" href="mailto:asterisk-users-bounces@lists.digium.com">mailto:asterisk-users-bounces@lists.digium.com</a>] <b>On Behalf Of </b>Lyle
Giese<br>
<b>Sent:</b> Friday, October 26, 2007 5:54 PM<br>
<b>To:</b> Asterisk Users Mailing List - Non-Commercial Discussion<br>
<b>Subject:</b> Re: [asterisk-users] Treating T1 as trunk in/out,
not individual lines<br>
</font><br>
</div>
Michelle Dupuis wrote:
<blockquote cite="mid002f01c81814$69b7e0d0$65fe1fac@ocg.ca"
type="cite">
<meta content="MSHTML 6.00.6000.16544" name="GENERATOR">
<div><font face="Arial" size="2"><span class="938410621-26102007">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.</span></font></div>
<div><font face="Arial" size="2"><span class="938410621-26102007"></span></font> </div>
<div><font face="Arial" size="2"><span class="938410621-26102007">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?</span></font></div>
<div><font face="Arial" size="2"><span class="938410621-26102007"></span></font> </div>
<div><font face="Arial" size="2"><span class="938410621-26102007">Thanks,</span></font></div>
<div><font face="Arial" size="2"><span class="938410621-26102007">MD</span></font></div>
<pre wrap=""><hr size="4" width="90%">
_______________________________________________
--Bandwidth and Colocation Provided by <a class="moz-txt-link-freetext"
href="http://www.api-digital.com">http://www.api-digital.com</a>--
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
<a class="moz-txt-link-freetext"
href="http://lists.digium.com/mailman/listinfo/asterisk-users">http://lists.digium.com/mailman/listinfo/asterisk-users</a></pre>
</blockquote>
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.<br>
<br>
Lyle<br>
<br>
</blockquote>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
--Bandwidth and Colocation Provided by <a class="moz-txt-link-freetext" href="http://www.api-digital.com">http://www.api-digital.com</a>--
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
<a class="moz-txt-link-freetext" href="http://lists.digium.com/mailman/listinfo/asterisk-users">http://lists.digium.com/mailman/listinfo/asterisk-users</a></pre>
</blockquote>
<br>
</body>
</html>