The BRI I've plugged into the PM2 worked fine on a Cisco & then on
an Ascend. It's only on the PM2 that it's not working right.
The symptom I see is that a call to the first DN on the BRI will come
in to B1 (S20, in this case) and work just beautifully. No problems
here.
The problem is when the SECOND person calls that DN. It will come
into the PM2 and the customer at the other end will get a 'call rejected'
indication.
If, instead, I have someone call the second DN on that BRI, it comes
in and the PM2 loves it.
I have tried variations with the same DN on both S20/S21, different DNs
on S20/S21, and no DN on S20/S21. I have also tried this with NI-1 and
5ESS as switch types. (It should be NI-1, but I'm trying everything).
If I look at the DEBUG ISDN-D, I see some very strange stuff. I suspect
that the PM2 is not putting everything out.
In the problem case, I see the call come in from the switch, asking for the
2nd BRI. The PM2 says that it then sends out a CONNECT. However, the
next thing that it gets back is a RELEASE COMPLETE from the switch, with
the cause code of "CALL REJECTED" (82 95). I don't believe the PM2; I
think that it is sending out a D-channel message but not reporting it.
Unfortunately, I don't have an ISDN protocol analyzer available.
So: has anyone in US West territory got this to work? I haven't even begun
to investigate the issue of hunting/forwarding from one BRI to the next.
I called Livingston tech support and the guy there seemed to think that
this was normal---they evidentally feel that this is normal behavior. He
says "well, you need to get your line provisioned differently." I suppose
that I could do that (although why if it works out-of-the-box with everyone
else?), but now I'm in the position of needing the correct magical
incantation for US West.
Anyone?
jms
Joel M Snyder, 1404 East Lind Road, Tucson, AZ, 85719
Phone: +1 520 324 0494 (voice) +1 520 324 0495 (FAX)
jms@Opus1.COM http://www.opus1.com/jms Opus One