remote 5312

[wil]

i have a 5312 connected to 5000, set it up for teleworker phone and it went through
and downloaded like normal phone's then after reboot it went to contacting server.Any one know
what i am missing here?

[ralph]

Do you have any phones working in teleworker mode?
If this is the 1st one then I would bet you don't have all the ports open.

Ralph

[wil]

yes it's the first one. I sent a list of ports to open to the network admin is this the right ports..3998-3999 TCP
 
 
 
 5004-5007 UDP Range
 
 5060 UDP
 
 5566 TCP
 
 5567 UDP
 
 5570 TCP
 
 6004-7039 UDP Range
 
 6800-6802 TCP Range
 
 20001 UDP
 
 50098-50508 UDP Range

[NTEDave]

Have you set the system NAT IP address to the external IP address you are using?

[wil]

yes sir, nat addy was 255.255.xxx.xxx changed to same addy i use for tw phone..

[acejavelin]

Don't forget you have to change the System NAT address in TWO places... IP Settings and Settings-Devices & Feature Codes-IP Connections-Pxxxx-NAT IP Address and you have to go into the set and change the NAT type as well.

Here is my super quick handy guide to remote IP phones on the 5000:

Here is the "official" tech bulletin on what to port forward for IP phones remotely, slightly dated but should still be applicable. https://dl.dropbox.com/u/95033600/Intertel%205000%20NAT%20Port%20Forwarding.pdf there are a wide variety of ports/ranges  you need to open up and map to the 5000's internal IP address.

Remember you need to set the public IP address in the 5000 in TWO places, first in System-IP Settings-System NAT IP Address and secondly in Settings-Devices & Feature Codes-IP Connections-Pxxxx-NAT IP Address. The only other thing you will have to do is go into each endpoint that is remote and under IP Settings of each individual endpoint change the NAT Address Type from Native (or Auto) to NAT. Also, although this won't effect phones connecting, if bandwidth is an issue you might want to use the Remote Call Configuration and apply it to the remote endpoints, basically all this does is force the phones to use G.729 instead of G.711, lowering their bandwidth requirements, and quality slightly, for audio.

Once those are in place, factory default the phone itself, make sure it is on a network that will provide it DHCP and power up and put the phone in Teleworker Mode to the public IP address with the port fowarding to the 5000.

That is it, there is no special magic or trick to make it work... I have connected literally hundreds of phones, both Mitel IP phones and the original Inter-Tel IP endpoints, in this way and had no issues for the most part. Occasionally I have run across routers (or configurations in routers) on the remote end that are too locked down to allow the phones to connect, but this is extemely rare and can usually be corrected by letting the network administrator know what port ranges you are using.

[wil]

thank you for info. i followed the 2. one system is 5.1. still didnt come up i need get intouch with the it department for the location
and make sure they open ports up, and did the nat. thanks for your help. will let you know how turns out..

Thanks again

[wil]

ok here is update, this is what i have open, per the network admin. and phone still say's contacting server.
could be a bad phone? was brand new out box?
access-list outside_access_in extended permit udp any any eq sip log warnings
 
access-list outside_access_in extended permit tcp any any range 3998 3999 log warnings
 
access-list outside_access_in extended permit udp any any range 5004 5007 log warnings
 
access-list outside_access_in extended permit tcp any any eq 5566 log warnings
 
access-list outside_access_in extended permit udp any any eq 5567 log warnings
 
access-list outside_access_in extended permit tcp any any eq 5570 log warnings
 
access-list outside_access_in extended permit udp any any range 6004 7039 log warnings
 
access-list outside_access_in extended permit tcp any any range 6800 6802 log warnings
 
access-list outside_access_in extended permit udp any any eq 20001 log warnings
 
access-list outside_access_in extended permit udp any any range 50098 50508 log warnings
 
static (inside,outside) 173.12.149.xxx Mitel netmask 255.255.255.255
also went into programming and change the nat addy to the external and set the phone for nat under the end point ip settings.

[sarond]

access-list outside_access_in extended permit udp any any eq sip log warnings
access-list outside_access_in extended permit tcp any any range 3998 3999 log warnings
access-list outside_access_in extended permit udp any any range 5004 5007 log warnings
access-list outside_access_in extended permit tcp any any eq 5566 log warnings
access-list outside_access_in extended permit udp any any eq 5567 log warnings
access-list outside_access_in extended permit tcp any any eq 5570 log warnings
access-list outside_access_in extended permit udp any any range 6004 7039 log warnings
access-list outside_access_in extended permit tcp any any range 6800 6802 log warnings
access-list outside_access_in extended permit udp any any eq 20001 log warnings
access-list outside_access_in extended permit udp any any range 50098 50508 log warnings
static (inside,outside) 173.12.149.xxx Mitel netmask 255.255.255.255

If I understand correctly you have set your firewall rules but have you also programmed port forwarding using

ip nat inside source static tcp etc...

[wil]

 yes i belive the port forward is done. the phone connected to phone system and downloaded the files, but after the reboot instead of connecting and prompt me for pin, it sat at contacting server..

[sarond]

Do you have a very restrictive outgoing firewall? Could the M5000 be too restricted on outgoing access?
Maybe allowing TFTP to upgraded but stopping on other applications.

[wil]

yea not sure, suck's when you don't have access to the router/firewall i have to go
by what the IT department for the that company tells me..

[sarond]

yea not sure, suck's when you don't have access to the router/firewall i have to go
by what the IT department for the that company tells me..

I think we all have the same problem

[wil]

Just an update, problem was a bad phone.  go figure