Connecting an Avaya ip phone to BCM50 via VPN (Draytek 2760VN)

Soldato
Joined
27 Apr 2007
Posts
3,231
As Above,
I have a remote user that I am trying to get connected back to the office to run a verified working Avaya 1230 IP phone.
I have tried (using my limited vlan knowledge) creating and connecting to the office (office router is a Draytek 2830n) and setting up a vlan but feel that something isnt quite right in my setup. The VPN connects fine but nothing beyond that.
Has anyone else done this with similar hardware that could shed some light on settings/screenshots of their vlan/physical port assignment?
 
I know a little about Avaya stuff but mainly the really old IP Office stuff. There's a few ways you might be able to do this and it's a little unclear how you're trying to do it. I'm not saying I can help here but clarification might help others help you.

1. You can set up a VPN to the LAN that contains the Avaya PBX. You then configure the phone - either directly or via DHCP - to communicate with the IP address of the PBX. Older Avaya stuff required DHCP to point the phone at either a TFTP or HTTP site that contained its updated firmware (if newer) and the config. This would be something like the PBX's IP being 10.0.0.254 and your local phone being something like 10.0.1.8.

2. It looks from the mention of vlans that you could be talking about trying to extend the network at layer 2 so that the office LAN containing the PBX is bridged to your site. This would mean that it would look (apart from the latency) like it was plugged into the office LAN - so DHCP would work from there and all the IP addressing would be the same as if plugged in on site. This is probably harder to achieve and I don't think will get you anything that just telling the phone "PBX is over there" via DHCP.

Gareth
 
Hi Canedd, yea option 2 is what I am trying to achieve, using bt infinity services both the remote user and the site containing the BCM50 PBX.
The guy is working from home, his router allows a single physical port to be assigned a Vlan so it doesn't interfere with the rest of his network (he hosts a server for his family etc...dont ask!).
The phone is set to a static ip, was tested on site and worked fine, the S1 and S2 ip and ports are correct etc also.
 
A VLAN doesn't necessarily do what you want. To achieve that, you'd have to bridge the office LAN at layer 2 and your equipment probably doesn't do that. It's also known as LAN extension or Data Centre Interconnect. If you're just after a bit of isolation from his home network you probably want to do this:

These are examples
Office network: 10.0.0.0 /24 (subnet mask 255.255.255.0)
Office default gateway (router): 10.0.0.1
PBX: 10.0.0.254
TFTP/HTTP Server: 10.0.0.10

Home User's home network: 192.168.0.0 /24
Home User's home network gateway: 192.168.0.1

Home User VPN: 10.0.1.0 /24 <---> 10.0.0.0 /24

Home User's office network: 10.0.1.0 /24
Home User's office network gateway: 10.0.1.1

Home User's office phone:
IP: 10.0.1.20
Subnet Mask: 255.255.255.0
Gateway: 10.0.1.1
PBX: 10.0.0.254
HTTP/TFTP server: 10.0.0.10

Obviously substitute in the IP ranges of the existing office and home network.
"/24" is CIDR notation for a subnet with a mask of 255.255.255.0

This would give you a routed connection rather than bridged. It's much more widely supported and hence easier to set up. Simpler to administrate in a lot of ways because you can see the separate networks from the addresses rather than just one big network without any clue where devices are physically located. Also potentially better performance because you won't have broadcasts unnecessarily being bridged from one to the other.
 
Back
Top Bottom