Specifications

Connecting the ISDN-Controller B1 PCI v4.0 to an Internal PBX Bus
60 ISDN-Controller B1 PCI v4.0 – 11 Special Types of Connections
signaled for outgoing calls is always configured directly
in the CAPI 2.0 application (such as FRITZ!) rather than
in the CAPI 2.0 driver. This is also the case for the sys-
tem drivers of the AVM Middleware product series, such
as the NDIS WAN CAPI Driver or the CAPI Port Driver.
Here the outgoing MSN must also be configured direct-
ly in the system drivers.
In many cases charge-calculation software provided by
the PBX manufacturers is also dependent on the signal-
ing of the correct MSN by the ISDN terminal device.
z The ISDN service indicator desired by the CAPI 2.0 ap-
plication (for example DATA64K, speech, 3.1 khz audio)
must be available for terminal devices at the corre-
sponding extension. This generally depends on the con-
figuration of the PBX software.
z If the ISDN-Controller or the CAPI 2.0 application using
the controller are to accept calls (from Dial-Up Network-
ing Servers or routers, for example), the extension must
also be configured for incoming calls. If multiple termi-
nal devices installed on the internal S
0
bus are config-
ured for the same ISDN service indicator (for instance, a
router and FRITZ!data in Server Mode both respond to
calls with the indicator “DATA64K”), the corresponding
application must use different MSN configurations to
direct calls correctly during parallel operation.
HB_B1V40-e.book Seite 60 Freitag, 24. September 2004 4:41 16