> Just a shot in the dark but...
> Have you tried clearing out the DirectoryNumbers from the ISDN ports?
well, this is how the ports are configured:
> show s11
--------------------- Current Status - ISDN Port S10
------------------------
Status: IDLE
Input: 1402219 Abort Errors: 1
Output: 5934932 CRC Errors: 0
Pending: 0 Overrun Errors: 0
TX Errors: 0 Frame Errors: 0
Modem Status: DCD- CTS+ TELCO+ NT1+ Disconnect:
Active Configuration Default Configuration
-------------------- ---------------------
Port Type: Login/Netwrk Login/Netwrk (Dial In)
(Security)
Line Speed: 64000 64000
Terminal Type:
SPID: 20644793901111
Directory No:
Dial Group: 0
> show s11
--------------------- Current Status - ISDN Port S11
------------------------
Status: IDLE
Input: 0 Abort Errors: 0
Output: 0 CRC Errors: 0
Pending: 0 Overrun Errors: 0
TX Errors: 0 Frame Errors: 0
Modem Status: DCD- CTS+ TELCO+ NT1+ Disconnect: Call Rejected
Active Configuration Default Configuration
-------------------- ---------------------
Port Type: Login/Netwrk Login/Netwrk (Dial In)
(Security)
Line Speed: 64000 64000
Terminal Type:
SPID: 20644794451111
Directory No:
Dial Group: 0
----------------------------original message------------------------
> On Tue, 03 Dec 1996 11:35:23 -0800, you wrote:
> >I recently had my local phone company to put mu ISDN numbers into a hunt
> >group. It seems the hunting is working in a sense that the call is being
> >routed from s10 to s11, but the connection can not be established. I
> >have on my premises PM2-ER with ISDN card. On the other end I have 2
> >clients with Pipeline 130 and 75 respectively. When one of my clients
> >has established connection to s10 (published number) and the other
> >client tries to establish the connection, the call is rejected.