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!

Teleworker 1

Status
Not open for further replies.

Mitelpassion

IS-IT--Management
May 2, 2005
1,153
ZA
Hi,

I am running the latest release of Teleworker and release 5.2.6.8 on my 3300 ICP controller. The problem I have is one way audio. I know that there could be a few reasons for this.

The question I have is once a call is established, do the phones on the "inside" of the teleworker communicate with the Teleworker phone via the Teleworker server or do they use their own path to get the the Teleworker phone?

I did a tcpdump on the Teleworker server and I can see the packets from the Teleworker phone coming in, but never do I see any packets from phones, or the controller go out through the Teleworker server.

Any ideas on how this should work?
 
this sounds like a firewall problem.

one way on the teleworker is always down to firewall config.
 
can anyone confirm if the local sets stream their audio vial the Teleworker or via it's own gateway address.

The Teleworker server is running in server-only mode, sits in a DMZ with a internal non-routeable IP address.

E
 
The audio gets streamed via their own gateway i believe. The Docs dont really explain this and this has tripped us up a few times when giving firewall details to customers, they then have to open more ports direct from the voice lan to the outside world. The docs give you the impression its all thru the teleworker
 
The Teleworker Server (software blade loaded onto a MAS6000) streams the audio and signally to and from the ICP. There is not a direct connection between a IP phone deployed as a teleworker and the ICP (hence, you wouldn't need a MAS6000 or the teleworker server).

Does your tele-worker phones actually connect to the office (i.e. do you see the time and date)?
 
Yes,

The Teleworker phone does connect. All the features are available and yes the time and date shows.

The problem I have is one way audio.
After reading through the docs I can only guess that the phones, internal on the LAN, does infact stream throught the Teleworker, but because it's in server-only mode it streams through the external IP address on the firewall.

So both are correct. The phones use the firewall as their gateway but stream throught the teleworker. This sound complex cause it is.
Tilf, did you deploy the server in server-only mode?


 
Yes, this is where I think the docs aren't clear enough, we've had customers follow these to the letter and still have to open extra ports

 
From the Manual
===============
Note: You must configure LAN UDP ports 1024 and greater to reach the public IP address of the Teleworker server, or one-way audio problems will result. (See Firewall Configuration Tips for more information.) See the Teleworker Engineering Guidelines for more details about firewall rules.

Do you require more information on this subject? Please advise!
 
I have read this and it has also been configured.

I am looking for any additional info.

Regards,
Eugene
 
I have been at this now for over 3 weeks. I am now going to try and deploy the server in gateway mode. I have done several installations like this.

I just need to find out why this is not working. Does anyone have additional info or documentation that does not appear on MOL. Maybe something that got given to anyone by a senior Mitel tech????

My real problem is that I can't find enough detailed information (granular level) on how Teleworker works. The documentation provided is more a "howto do" than a "how it works" if you know what I mean.

Thanks for the input so far guys.
 
Had a similar problem myself (a few times) - it generally seems to be due to the fact that everything (3300 and teleworker handsets) all talk to the external address of the MAS. This causes problems with many firewalls (because they do not like IP spoofing). So the firewall sends the packets from the 3300 out of the 'www' port an not out of the DMZ port - hope that makes sense. The fix I have started using is to always spec a PIX515E DMZ because this can be configured to route the external MAS address to the DMZ without too much of a problem.
 
thanks for the info. I assumed that it was a firewall problem but couldn't fix it.

I just installed the teleworker in server-gateway mode and all is well.

Must admit though I still don't understand how the packet flow works on the Teleworker. I have read the documentation but get confused when trying to "apply" what I have read.

E
 

I can sympathise with the hassle factor.

Instead of the Teleworker/MAS6000 I use a Cisco 831 secure VPN router at each remote client location (abt $400 per site)
The 831 also allows secure split-tunnelling so you can send the voice traffic one way (via the tunnel to the office) and send your internet/surfing/email traffic to the greater internet without going through the office network to get there.
Inbound traffic from either tunnel cannot traverse the router to go back out the other tunnel.

Teleworker not required and no instrument limitation either.
The client can use literally any IP set that the 3300 (or 200) supports.
It is required that you hard-code the address of your ICP and TFTP address in the phone, but that's pretty easy.

 
We weren't trying to beat anyone out of a sale, goodness knows the Teleworker is cheap enough.
We were just trying to come up with a simple solution that did not require adding a server or require battling w/my IT dept about opening ports.

No argument this approach is more costly, essentially doubling the cost of each deployment, but so far it seems pretty much hassle free and with it I'm able to give the client any phone, including a 5201 (not that I ever would).

But another reason for the router approach was that we have both Mitel 3300 and Cisco CM in the same shop.
Ergo we can send the client home with either a Mitel or a Cisco phone and you can't do that w/Teleworker.
 
This works for me ,i put a policy on my firewall from internal to external , from all my lan to the real ip address of the mas6000 and voila ¡
tanx to themitelguy



From the Manual
===============
Note: You must configure LAN UDP ports 1024 and greater to reach the public IP address of the Teleworker server, or one-way audio problems will result. (See Firewall Configuration Tips for more information.) See the Teleworker Engineering Guidelines for more details about firewall rules.

Do you require more information on this subject? Please advise!
 
beleive me, I followed the installation to the book. we even tried it with no port restriction whatsoever.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top