no line pickups in TAPI drop down menu 1

[leprechaun3]

Ihave a BCM 2.5......I have downloaded clients LAN CTE AND PERSONAL CALL MANAGER...DO NOT NEED TAPI BECAUSE THE PC IS RUNNING XP....WHEN I GO TO TOOLS and (dial using), the drop down menu does not display any line numbers on the bcm 2.5...all it displays is h323,winport,lpt1 and so on....any suggestions.

 

[leprechaun3]

The TSP service still shows initializing. When I select diagnose this is what I get:

12:33:13.375 [CteApi.dll:4.]RpcRegisterRemoteCteApi: RPC error 1722: The RPC server is unavailable.

12:33:13.375 [EnterpriseEdge.tsp:4.][TSP](2) mbRegisterApplication failed with rc=0x00e1
12:33:13.375 [EnterpriseEdge.tsp:4.][TSP](1) TspStartupLoopProcessThread() : looping waiting for InitializeAccessConnection() or shutdown.
12:33:34.625 [EnterpriseEdge.tsp:4.][TSP](2) DLL_THREAD_ATTACH

Resources/LAN CTE shows licenses registered but none in use.
LAN CTE installation, I used LAN1 address and port #
IP address and machine name and dn are entered.

Any suggestions?

 

[3Sixty]

Hi leprechaun3

What is the IP address of Lan 1?
What is the IP address of the PC?
What is the operating system?
What is the published IP address of the BCM lan 1 or lan 2?

The fact the TSP service is still initializing means that you have not got connectivity between the PC and the BCM.

I would check the published IP address of the BCM and make sure you put in the published ip address of the bcm in the TSP client.

I would also check the service is working on the BCM.

 

[leprechaun3]

THKS mrmarshall .... I will chk these settings.....

 

[leprechaun3]

LAN 1 =10.1.10.4:6800
PC=10.1.3.106 RUNNING XP
PUBLISHED IP IS LAN 1

I can ping the bcm and access the management interface from this PC. I have disabled fire wall and proxy.

 

[3Sixty]

Hi leprechaun3

What is the subnet on your LAN 255.255.0.0?

What is the next hop router of the BCM?

Are you on the same LAN?

 

[joverly]

I have the same issues.. 20 machines work fine, 2 or 3 don't. I can reinstall and they will work for a few weeks, then suddenly stop. Uninstall/Reboot/Re-install and the line selection is not available. Sometimes it will just pop-up as a selection for no apparent reason. The client shows connected and initialized. Can ping the published IP just fine. XP sp1, Office XP, BCM 3.6. All the PCs are identical and connected the exact same way. I have been fighting this for months. No firewall between the PC and the BCM, windows firewall is OFF.

Shows In Service TSP 6.6.1.60.A.0 Switch Type T1 GLB 3.6 CTI Device CTI. Client is set in the BCM, 16 Licenses, 12 show In-Service.

Tried the Personal Call Manager. The Line does not show up in there as a availble selection either.

 

[joverly]

... this is occuring over 3 seperate BCMs at 3 different locations. The 20 that work are spread out among the 3 (48 licenses total). I have 1 or 2 "problem" PCs at each location.

 

[3Sixty]

What patches have you got on your BCM?

I have seen this problem on heavy utilised systems but not on small systems like the one you are talking about. I have a site with 110 users and we had to upgrade the ram to smooth out the issues with the customers loosing the extension on PCM.

 

[joverly]

Mrmarshall... I assume you are replying to mine. I don't want to hijack anyone's thread..

2 are 3.6 with all patches up and not including core 1. One is all patches up to and including core 1. I have not installed the core 2 patch yet as I saw mention of VoIp trunks getting wiped out afterwards.

The largest of the three is 30 users. 2 are on 400's, the smallest office (8 users) is on a 200. They will go for weeks just fine and then out of the blue start dropping like flies. The specific PC I have been working on has been a problem since day one. We even changed out PCs. I just tried putting him on a statis IP and changing Lan CTE auth to IP based. Uninstall/ clean registry/ reinstall. Same results.

We went through Nortel support once on this and they had an odd response. They don't support the LanCTE client. If things work via the Personal Call Manager (which they don't) then there is nothing they will do.

It really appears to be a DLL issue and it not registering properly. I am going to chase down this..

 

[3Sixty]

Yeah I think PCM is a demo platform of what can be done the PCM seems very much an after thought. I have not had any probs with VOIP trunks but I would always do a backup before any patch or upgrade.