Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Problem with Personal Call Manager & XP Professional

Status
Not open for further replies.

BizFoneGuy

Technical User
Aug 14, 2005
123
CA
I have a problem with trying to get Personal Call Manager to work on XP Professional(SP2)in a 2003 Server(SP1) environment. With either a 2.5 or 3.6 BCM it will not work. When personal call diagnostics are turned on this is what I get:

40c 12:42:05.571 [EnterpriseEdge.tsp:4.] [TSP](2) DLL_THREAD_ATTACH

40c 12:42:05.606 [EnterpriseEdge.tsp:4.] [TSP](2) DLL_THREAD_ATTACH

40c 12:42:05.677 [EnterpriseEdge.tsp:4.] [TSP](2) DLL_THREAD_ATTACH

40c 12:42:07.952 [EnterpriseEdge.tsp:4.] [TSP](2) DLL_THREAD_ATTACH

40c 12:42:09.392 [EnterpriseEdge.tsp:4.] [TSP](2) DLL_THREAD_ATTACH

40c 12:42:09.623 [EnterpriseEdge.tsp:4.] [TSP](x0008) InitializeAccessConnection: entered.

40c 12:42:09.623 [EnterpriseEdge.tsp:4.] [TSP](x0008) CTE 5.1 5.10.A.4

40c 12:42:09.730 [CteApi.dll:4.] API client created for ROUTER server "192.168.1.29"

40c 12:42:09.748 [CteApi.dll:4.] API server created on port wzcsvc

40c 12:42:09.748 [CteApi.dll:4.] API server created on port OLE8236C1D08B1342BB85554E7D3AF5

40c 12:42:09.748 [CteApi.dll:4.] API server created on port 1025

40c 12:42:09.766 [CteApi.dll:4.] API server created on port \PIPE\atsvc

40c 12:42:09.766 [CteApi.dll:4.] API server created on port AudioSrv

40c 12:42:09.766 [CteApi.dll:4.] API server created on port \PIPE\wkssvc

40c 12:42:09.766 [CteApi.dll:4.] API server created on port \pipe\keysvc

40c 12:42:09.766 [CteApi.dll:4.] API server created on port keysvc

40c 12:42:09.766 [CteApi.dll:4.] API server created on port \PIPE\srvsvc

40c 12:42:09.801 [CteApi.dll:4.] API server created on port \PIPE\SECLOGON

40c 12:42:09.801 [CteApi.dll:4.] API server created on port \PIPE\msgsvc

40c 12:42:09.801 [CteApi.dll:4.] API server created on port senssvc

40c 12:42:09.801 [CteApi.dll:4.] API server created on port \PIPE\browser

40c 12:42:09.801 [CteApi.dll:4.] API server created on port \PIPE\W32TIME

40c 12:42:09.801 [CteApi.dll:4.] API server created on port \pipe\trkwks

40c 12:42:09.837 [CteApi.dll:4.] API server created on port trkwks

40c 12:42:09.837 [CteApi.dll:4.] API server created on port srrpc

40c 12:42:09.837 [CteApi.dll:4.] API server created on port IcaApi

40c 12:42:09.837 [CteApi.dll:4.] API server created on port \pipe\Ctx_WinStation_API_service

40c 12:42:09.837 [CteApi.dll:4.] API server created on port tapsrvlpc

40c 12:42:09.837 [CteApi.dll:4.] API server created on port \PIPE\ROUTER

40c 12:42:09.908 [CteApi.dll:4.] API client terminated for ROUTER server "192.168.1.29"

40c 12:42:10.014 [CteApi.dll:4.] API server terminated on port wzcsvc

40c 12:42:10.014 [CteApi.dll:4.] API server terminated on port OLE8236C1D08B1342BB85554E7D3AF5

40c 12:42:10.014 [CteApi.dll:4.] API server terminated on port 1025

