We have issues with keeping D-channel up on a trunk group between G3si-v11 and our Predictive Dialer.
Using 2-TN767E Circuit cards and signaling as follows:
Signaling Mode: ISDN PRI
Connect: PBX
Interworking Message: Progress
Line Coding: b8zs
Frame Mode: esf
Interface: network
Protocol Version: a
idle code: 11111111
DCP/ANA Bearer Capability: 3.1 KHZ
Slip Detection: N
Near End CSU: Other
Send ANSI - T1.403: N
Far-End CSU Address: b
--------------------------
The D-channel goes out and displays error codes 1793, 257
The DS1 board shows errors: 1301 aux 1301; 3329 aux 17; 2305 aux 17
----------------------------------------------
The Dialer techs thinks it is the PBX causing the issue, the PBX vendor says it's dialer causing the issue. I am trying to find a solution. TO me it seems like the Dialer is the source of the problem. The only way I can find to bring back the d-channel is to re-boot the Dialer. This only lasts a day or two until another reboot is required.
Any suggestions on finding a solution?
Using 2-TN767E Circuit cards and signaling as follows:
Signaling Mode: ISDN PRI
Connect: PBX
Interworking Message: Progress
Line Coding: b8zs
Frame Mode: esf
Interface: network
Protocol Version: a
idle code: 11111111
DCP/ANA Bearer Capability: 3.1 KHZ
Slip Detection: N
Near End CSU: Other
Send ANSI - T1.403: N
Far-End CSU Address: b
--------------------------
The D-channel goes out and displays error codes 1793, 257
The DS1 board shows errors: 1301 aux 1301; 3329 aux 17; 2305 aux 17
----------------------------------------------
The Dialer techs thinks it is the PBX causing the issue, the PBX vendor says it's dialer causing the issue. I am trying to find a solution. TO me it seems like the Dialer is the source of the problem. The only way I can find to bring back the d-channel is to re-boot the Dialer. This only lasts a day or two until another reboot is required.
Any suggestions on finding a solution?