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 derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Lan CTE on remote/BSR /2004/PC

Status
Not open for further replies.

Phonedaddy

Technical User
Oct 6, 2007
68
US
I'm trying to get Lan CTE working on an extension that was moved from the local office as a digital set T7316e with a working setup of Lan CTE/dialling from Outlook via contacts,machine name and ext 2001.
Internally the BCM is 172.18.1.201 and this is what I get when using ctebcmid in cmd prompt from remote PC. Now that this phone has been moved offsite using a BSR, a 2004 phone is working fine as far as making/receiving calls and VM and the PC can communicate with the home office via the tunnel in the BSR. At this same location from my laptop and softphone, I can use PCM and call other staions internally or through the DID/target line. The 2004 phone can be called using its target line but not by dialling its ext number directly using PCM, it returns a reorder tone.

Does anyone have any experience with using the BSR/IPphone/Lan CTE on a 400

I guess my first step needs to be getting the PCM to work at least, hopefully the Outlook contacts issue will fall into place after that.
 
Is the lan CTE configured using pc names or ip addresses and was this altered to reflect the change when the PC was moved ?

If its not broke tweak it..
 
The laptop she is using was originally configured locally using PC name .When we deployed this machine to the remote location, I tried connecting using the same machine/ PC name and had no luck. My laptop was able to use machine name locally and remotely, but not hers. So I changed hers to look at IP and still no luck. I also went through the tedious process of rebooting her machine after each change.

Would assinging static IP's to all the devices on the remote network in the 192.168 range work better talking to the systems local network (172.18.1.XXX), rather than using PC names and having to go through the DNS for name resolution?

 
Worth a try, I had a similar problem and it was fixed using IP addresses and not PC names, it was something to do with the BCM not being able to resole the PC name when the Lan cte client connected

also disable the firmware on the PC while testing just in case that's causing problems..

I always test my lan cte with this program first, sometimes the tapi does not show up in outlook


If its not broke tweak it..
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top