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

5610 IP phone not getting extension

Status
Not open for further replies.

YanN1ck

MIS
Sep 17, 2008
9
US
Hi,

We have a remote warehouse where we are trying to set up 5610 IP phone. We are connected through VPN between the warehouse and office (office uses Secure Computing firewall, warehouse uses Sonicwall firewall) I am able to use the IP phone in our office without any problems. When I plugged in the phone on our side, it connects to IP office, TFTP server, downloads configs fine but never accepts extension.
We have the following settings:
Local office
IP Office 406 v4: 192.168.21.220
TFTP: 192.168.21.221
Gateway: 192.168.21.254
Firewall: 192.168.21.1

2nd Warehouse:
5610 phone: 192.168.22.30
Gateway/firewall: 192.168.22.1

Under IP Routes we have:
IP Address: 0.0.0.0
IP Mask: 0.0.0.0
Gateway IP Address: 192.168.21.254

Does anyone have any suggestion why the phone cannot get extension from IP Office even though it connectes for configs?

Thanks a lot for all your help.


 
your main office seems to use the firewall as it's route which in turn is connected to the gateway.

Should your IPO not have the firewall as the route, i.e. 192.168.21.1, as this is your vpn tunnel?


If you still need to have a direct to .254 connection then put in a route .22.0 via .21.1.
 
Do I understand this corectly?
Add this IP Route:
IP Address: 0.0.0.0
IP Mask: 192.168.22.0
Gateway IP Address: 192.168.21.1

Thanks.
 
You need to set the gateway ipaddress to the router that makes the vpn connection
If that is your firewall with ipaddress 192.168.21.1 then yes :)


ACA - Implement IP Office
ACS - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
 
Look closely...the IP Address should be 192.168.22.0 and IP Mask should be 255.255.255.0.
 
You say "never accepts extension"

What precisely do you mean? While all the above is good, and you may need to revisit if you have speech path problems, I don't think it will resolve your problem.

Is "auto-create extension" and "auto create user" set on in the gatekeeper tab? If off (IMHO the correct setting is off), have you created both the extension and user. You need both to successfully register an extension - you don't get the NoUser Profile applied (on V4.1.15 at least)

Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.
 
On Gatekeeper Auto-Create Extn is on, Auto-create user is off.

I have an existing user created. We have created VoIP extension (Ext. ID 8002, base ext. 260, IP is set to 0.0.0.0, Auto compress, Gain: Default, H450 support: none, Allow Direct Media Path and Out Of Band DTMF are checked. It has worked fine within our office, just not between the buildings. I have added the route as mentioned above and I am going to check on the phone there. Will let you know if setting 21.1 worked.

Thanks.
 
Can you ping the ipoffice from the remote location ?

ACA - Implement IP Office
ACS - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
 
Yes, I can ping across fine and access servers on 21 network just fine. I just came back from the other warehouse. Phone still downloads settings files from TFTP but ends up sitting with Discover 192.168.21.220 (IP Office address) This shows on TFTP Log.
IP address: 192.168.22.0
IP Mask: 255.255.255.0
Gateway IP:192.168.21.1

This is from TFTP log:
Friday, November 14, 2008 2:30:45 PM : Sent 10% of 46xxupgrade.scr to 192.168.22.30:1025
Friday, November 14, 2008 2:30:45 PM : Sent 20% of 46xxupgrade.scr to 192.168.22.30:1025
Friday, November 14, 2008 2:30:45 PM : Sent 30% of 46xxupgrade.scr to 192.168.22.30:1025
Friday, November 14, 2008 2:30:45 PM : Sent 40% of 46xxupgrade.scr to 192.168.22.30:1025
Friday, November 14, 2008 2:30:45 PM : Sent 50% of 46xxupgrade.scr to 192.168.22.30:1025
Friday, November 14, 2008 2:30:45 PM : Sent 60% of 46xxupgrade.scr to 192.168.22.30:1025
Friday, November 14, 2008 2:30:45 PM : Sent 70% of 46xxupgrade.scr to 192.168.22.30:1025
Friday, November 14, 2008 2:30:45 PM : Sent 80% of 46xxupgrade.scr to 192.168.22.30:1025
Friday, November 14, 2008 2:30:45 PM : Sent 90% of 46xxupgrade.scr to 192.168.22.30:1025
Friday, November 14, 2008 2:30:45 PM : Sent 100% of 46xxupgrade.scr to 192.168.22.30:1025
Friday, November 14, 2008 2:30:46 PM : Sent 11% of 46xxsettings.txt to 192.168.22.30:1026
Friday, November 14, 2008 2:30:47 PM : Sent 22% of 46xxsettings.txt to 192.168.22.30:1026
Friday, November 14, 2008 2:30:47 PM : Sent 33% of 46xxsettings.txt to 192.168.22.30:1026
Friday, November 14, 2008 2:30:47 PM : Sent 44% of 46xxsettings.txt to 192.168.22.30:1026
Friday, November 14, 2008 2:30:47 PM : Sent 55% of 46xxsettings.txt to 192.168.22.30:1026
Friday, November 14, 2008 2:30:47 PM : Sent 66% of 46xxsettings.txt to 192.168.22.30:1026
Friday, November 14, 2008 2:30:47 PM : Sent 77% of 46xxsettings.txt to 192.168.22.30:1026
Friday, November 14, 2008 2:30:47 PM : Sent 88% of 46xxsettings.txt to 192.168.22.30:1026
Friday, November 14, 2008 2:30:47 PM : Sent 99% of 46xxsettings.txt to 192.168.22.30:1026
 
make sure that the ports 1719 and 1720 are not blocked for some odd reason because the settings file goes via port 69 the communication between the IPO and the phone use these different ports

Joe W.

FHandw., ACS

If you can't be good, be good at it!
 
I have checked with both firewall installers and VPN allows all the trafic (we use a couple of custom programs with nonstandard ports).
 
You are probably still being blocked by the firewall. Just because traffic is allowed doesn't mean that critical ports are unblocked. If there is a way to bypass the firewall from IPO to the destination then you will determine that the firewall is indeed blocking pretty quickly.

You could also set up wireshark on both ends and connect the IPO and ip phone to hubs instead of switches to gather the traffic. The traffic will typically stall at registration when there is a port blocking issue.
 
When it is in discovery, after a while you can press the *
Then look what ip address it has

I bet it has the wrong ipadres

Try to set it up maualy

callsv is the ipo
filesv is the tftp
router is your vpn gateway
mask is the subnet mask
Leave the rest default

ACA - Implement IP Office
ACS - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
 
In the IP extn config have you set an IP address for the Phone. If so, is it the same IP address as the Phone is set to??? If these do not match, then it will not register.

In the IP Extn form, leave the IP Address as 0.0.0.0. Then the IPO will accept a phone with any IP address.

Jamie Green

ACA:Implement - IP Office
ACS:Implement - IP Office

Football is not a matter of life and death-It is far more important!!!!
 
Yes, I can ping across fine and access servers on 21 network just fine.", including IPO?

You need to find out if it is a vpn/network/route problem. Do a HOLD CLEAR# on the phone - then program it statically as tlpeter says above. The phone should come back up with Enter Extension number. Enter a new extension number. If it doesn't come up at this stage then you have vpn/route/network problem. If you get Extension in use, try a different number.
 
After checking into all the suggestions, it appears to be a problem with port 1720. 1719 works fine but something is wrong with 1720. Our firewall guys are looking into and I will let you know if this fixes the issue. Thanks a lot for all your help.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top