40c 12:42:10.032 [CteApi.dll:4.] API server terminated on port \PIPE\atsvc

40c 12:42:10.032 [CteApi.dll:4.] API server terminated on port AudioSrv

40c 12:42:10.032 [CteApi.dll:4.] API server terminated on port \PIPE\wkssvc

40c 12:42:10.032 [CteApi.dll:4.] API server terminated on port \pipe\keysvc

40c 12:42:10.032 [CteApi.dll:4.] API server terminated on port keysvc

40c 12:42:10.032 [CteApi.dll:4.] API server terminated on port \PIPE\srvsvc

40c 12:42:10.050 [CteApi.dll:4.] API server terminated on port \PIPE\SECLOGON

40c 12:42:10.050 [CteApi.dll:4.] API server terminated on port \PIPE\msgsvc

40c 12:42:10.050 [CteApi.dll:4.] API server terminated on port senssvc

40c 12:42:10.068 [CteApi.dll:4.] API server terminated on port \PIPE\browser

40c 12:42:10.068 [CteApi.dll:4.] API server terminated on port \PIPE\W32TIME

40c 12:42:10.068 [CteApi.dll:4.] API server terminated on port \pipe\trkwks

40c 12:42:10.086 [CteApi.dll:4.] API server terminated on port trkwks

40c 12:42:10.086 [CteApi.dll:4.] API server terminated on port srrpc

40c 12:42:10.086 [CteApi.dll:4.] API server terminated on port IcaApi

40c 12:42:10.103 [CteApi.dll:4.] API server terminated on port \pipe\Ctx_WinStation_API_service

40c 12:42:10.103 [CteApi.dll:4.] API server terminated on port tapsrvlpc

40c 12:42:10.103 [CteApi.dll:4.] API server terminated on port \PIPE\ROUTER

40c 12:42:10.121 [EnterpriseEdge.tsp:4.] [TSP](2) mbRegisterApplication failed with rc=0x0016

40c 12:42:10.121 [EnterpriseEdge.tsp:4.] [TSP](1) TspStartupLoopProcessThread() : looping waiting for InitializeAccessConnection() or shutdown.

40c 12:42:15.756 [EnterpriseEdge.tsp:4.] [TSP](2) DLL_THREAD_DETACH

40c 12:42:22.351 [EnterpriseEdge.tsp:4.] [TSP](2) DLL_THREAD_ATTACH

This process repeats over and over and the smaller diagnostics window shows PCM is initializing.

Any ideas would be greatly appreciated.
 
There is a thread regarding compatability issues with the tapi interface and windows xp service pack 2. Have you got another machine running a different OS you could try it on to confirm you have all of your settings right on the BCM. I am guessing when you check the status of the shuutle in the bottom corner on the taskbar you are not getting connected.I would also check windows has not enabled the firewall on your ethernet connection.

Marshall

 
We tried 2 different BCM's one with 2.5 and one with 3.6. Both had the same result. I took the 3.6 to another location where we set up 2003 & XP Professional and it worked fine but service pack 2 wasn't installed. We are going to add SP2 to that machine and see if it gets the same problem. If it does, how do you get around it?

Thanks Marshall.
 
As another follow-up, I've used my computer with XP Home Service Pack 2 with no problems on Personal Call Manager on the actual 3.6 machine I brought out on site. Unless it's just wirh XP Professional Service Pack 2?
 
XP PRO and service pack 2 is what's installed at the customer location. Is there a solution? Some people mentioned a Patch or is it resolved in later software revisions like 3.7? I can't believe it could be just left like this by Nortel in the predominance of XP PRO & SP2.

Any direction from anyone with experience on this would be greatly appreciated.

Thanks in advance!
 
In follow up to this, I have tried a BCH 1000 3.6 at two sites with XP PRO & SP2, no problem, Personal Call Manager works fine and Tapi service is up and running. Another site I cannot get it to work? Anybody else crossed this bridge?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top