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

VPN Remote 5610SW IP Phone 1

Status
Not open for further replies.

MWeise

IS-IT--Management
Sep 29, 2006
72
US
Hi gang,
New guy on the forum here!! I recently installed an IP Office 403 and it actaully works :) I was recently certified and it was my first. An Ip Office virgin so to speak. My questions are these:

I am adding a home office remote phone a 5610SW IP.

Is this correct:
1. Update the *.scr file to the 4600VPN *.scr file
2. Install Communication Manager, configure.
3. Setup the extension in the Manager Config as a remote extension.
4. Plug it in at the Router in the home office location.
5. Configure the IP settings.

And I ma good to go, correct? I' over simplifying a bit :) but you get the idea. Am I missing anything? I don't need any additional softwares or licenses do I?
I REALLY appreciate the help!!
Mike
 
Hi, what country are you in? Where did you do the 5 day training course?

Firstly, what's this Communication Manager? Avaya Communication Manager is a completely different product than the IP Office (it's the new Definity). Are you talking about Manager - the programming tool & TFTP server?

Manager acts as a TFTP server and has the latest firmware for the phone. It should br running on the same subnet as the phone when it boots to upgrade it (if required).

Is the IP Office the DHCP server? It's easier if it is.

1. Plug the phone into the LAN on the same site as the IP Office.
2. The phone will get an IP address from the IP Office and system defaults will register the phone and assign an xtn/user automatically.
3. The phone is working.

Then you can start changing it's settings. Reset the phone and enter programming during boot. Enter it's static IP address, router etc

Or, you can do it all manually.
1. Create a new user. It will ask you if you want to create a VoIP xtn - say yes. Save the config
2. Plug the phone in set it's IP address etc

NOTE: it's best to make sure the phone works in the office before taking it home. You don't want to be stuck miles away trying to get it to work.

You don't need to change the *.scr file unless you really want to edit the settings - do you?

 
I'm in the US of A my technical friend :) Took the 5 day over at Avaya in California. Apparenlty, it was pretty good stuff? Did the install, voice mail, auto attendant without a problem.

Dude, you rock that is the info I needed. As far as the Communication Manager, I got that info off another thread I think that's where I was getting confused.

No, the IP Office Unit is not setup as DHCP, but let me follow what you got. I report back soon!!

Thanks again for the help!!
Mike
 
I'm an ex-Avaya Certified Instructor on the IPO and this is supposed to be taught in the 5 day course! I ran a good couple of days on VoIP with lots of hands on installing of IP phones using DHCP and static. At least that's "supposed" to be in the course. Some supposed qualified instructors somehow forget to include certain vital information that is required in the real world!

Give it a go. It's a bit hard to explain in such a short area but it should make sense when you're hands on. If it's just one phone then just use static IP addresses. Set it up in the office first and then take it off site.

Let me know how you go.
 
It's funny you mention that, we (the class) specifically asked about remote setup, home office access info, etc and the instructor said they would get us the info but never did. Other than that it was good training, like I said, I did my first one with NO problem :)I printed out your instructions and will let you know how it goes!!

CYA

Mike
 
Hey Disturbedone,
Riddle me this batman, I use outlook Express on the Voice Mail server to copy voicemail to emails, and it is working fine ACCEPT for the fact that when it sends the email to the user it generates ANOTHER outbound email with no delivery address? Can't figure that one out. Not a big deal, everything is working fine accept for the fact every now and then when I log into the Outllok Express there are like 100 outbound messages that can't be delivered because there is no address in the To: field, yet the user get's the copy just fine?

Thanks,
Mike
 
No idea on that one. Is this with every single email you get a blank one? Is there any attachment ie is it sending the wav file again just with no recipient?

What voicemail - Lite or Pro? What version?

Strange!

First step: RTFM. Second step: RTFMA.

 
Yes, every single one you get a blank one with NO attachment. We are using Voice Mail Pro version 3.1 (18)with Outlook Express. Crazy, can't figure it out.

Mike
 
Also, where do you find the 46XXvpnupgrade.scr or *.txt file? I've searched EVERYWHERE

Thanks,
Mike
 
It's in the C:\Program Files\Avaya\IP Office\Manager folder but it's just 46xxupgrade.scr. There's really no need to edit this for most normal uses.

As for the emails...are you getting failure receipts for the 2nd email? If not, I'd turn off saving emails to the Sent Items folder and just forget about it. If you are, then I'll give you the Avaya answer and upgrade to the latest version! No idea other than that sorry. Never heard or seen that happening before.
 
I can't figure it out, I setup the 5610SW IP Phone on the network inside the office, boots up and works fine accept for the TFTP Server which "Times Out"...otherwise, the phone works great. I take it home and plug it into my router and I get nothing and still get the TFTP error? I must be missing something? Is this a TFTP server thing? Or maybe a Fire wall or gateway issue? Not sure any help would be appreciated. I will try NOT saving sent messages in Outlook and see what happnes.

Thanks!!
Mike
 
In the office...
1. Is Manager open & running? It has to be to act as a TFTP server.
2. Is it on XP? Is the Windows firewall off? This is probably why it won't send the files.
3. Where is it getting it's IP address from? If not the IPO then have you configured the DHCP server to allocate the IP address of the PC with Manager as the TFTP server? The phone needs to know where to find it.

