ktruk Report post Posted 03/06/2007 03:55 PM Hi, I am using E1 line to make calls to TAPI VG on Win Server 2003 and an Eicon PRI (V2) Card. running ComISDN as the CAPI<>TAPI bridge/driver. Calls are only answered on "Line2" of the PRI card. I wonder, is the Line1 reserved in some way? I have looked the VG start-up log and get 30 channels listed as "Tapi" and then 30 channels listed as ISDN lines (via ComISDN), eg: (see file attached: vg-pri1.txt bit of start-up log): 110137.72 0 init InitClear start 110137.80 0 ----------------------------------------- 110137.81 0 VoiceGuide TAPI v5.2.5047 110137.81 0 ----------------------------------------- 110138.09 0 ApiMode=[TAPI] 110138.13 0 tapi device 82 is: ISDN Line 5 Channel 30 110138.16 0 tapi device 81 is: ISDN Line 5 Channel 29 110138.16 0 tapi device 80 is: ISDN Line 5 Channel 28 110138.17 0 tapi device 79 is: ISDN Line 5 Channel 27 ... 110138.21 0 tapi device 61 is: ISDN Line 5 Channel 9 110138.21 0 tapi device 60 is: ISDN Line 5 Channel 8 110138.21 0 tapi device 59 is: ISDN Line 5 Channel 7 110138.22 0 tapi device 58 is: ISDN Line 5 Channel 6 110138.22 0 tapi device 57 is: ISDN Line 5 Channel 5 110138.22 0 tapi device 56 is: ISDN Line 5 Channel 4 110138.22 0 tapi device 55 is: ISDN Line 5 Channel 3 110138.22 0 tapi device 54 is: ISDN Line 5 Channel 2 110138.23 0 tapi device 53 is: ISDN Line 5 Channel 1 110138.23 0 tapi device 52 is: ISDN Line 4 Channel 2 110138.23 0 tapi device 51 is: ISDN Line 4 Channel 1 110138.23 0 tapi device 50 is: ISDN Line 3 Channel 2 110138.24 0 tapi device 49 is: ISDN Line 3 Channel 1 110138.24 0 tapi device 48 is: ISDN Line 2 Channel 2 110138.24 0 tapi device 47 is: ISDN Line 2 Channel 1 110138.24 0 tapi device 46 is: ISDN Line 1 Channel 2 110138.25 0 tapi device 45 is: ISDN Line 1 Channel 1 110138.25 0 tapi device 44 is: H323 Line 110138.25 0 tapi device 43 is: IPCONF LINE 110138.25 0 tapi device 42 is: LPT1T 110138.25 0 tapi device 41 is: WAN Miniport (L2TP) 110138.26 0 tapi device 40 is: Eicon ISDN Channel 110138.26 0 tapi device 39 is: Eicon ISDN Channel 110138.26 0 tapi device 38 is: Eicon ISDN Channel 110138.26 0 tapi device 37 is: Eicon ISDN Channel 110138.27 0 tapi device 36 is: Eicon ISDN Channel 110138.27 0 tapi device 35 is: Eicon ISDN Channel 110138.27 0 tapi device 34 is: Eicon ISDN Channel 110138.27 0 tapi device 33 is: Eicon ISDN Channel 110138.28 0 tapi device 32 is: Eicon ISDN Channel 110138.28 0 tapi device 31 is: Eicon ISDN Channel 110138.28 0 tapi device 30 is: Eicon ISDN Channel 110138.28 0 tapi device 29 is: Eicon ISDN Channel 110138.28 0 tapi device 28 is: Eicon ISDN Channel ... 110138.33 0 tapi device 9 is: Eicon ISDN Channel 110138.33 0 tapi device 8 is: Eicon ISDN Channel 110138.33 0 tapi device 7 is: Eicon ISDN Channel 110138.34 0 tapi device 6 is: Eicon ISDN Channel 110138.34 0 tapi device 5 is: Eicon ISDN Channel 110138.34 0 tapi device 4 is: Eicon ISDN Channel 110138.34 0 tapi device 3 is: Eicon ISDN Channel 110138.34 0 tapi device 2 is: Eicon ISDN Channel 110138.35 0 tapi device 1 is: RAS VPN Line 0 110138.35 0 tapi device 0 is: RAS PPPoE Line0000 110138.36 0 init vgmulti ver 5.2.5047 So, any idea why it only answers calls starting on channel 2? If I specify channel 1 as a selected TAPI line, it just gets ignored, so all calls to the card start being answered from channel 2 only. Could it be that channel 1 is reserved as a timing channel? If so, why only 30 channels listed in the VG TAPI device list? (the pri line is coming from a local PABX, not a live public circuit or exchange) and I only have (at the moment) an 8 line license, so I can't test more than 8 lines. Any ideas? Thanks! vg_pri1.txt Share this post Link to post
SupportTeam Report post Posted 03/06/2007 08:49 PM If you see VoiceGuide answering calls on line 2 it would be because the calls have been presented to it on that line. You should look at the ComISDN driver to determine why it is presenting calls on that channel. Share this post Link to post
ktruk Report post Posted 03/06/2007 10:20 PM Okay, thanks. I already asked ComISDN, they commented that they just use the CAPI channel controller assigned by the driver. So, if I am using Eicon CAPI driver, your comment suggests that the source of the problem is there. I know that CAPI is not your strongpoint, but from what you know about TAPI, Please confirm its the TAPI hardware driver that matches TAPI line/device/channels to the hardware, and that VG just uses whatever TAPI lines it is given when it asks the OS/Hardware to list the available TAPI devices. If this is the case (as it surely must be) then it looks like the "TSP" or the hardware is wrong! Share this post Link to post
SupportTeam Report post Posted 03/06/2007 11:51 PM Please confirm its the TAPI hardware driver that matches TAPI line/device/channels to the hardware, and that VG just uses whatever TAPI lines it is given when it asks the OS/Hardware to list the available TAPI devices.That's correct. Why have you selected the Eicon brand card instead of a Dialogic D/300 card? Share this post Link to post
ktruk Report post Posted 03/08/2007 09:42 PM Okay - Thanks. Eicon is Dialogic !! ;-) But really: Originally I wanted ISDN BRI solutions and to provide PABX interfaces over BRI - S0 bus. Now I have Eicon PRI connecting/bridging over to Eicon BRI - its really neat, apart from odd teething niggles, like the one above. The Eicon Card drivers are lot more compact and easy to work with, the setup/install is trouble-free, less complex and a lot more elegant. No tone/disconnect issues, fast setup/disconnect time and cards at a reasonable price. Support you can actually talk to, need I go on? Share this post Link to post
