Mitel 5000 - New user - Lots of questions - Please Be Gentle!!

[sarond]

Check your gateways normally it will be a routing issue if you have no/one way speech.
Sounds like your internal extensions gateway might be right but your system may be incorrect, are they the same?

[acejavelin]

Well finally got round to installing and testing this.   On trying it through the normal method we add the Mitel's to the system, previously defining ICP on the phone to the NAT address of the system, I continually got to DHCP then the error "Option 128 Missing".

So tried with the pressing 7 and putting the handset to teleworker mode, this worked fine, got an address from the system and applied the extension number.   So happy about that.

Yes, as you discovered the phones must be in Teleworker mode and have the IP address set properly, or they will fail with an "Option xxx missing" and not boot properly.

...You also need to make sure the System NAT address (ie. the public IP address of the router forwarding ports to the 5000) is set properly in TWO places:

System\IP Settings\System NAT IP Address
System\Devices and Feature Codes\IP Connections\P6000\NAT IP Address

And to finish it all off, on the remote phones themselves in:

System\Devices and Feature Codes\Phones\<Ext num>\IP Settings

Change the NAT Address Type to NAT.

Check these three settings... if they are all correct and you are getting one-way/no audio, it is a networking issue, ports not forwarded correctly or other settings. These are the three main ones you can control. The most common one I see is on the phone itself, changing the NAT Type.

[d95gas]

Thanks for the advice guys.

I have checked the two places on the Mitel;

System\IP Settings\System NAT IP Address
System\Devices and Feature Codes\IP Connections\P6000\NAT IP Address

Both settings have the same WAN IP address

on the remote phone have changed it to NAT

Router is a Draytek 2820 and have the open ports set as per the attachment:



Still no voice........


On the phone I have set the ICP to the WAN Address and in Teleworker mode given the WAN Address.

Thanks

Graeme

[sarond]

I know it's not ideal but you could temporarily put the Mitel in the DMZ to eliminate a port forward issue.
You don't have an expansion processor do you?

[d95gas]

put the phone in the DMZ, now when I dial from the Remote teleworker phone, I can hear the other end fine, but they cannot hear me.....Grrrrr frustrating :-)

[sarond]

I actually meant the phone system, try putting the system in the DMZ and see what happens.

[sarond]

Another thing to try is disabling SIP ALG on the router if it has an option.

[acejavelin]

put the phone in the DMZ, now when I dial from the Remote teleworker phone, I can hear the other end fine, but they cannot hear me.....Grrrrr frustrating :-)

Yes, DMZ the system and try again. This does appear to be a port forwarding issue.

[x-man]

You will HAVE to disable SIP Alg on the Draytek. You can only do this through the command line interface. I have  2830 here that works fine once you have SIP Alg turned off. BTW guys, on the Draytek opening the ports is all you need, it automatically punches them through the firewall for you.

[d95gas]

Okay guys, I have:

System on DMZ
the phone on the remote end on DMZ

Still only one way traffic I can hear them (system end) they cannot hear me (remote)

On the Draytek's on both ends, have checked sip_alg and both confirmed as disabled.

Both ends are running across ADSL and both have 6mb down and 512k up.  Currently no network issues, and the half of the call we do get is good quality.

Any more suggestions :-(


Thanks for your input.

[d95gas]

Just to confirm the "Open Ports" on the System end, we have probably gone to the extreme after scanning every tech document we could find, but we can always remove later once its working.   The following have been opened:





Also, ran Syslog on the remote end whilst making a call to the system end (192.168.1.202) the following is the result:

[x-man]

Have you checked the SIP Alg from the command line? My guess is still the SIP_Alg if its not been done from the command line.

[d95gas]

Have you checked the SIP Alg from the command line? My guess is still the SIP_Alg if its not been done from the command line.

Yep checked from command line and SIP_ALG is off on both ends.

[sarond]

mmm... thinking a bit differently now, do both Draytek routers support VPN.

Could you just setup a VPN between all sites?

Also looking at your port forwarding it looks like entry 6 is forwarding most UDP ports 6000 - 60000, is this your intent?

[d95gas]

mmm... thinking a bit differently now, do both Draytek routers support VPN.

Could you just setup a VPN between all sites?

Also looking at your port forwarding it looks like entry 6 is forwarding most UDP ports 6000 - 60000, is this your intent?

VPN was our next thought.   Entry No 6 was just a test.....If I recall, at the moment we are just trying to expand what we have to see if it has any effect.   Nothing we seem to do makes any difference.

when looking at the Syslog from the Draytek you can see when the call is made, starts off ok, but the second the call is answered the log is flooded with "User: 192.168.1.201 -> 192.168.3.10 (ICMP) Destination Unreachable"

both routers can ping each other with no problems.   And we thought by putting the phone and the system in the DMZ it would solve the problem.......but we were wrong again.

So now just banging heads against the wall!!!!!