qrss wrote:
Does anyone have any ideas? Any magic words to give to the people at
McLeod to get this running?
You might ask the carrier to take a careful look at the mapping for the
d-channel in their DACS equipment and perhaps even ask them to try
re-mapping it for you. If that does not get t
We have a McLeod T1 and they told us specifically that it was a PRI, ended up
being em_wink. Make sure they really have it setup right.
--
~Andy Brezinsky
On Friday 08 July 2005 5:45 pm, Kristian Kielhofner wrote:
> Hello everyone,
>
> We have recently turned up a new T1 from McLeod (Mid
>Does anyone have any ideas? Any magic words to give to the people at
>McLeod to get this running?
You might ask the carrier to take a careful look at the mapping for the
d-channel in their DACS equipment and perhaps even ask them to try
re-mapping it for you. If that does not get things moving,
Chris Shaw wrote:
**Snip**
pbx*CLI> pri show span 1
Primary D-channel: 24
Status: Provisioned, Down, Active
Switchtype: National ISDN
Type: CPE
Window Length: 0/7
Sentrej: 0
SolicitFbit: 0
Retrans: 0
Busy: 0
Overlap Dial: 0
T200 Timer: 1000
T203 Timer: 1
T305 Timer: 3
T308 Timer: 4000
T3
**Snip**
pbx*CLI> pri show span 1
Primary D-channel: 24
Status: Provisioned, Down, Active
Switchtype: National ISDN
Type: CPE
Window Length: 0/7
Sentrej: 0
SolicitFbit: 0
Retrans: 0
Busy: 0
Overlap Dial: 0
T200 Timer: 1000
T203 Timer: 1
T305 Timer: 3
T308 Timer: 4000
T313 Timer: 4000
N200
Hello everyone,
We have recently turned up a new T1 from McLeod (Midwestern CLEC). It
is configured like so:
/etc/zaptel.conf:
loadzone=us
defaultzone=us
span=1,0,0,esf,b8zs ;(also tried 1,1,0,esf,b8zs)
bchan=13-23
nethdlc=1-12
dchan=24
/etc/zapata.conf:
switchtype=national
context=pri-i