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 Speech issue

Status
Not open for further replies.

wontwork

Technical User
Mar 15, 2004
181
GB
Hi,

Was wondering if anybody could help?
My issue is as follows:

We have 3300 running 5340 ip handsets and one analog extension and a teleworker solution with 5340 ip sets hanging off it.

My issue is that there is no speech at all when calling from the teleworker handset to either the 5340 ip sets or the analog phone on the 3300. The call connects fine but there is just no speech!
The 5340 ip sets and the analog phone on the 3300 can talk to each other fine it is only when calling from the 3300 to the teleworker when the problem occurs!

Does anybody know the correct ports which need to be opened up on the router in order to allow the speech?

Cheers


 
Is the teleworker on a different subnet than the 3300ICP?

If so, the problem is most likely in your teleworker server/6000MAS. Add the subnet of the 3300 to the Local Networks.
 
Yes the IP Addresses are as follows:

3300 = 192.168.42.100
Internal side of teleworker = 192.168.42.101
External side of teleworker = 192.168.0.253

We can ping everything from a PC on the 192.168.42.0 subnet and it's fine.
 
Check your manual for a full list of ports but check these - they cause one way audio and no audio issues if not forwarded correctly

UDP 20,000 to configured upper bound* (SRTP)
Server ? Internet
Server ? LAN
Voice Communications. Allow incoming SRTP on UDP ports 20000 – configured upper bound* from all streaming devices on the LAN and the Internet. Mis-configuration here is a common cause of one-way audio problems.

UDP 1024 to 65,535 (RTP)
Server ? LAN
Server ? Internet
Voice Communications. Allow outgoing SRTP on UDP ports greater than, or equal to, 1024 from the server to all streaming devices on the LAN and the Internet. Mis-configuration here is a common cause of one-way audio problems.
 
Is the other 3300 network in local networks on the TW
 
Hi M1tel,

I have already added the 3300 network in local networks on the TW.

I am using a Zyxel prestige 600 series router, has anybody got the TW working with one of these routers?

Cheers
 
Wontwork,

How about the network of the TW set. Is it in the local networks?





*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
 
Hi KwbMitel,

Yes i have got the network of the TW set in the Local networks but still no joy.

Really strange one! I think it is still a port issue even though i have opened all ports that it requires going by the Manual!
I have even tried allowing all ports through and turning the firewall off on the router but still to no avail.

Looking through the foram i can see a few people that have had one way audio but no-one that has had no audio at all!

Does anybody have any more ideas??

Thank you



 
One way or No way audio is usually a gateway issue at the set level. The controllers have the correct gateways obviously as the call is able to be set up. It is at the moment of answering that this fails, indicating a probable gateway issue on the handset.

Try using the set network debug tools to send pings directly from the set. These can be initiated at the set level or from teh 3300.



*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
 
It's a long time ago i've installed a Mitel's but this is a known problem


With the introduction of DSL pipes up to 4Mb there is a requirement to host 6010 servers behind a DSL broadband router. Most in-expensive DSL routers do not have true DMZ functionality and simulate this using port translation. This can cause one way speech with the teleworker solution.

An example set up is shown in the example below:-


DSL router:-

Public IP address 195.23.43.75 programmed into the DSL router. Internal address of DSL router 10.10.20.1. DMZ server address programmed as 10.10.20.2 with NAT enabled.

6010 Server:-

Server/Gateway mode with external address 10.10.20.2 (gateway 10.10.20.1) and internal address 10.10.10.1.

3100/3300:-

RTC/E2T ip address 10.10.10.10. Gateway 10.10.10.1.

Log into the 6010 server as root. Then type in the following commands:-

mkdir -p /etc/e-smith/templates-custom/etc/tug.ini

echo "udp_setside_address=[195.23.43.75]" > etc/e-smith/templates-custom/etc/tug.ini/15udp_setside_address

/sbin/e-smith/expand-template /etc/tug.ini

/sbin/e-smith/signal-event tug-update



Greetzzzz....Bas

y1pzZTEUdok1vrI5cLb3FdPX4PgTPlSONkb5WPjz0x50etSujaMSmhdRCbOx9vASnrRNzzXv0IxNQA

___________________________________________
It works! Now if only I could remember what I did...
___________________________________________
 
I also have a teleworker configured as server only mode with one way/no way audio. The 3300 and IP phones send thier udp packets to the external ip address which is blocked. I have tried to edit the 15udp_icpside_address and enter the internal address but they still reply to the external address.

Does anyone know how to change the teleworker so it makes the 3300 and Ip phones send responses back to the internal address?
 
Hornetswfc, you need to start your own post.

Wontwork gets notified of all posts here.



*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
 
Check on the teleworker what mode it is in...
On the lefthand side under configuration click on review configuration. IT should show Server Mode. Is it servergateway or server only.

If it's servergateway the problem is the router on your 192.168.0.x interface is blocking inbound udp traffic to your teleworker on ports greater than 19999.
 
Hi,

Is your External address dedicated to the Teleworker, I.e. Isn't used for SMTP collection etc.

Are you natting the outside address to the Inside address and vice versa?

Are you able to setup in server gateway mode as this often works much better? Put one Nic directly on an external address and the other nic on your voice vlan. Works a treat without issue.

It will be a router issue, it always is!.

 
Just reviewed your config further up, it looks like the External IP address is a private one? It needs to be a public one.

What is the external plugged into? Router ? modem or direct into the circuit?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top