GarryWilmeth

Is it possible to use an Avaya 5610 at a remote location that has Dynamic DSL?

The phone is communicating with the system and downloading updates, etc.. After it completes, I get a message that says, "Discover XXX.XXX.XXX.XXX" where X is the IP address of my T1 at the office (where the IP Office 406 is located).

Thanks!

koelemon

Yes, as long as you are using some sort of VPN or public addressing (which is not at all reccomended) on the IP Office side.

Essentially, you would have the phone set to an address local (probably private 192.168.x.x) address, using their local DSL router as the router, then the rest of the addresses would be on the IP Office addressing scheme.

__________________
"There are only 10 types of people in the world,
those who can read binary and those that cannot."

PBXtech.info

 

GarryWilmeth

Scratch that... I was only trying to quickly test the IP phone.

Here is my problem.

I am trying to connect an Avaya 5610 phone at my home office. Here is my configurations...

Office:

Avaya IP Office 406 connected to internet Via T1 through a Cisco 1841 router. I have configured a site to site VPN between this router and the router at my home office. The IP Office unit has been configured with an IP on my LAN. Manager is running on a windows 2003 server.

Home:

Avaya 5610 IP Phone connected to internet via SBC Dynamic DSL through a Cisco 1710 VPN router. I have configured a site to site VPN between this router and the router at my office.

Avaya 5610:

IP= IP address on my home LAN
CallSv= LAN1 IP address for IP Office (Configured with gatekeeper on)
CallSvPort= 1719
Router= IP address of LAN interface on cisco 1710 (Home Router)
Mask= SNM of LAN on cisco 1710 (Home Router)
FileSv= LAN IP address for PC on remote server running Manager
802.1Q= Off

When I start the phone, it will connect to the TFTP server, download and install scripts, auto create and extension in manager and then it hangs on "Discover X.X.X.X" where X.X.X.X is the IP address of the IP Office unit. Here is the output from the IP Office monitor...

493892mS PRN: Recv: GatekeeperRequest 0a0a0a05
498879mS PRN: Recv: GatekeeperRequest 0a0a0a05
504558mS PRN: Recv: GatekeeperRequest 0a0a0a05
504603mS PRN: Recv: GatekeeperRequest 0a0a0a05
509583mS PRN: Recv: GatekeeperRequest 0a0a0a05
514569mS PRN: Recv: GatekeeperRequest 0a0a0a05

From home, I can ping all LAN IP addresses at office exept that of the IP Office unit. From the office, I can ping the IP phone and all other LAN addresses at home.

koelemon

Make sure UDP ports 49152 through 53247 are open as well

__________________
"There are only 10 types of people in the world,
those who can read binary and those that cannot."

jiml@SF

Garry, I am having the same problem. I have gone as far as putting the ip office 406 3.1.48 on a public ip on one provider and the 5610 setup with a public ip on another provider and recieve the same problems. I can see the tftp take place, but the phone will not register. There are no firewall or blocked ports. But with my cisco ip phones and a CME 2610 on the same lines wala no problems. I actually have a ticket in with avaya about this.

crusty

Did you manage to find an answer to this question? I was thinking that it can't be done because the 2nd site is another subnet and IP Office needs a VPN connection to allow this (because the Logical Lan is NATed). Also this VPN connection must terminate at the IP Office not a local router. (IP 406v2)

Please advise, I am having the same problems.

PBXtech.info

 

jiml@SF

yes it can be done, the problems that everyone are experiencing are actually due to avayas software development. I have found that they are using a proprietary h323 format, this format has its own issues mainly because it is using the udp protocol instead of tcp like all other voice over. This is why if you reboot a switch that ip phones are branched out registered phone become unregistered and will display the extension is already in use error. Avaya is aware of this and as of not will not be coming out with a patch, avayas tech support points the blame at ipv4 stack. I find this quite hilarious being that a 30 year old plus protocol works perfectly fine with the normal h.323 standard and sip. Apperently avaya thinks that they are unique and standards should be bent for them. Now , as far as the vpn goes the pix is the only out of the box supported vpn gateway, junipers netsreen requires a patch to load on top of the firmware to work with avayas ip voice. Being that all the problems i have run into one way or the other with the ip office, i would highly recomend not using it as a vpn endpoint, i would use 2 pixs, and add the routes on to the ip office. Hope that helps.