<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2743.600" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2><FONT face="Times New Roman" size=3>> > >
pri show span 1<BR>> ><BR>> > pri show span 1<BR>> > Primary
D-channel: 24<BR>> > Status: Provisioned, Down, Active<BR>><BR>> The
"Down" indicates the d-chan is down. Call Verizon and have them<BR>> activate
it. (Its not uncommon for telco's to deactivate the d-chan<BR>> when a
circuit hasn't been fully turned up. It reduces the number of<BR>> alarms
they have to deal with.)<BR><BR>Aha! That would make sense. We
ordered the PRI a while back for a new<BR>office space, but construction was
delayed, and it has been sitting idle for<BR>more than a month.<BR><BR><BR>>
> zapata.conf:<BR>> > switchtype = national<BR>> > context =
incoming<BR>> > signalling = pri_cpe<BR>> > group = 1<BR>> >
channel => 1-23<BR>><BR>> In the above for US-based PRI's, you'll want
to add:<BR>> pridialplan=unknown<BR>> echocancel=yes<BR>>
echotraining=yes ; try =800 if there is still echo with =yes<BR>>
echocancelwhenbridged=yes<BR>><BR>> The pridialplan= statement essentially
tells the Verizon switch<BR>> what type of dialplan you expect to use.
'unknown' allows you to<BR>> send 7 digits, 1+ 10 digits, etc. 'national'
restricts international<BR>> long distance, while 'international' imposes
other restrictions.<BR>> The added zapata.conf parameters are not the cause
for your d-chan<BR>> being down, however after that issue is resolved you'll
bump into<BR>> these parameters.<BR>><BR>> After the above items are
resolved and things are closer to working,<BR>> you'll need to know how many
digits (if any) Verizon is going to be<BR>> sending to you for inbound calls.
If you asked them to provide DID<BR>> numbers, then the number of digits
received will become important<BR>> for you to define extensions.conf entries
associated with your<BR>> context=incoming statement above. If they send you
4 digits, then<BR>> use extension.conf test entries like:<BR>>
[incoming]<BR>> include => valid-did<BR>> include =>
invalid-did<BR>><BR>> [valid-did]<BR>> exten =>
1234,1,Goto(local-extns,1234,1)<BR>> exten =>
1235,1,Goto(local-extns,1235,1)<BR>><BR>> [invalid-did]<BR>> exten
=> _.,1,Answer<BR>> exten => _.,2,Wait(1)<BR>> exten =>
_.,3,Playback(the-number-u-dialed)<BR>> exten =>
_.,4,Playback(not-yet-assigned)<BR>> exten => _.,5,Wait(2)<BR>> exten
=> _.,6,Hangup<BR>><BR>> You will also want to talk to a Verizon switch
tech about how to<BR>> handle outbound CallerID. E.g., do you want to send
CallerIDNum to<BR>> Verizon matching each originating DID number, or, map all
outbound<BR>> calls to a single CallerIDNum? They will also set a
common<BR>> CallerIDName for all outbound calls, but probably won't allow
you<BR>> to send the name to them.<BR><BR>Wow, a wealth of information!
Thanks, Rich, for all the dialplan and echo<BR>cancel stuff. I
certainly would not have thought to cover invalid DID'd or<BR>outbound
CallerID! This will save me a GREAT deal of time (which is<BR>suddenly a
huge premium for
me).<BR><BR>Thanks,<BR>Noah</FONT><BR><BR><BR></FONT></DIV></BODY></HTML>