Out of the office...
If the phone doesn't work at all then it can't find th IPO
1. Where is it getting it's IP address from - static or DHCP? Do you have the IP address of the TFPT server allocated?
2. What are the IP address ranges you're using in & out of the office? If different, have you go IP routes in the IPO between them?
3. Have you left a firewall on the VPN connection? You don't need it, it's secure as it is. Turn it off if you do, but leave a firewall on the Internet connection.

Don't worry about the whole TFTP thing at the moment. Get the phone working and then worry about it. It doesn't need to download these files to work, it's just to upgrade it's firmware or set special settings but these are optional.
 
Your answers:

In the office...
1. Is Manager open & running? It has to be to act as a TFTP server. Mike - YES
2. Is it on XP? Is the Windows firewall off? This is probably why it won't send the files. Mike - YES, and YES the Firewall is OFF
3. Where is it getting it's IP address from? If not the IPO then have you configured the DHCP server to allocate the IP address of the PC with Manager as the TFTP server? The phone needs to know where to find it. Mike - Our internal Server is the DHCP server, and YES I think ? :)

Out of the office...
If the phone doesn't work at all then it can't find th IPO
1. Where is it getting it's IP address from - static or DHCP? Do you have the IP address of the TFPT server allocated? Mike - It gets the IP from the sever on our internal network. Allocated? Not sure on that one?
2. What are the IP address ranges you're using in & out of the office? If different, have you go IP routes in the IPO between them? Mike - Don't undertsnad the question? Our range of internal IP's is 192.168.100.200 - 250, externally is is something like 24.169. etc, etc?
3. Have you left a firewall on the VPN connection? You don't need it, it's secure as it is. Turn it off if you do, but leave a firewall on the Internet connection. Mike - Turned off

Don't worry about the whole TFTP thing at the moment. Get the phone working and then worry about it. It doesn't need to download these files to work, it's just to upgrade it's firmware or set special settings but these are optional.


Thanks for the help!!!
Mike
 
In the office...
3. I guess whoever looks after the DHCP server has configured something otherwise the phone wouldn't work. Check that the Scope Options include the TFTP server address. Also check in the IPO config in the System settings that it has the TFTP server IP address too.

Out of the office...
1. Does the other location have it's own DHCP server allocating a similar range eg 192.168.100.150-199 or is there a DHCP relay agent sending the requests back to the office?
2. Office is 192.168.100.200-250, does the other location have it's own DHCP server allocating a similar range eg 192.168.100.150-199 or is it allocating a completely different range eg 10.0.0.200-250? If it's a different range then you'll need IP routes.
 
I think this is definately an Ip issue :) The phone works great inside the netwrok. I had these settings on the phone EXTERNALLY:

TFTP - 192.168.100.115 which is where the Manager/TFTP is running but it still times out.
Call SVC - 0.0.0.0
File Svc - 192.168.100.115
Mask - 255.255.255.0
Router - I think I screwed the pooch on this one? Is this the outside IP for our company network router?
Also, I think the router in my home hands out IP addresses, soi the phone isn't getting an IP from our company server or the IP office correct?

Our company outside IP is 24.117.250.149

I'm soooo confused :)

Later,
Mike
 
Hmm, this gets quite complicated depending on how much you understand about IP.

You need to find out what IP address range you are using at home. It is probably 10.0.0.x or something but you need to know.

How is the VPN being created? Through your router at home (hardware VPN)? Or are you using a Windows PC to create the VPN (software VPN)? This only works using a hardware VPN. If you haven't got that facility on your router at home then you'll need to get one that does.

Then it starts getting tricky and you really need to understand IP and routing. I'd suggest talking to the IT dept and work out what is what because it's a bit hard to tell you how to do it because there are so many factors that come into play.

What country are you in?

 
Thanks, I would agree, my IP expertise is lacking :) I am in the US. Thanks for the help!!
Mike
 
I'd have a word to the IT dept and they should be able to let you know how the IP network is set up. Basically you need the phone to have an IP address in the range of the network at home, a hardware VPN, and routing between the 2 networks.

In the IP Office you can create an IP Route from your office network to your home network. Once this is set up, and the routing is done at the home network, then it should to talk.

Sorry, but it's a bit too involved to try and resolve without having more info on the IP stuff. I could go on and on about the network stuff but if it's not making a lot of sense to you then it wouldn't mean much.

Also have a word to your distributor and give them as much info as you can about the networks and they'll probably draw a picture so it makes more sense to them on paper. They should be able to provide some support but they'll need to know all the IP details.

Good luck!
 
I completey understand. I wil call Catalyst the ditributor and have them walk me through it. I have ONE last question. I have an incoming phone line that I would like to send directly to an extension, by passing the auto attendant but still giving the user a voice mail box. I went into manager and directed the incoming call route to that etxnsion but I still get the auto attendant? Do I have to do anything in voice mail pro?

Thanks
 
The Incoming Call Route should have a Destination of "JSmith 203" or whatever the name of the User is. If you've done this then there's no way it can go to an Auto Attendant.

Is the incoming line a DDI/DID on an ISDN line? If so, then make sure the Incoming Number is correct. If it's a CO line then make sure you've got the correct Incoming Group ID set on the Line and in the Incoming Call Route.

Hope this helps.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top